Get an audit

Head to head · Crm records · October 2026 research run

Affinity vs Salesforce API + MCP

Affinity scores 63.4 (B) on agent readiness against Salesforce API + MCP's 60.5 (C), and leads in 3 of 7 scored categories. Salesforce API + MCP leads on agent ergonomics, security & auth and payments & pricing. Both do crm records.

AffinityProject Affinity, Inc. · HTTP API B63.4/100#311 of 722 Salesforce API + MCPSalesforce · HTTP API C60.5/100#398 of 722

Which one, for what

Affinity B

Good for Venture capital, private equity and other private capital firms that already run Affinity and want an agent to read relationship strength, pipeline lists, notes and meetings, then update fields and log notes.

Ahead on

  • Reliability, 64 against 58
  • Schema & documentation, 91 against 76
  • Maintenance & community, 70 against 18

Also in its favour

  • Runs on your own machine

Watch for

No self-serve access. Every plan button reads Contact sales, the Essential plan has no API, and trial accounts can't call the API

Salesforce API + MCP C

Good for Organisations already on Salesforce that need an agent to read and update any object under existing security rules.

Ahead on

  • Agent ergonomics, 76 against 66
  • Security & auth, 72 against 66
  • Payments & pricing, 30 against 10

Watch for

No hosted MCP changelog yet

Score by category

CategoryWeight this runAffinitySalesforce API + MCPEdge
Reliability16%206458Affinity +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29176Affinity +15
Agent ergonomics13%16.26676Salesforce API + MCP +10
Security & auth14%17.56672Salesforce API + MCP +6
Payments & pricing10%12.51030Salesforce API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87018Affinity +52
Transparency & trust7%8.87072Salesforce API + MCP +2
Negative events≤1500
Total63.4 · B60.5 · C

Facts side by side

FactAffinitySalesforce API + MCP
KindHTTP APIHTTP API
VendorProject Affinity, Inc.Salesforce
Hosted endpointhttps://api.affinity.co/v2https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
LicenceProprietary service under Affinity's master subscription agreement. The affinity-mcp package on PyPI is MITnone
Tools exposed7511
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-02none
Terms last updated2025-04-08
Privacy policy last updated2026-07-01no date given
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity268 PyPI/wknone
Agent reviewsnone4/5 (2)

Verdicts

Affinity

A public OpenAPI 3.1 file, dated API versions with migration notes and a hosted MCP server with a read-only OAuth scope give an agent a well-documented way in. Access needs a Scale plan at $2,300 a user a year, sold through sales, with no trial that includes the API, and 36 of the 112 v2 operations are marked beta.

Salesforce API + MCP

Per-user OAuth 2.0 with PKCE and only mcp_api and refresh_token scopes. No hosted MCP changelog yet.

Before you call either

Affinity

  1. Send X-Affinity-Api-Version: 2026-09-17 on every request, or the key's default version applies. Unauthenticated calls answered as 2024-01-01 when we checked
  2. Read x-ratelimit-limit-user-remaining and x-ratelimit-limit-org-remaining on each response. The limits are 900 calls a minute per user and, below Enterprise, 100,000 a month per account, shared by v1, v2 and MCP
  3. Follow pagination.nextUrl for the next page, and pass fieldIds or fieldTypes so list calls return only the fields needed
  4. Check for duplicates before a create. There are no idempotency keys, so a retried POST can make a second record
  5. For MCP, untick the write scope at OAuth consent when the task only reads. Treat note, transcript and file text as untrusted input

Salesforce API + MCP

  1. Call getObjectSchema in index mode first, then detail mode for the object you need
  2. Put WHERE and LIMIT on every SOQL query and filter on indexed fields to avoid timeouts
  3. Ask the admin for SObject Reads if the job only reads, since SObject All includes delete
  4. Watch Sforce-Limit-Info on REST calls, as the daily allocation is shared by the org
  5. Re-authorise if a token came from the beta service, because beta tokens don't work on GA

Questions

Which is better for AI agents, Affinity or Salesforce API + MCP?

Affinity scores 63.4 (B) on agent readiness against Salesforce API + MCP's 60.5 (C), and leads in 3 of 7 scored categories. Salesforce API + MCP leads on agent ergonomics, security & auth and payments & pricing.

Do Affinity and Salesforce API + MCP need an API key?

Affinity takes an API key or an OAuth sign-in. Salesforce API + MCP uses an OAuth sign-in.

Can an agent call Affinity and Salesforce API + MCP without installing anything?

Yes. Affinity has a hosted endpoint at https://api.affinity.co/v2 and Salesforce API + MCP at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all.

Other comparisons with Affinity or Salesforce API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report