Head to head · CRM records · October 2026 research run

Affinity vs Salesforce API + MCP

Affinity scores 62.7 (B) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 5 of 7 scored categories. Salesforce API + MCP leads on payments & pricing. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

Affinity B

Best 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, 59 against 45
  • Schema & documentation, 91 against 0
  • Agent ergonomics, 66 against 0
  • Security & auth, 66 against 40
  • Maintenance & community, 70 against 4

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 F

Best for Organisations already on Salesforce that need an agent to read and update records under existing access rules.

Ahead on

  • Payments & pricing, 45 against 15

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.3 out of 5

Watch for

API access needs the $25 add-on on Pro Suite or a Core seat at $195, and Free and Starter suites have none

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Affinity +91

Affinity 91

Public OpenAPI 3.1.1 files for three dated versions, 115 operations on 88 paths in 2026-09-17 (25). llms.txt with 386 links and a Markdown copy of each page (10). Operation descriptions state the permission needed, limits and beta status, and the MCP tool page says when to pick search_companies_top_matches over search_all_companies (16 of 20). 373 schemas with 125 enums and additionalProperties: false on the ones we read, though list endpoints take a filter string with its own grammar (12 of 15). 868 example entries and typed error schemas with a code and message, while the error page itself is a table of HTTP codes (13 of 15). Date-based versions chosen by header, a migration page per version and a dated changelog (15).

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The hosted MCP references, the API reference, llms.txt and the platform versioning notes were all read there. The release notes on help.salesforce.com load only by script, www.salesforce.com/llms.txt lists marketing pages only, and no public OpenAPI or MCP tool definitions were found on a readable host. Contract, llms.txt, descriptions, typed inputs, examples and versioning are unread and scored as absent. 0 + 0 + 0 + 0 + 0 + 0 = 0.

Agent ergonomics Affinity +66

Affinity 66

API responses can be sized with limit, fieldIds and fieldTypes, but the MCP server lists 75 tools and skills with no toolsets or dynamic loading documented (12 of 25). Cursor pagination with nextUrl, a filter grammar, and search endpoints with nested filters and up to five sorts (20). Errors come as an array of typed codes with messages, and validation errors name the property (15 of 20). No idempotency keys. The affinity-mcp 0.5.1 package registers every tool with readOnlyHint, destructiveHint and idempotentHint, which we read in the wheel. We couldn't list the hosted server's tools without an account. Deletes and merges wait for confirmation per the docs (13 of 20). Defaults are sensible and few parameters are required, but we found no official API client in any language, only the Python MCP package (6 of 15).

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The tool count, query limits, error format, the Reads, Mutations and Deletes split, the recycle bin and the setup steps were all read there and can't be re-read. No official general-purpose REST SDK was found on a readable host. Every line is unread and scored as absent. 0 + 0 + 0 + 0 + 0 = 0.

Maintenance & community Affinity +66

Affinity 70

Newest API changelog entry 28 October 2026, and affinity-mcp 0.7.0 and 0.7.1 on PyPI the same day (30). Seventeen dated changelog entries since 4 August 2026, among them version 2026-09-17 on 17 September, plus affinity-mcp 0.6.0 (21 October) and 0.7.0 and 0.7.1 (28 October) (20). Closed service with a public changelog, a support address and a feedback endpoint. We didn't test support (10 of 15). Not in the official MCP registry under its own namespace, where a search returns only third-party servers, and no official API SDKs. The official affinity-mcp package is on PyPI (5 of 15). affinity-mcp 0.7.1 is classed Beta, requires Python 3.13 and has no public repository or CI we could find (5 of 10).

Salesforce API + MCP 4

No dated API or MCP change could be read on 4 November. developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The release notes on help.salesforce.com load only by script. The April 2026 GA in the listing is now more than 180 days old in any case (0). No dated change in the 90 days from 6 August could be read (0). Support and help routes are linked from Salesforce's readable pages; the changelog can't be read (4 of 15). Not in the official MCP registry, which lists only third-party Salesforce servers on 4 November, and no official general-purpose REST SDK found (0). No packages to judge (0). 0 + 0 + 4 + 0 + 0 = 4.

Payments & pricing Salesforce API + MCP +30

Affinity 15

No x402, MPP or L402 (0). Per-seat yearly prices are public, Essential $2,000, Scale $2,300 and Advanced $2,700 a user a year, with no per-call price and every plan sold through sales (10). No free tier or card-free trial that reaches the API. The help centre says trial accounts can't use the API until they buy Scale or above (0). A person at a paying firm makes the key or approves OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Salesforce API + MCP 45

No x402, MPP or L402 (0). The pricing page, read on 4 November, publishes per-user prices (Starter Suite $25, Pro Suite $100 plus "Web Services API Additional $25", Core $195, Advanced $395, Max $550 a user a month) (10). "Try Sales Cloud free for 30 days. No credit card" (20). The Developer Edition and Flex Credit readings came from the blocked developer host and are struck. A person signs up and an admin configures access (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Security & auth Affinity +26

Affinity 66

The hosted MCP server takes OAuth 2.0 with scopes mcp, mcp.read, api, api.read and offline_access. Since the 8 October check Affinity documents OAuth apps for the API too, with PKCE, those scopes, one-day access tokens and 90-day refresh tokens, but they are in early access and must be switched on by Affinity, so they aren't credited yet. API keys are named, revocable, several per user and can be tied to an IP allowlist, but carry all of their owner's permissions with no per-key scope or expiry. v2 takes the key only as a Bearer header (25 of 30). Read-only access can be chosen at OAuth consent, admins can disable each AI client for the firm, and every delete and merge waits for confirmation. An API key has no read-only mode (16 of 20). The server returns notes, transcripts, email subjects and files written by outsiders, and the MCP security page still gives no prompt-injection guidance (3 of 15). Manage Apps shows each key's owner, last use and revoked history and the account's usage, and the local server can export OpenTelemetry traces. No per-call audit log for the operator is documented (7 of 15). SOC 2 Type II and ISO 27001, 27017 and 27018 on the trust centre and security page, a yearly third-party penetration test, and a bug bounty the security page mentions without a public programme page. No security.txt (15 of 20).

Salesforce API + MCP 40

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The OAuth 2.0 with PKCE and mcp_api scope reading came from there; no readable page states the API's credential model (0). Salesforce's security model page, read on 4 November, says access is limited at the object, field and record level through profiles, roles and permission sets; the per-risk MCP servers and delete confirmation are struck with the docs (10 of 20). Record text written by outsiders reaches the model. Salesforce's security site publishes prompt-injection advisories that turned on human confirmation for Agentforce actions (14 and 25 August 2025) and an LLM risk whitepaper, none for hosted MCP (4 of 15). The same page lists Setup Audit Trail, Login History and Field History Tracking built in, and Event Monitoring of 90+ event types in the paid Shield add-on (8 of 15). A responsible disclosure policy, an "independent bug bounty program" and SOC 2 Type II, ISO, PCI DSS L1 and FedRAMP claims on the security model page, and a public advisory archive and feed with CVEs (newest 2 October 2025). No security.txt found. Read above twilio-voice (disclosure, bounty, certifications, no advisories, 15) for the public advisories (18 of 20). 0 + 10 + 4 + 8 + 18 = 40.

Reliability Affinity +14

Affinity 59

Status page at status.affinity.co with component history and separate components for External API v1, External API v2 and MCP (20). Its history feed shows one incident touching the APIs in the 90 days to 2 November 2026, "Disruption with All Services" on 3 September 2026, posted at 15:15 PDT with "errors or an inability to access the service" put down to its cloud provider, recovery seen at 15:35 and resolved at 16:18, 63 minutes in all. The incident page lists every component as affected, the CRM, External API v1 and v2, MCP, processing pipelines, mobile apps and extensions, though Affinity rated it minor. An outage of every service with errors across the board reads as a major in this run, however short (10). The 8 October reading of 15 sat between checklist values. Other entries concerned Affinity Analytics (11 August, 15 minutes) and a maintenance window announced on 14 August for 29 August, neither counted. Limits published, 900 requests a minute per user and 100,000 a month per account on Scale and Advanced (15). The docs tell integrators to handle 429 and every response carries x-ratelimit-* headers with seconds to reset, but we found no Retry-After, no backoff guidance and no idempotency keys (8 of 15). No SLA in the master subscription agreement. The trust centre lists a Service-Level Agreement item whose text we couldn't read (0). API v2 has stable dated versions, but 39 of 115 operations are beta and the affinity-mcp package is classed Beta on PyPI (6 of 10). Hosted lines used. 20 + 10 + 15 + 8 + 0 + 6 = 59.

Salesforce API + MCP 45

status.salesforce.com is a status site drawn by script, and trust.salesforce.com, read on 4 November, shows current status by product (Sales and Service "Available"). The status-page line is kept on that and the 1 October reading (20). The 1 October incident count came from api.status.salesforce.com, the status site's data API, which this run doesn't read, so it is struck; no incident history could be read on 4 November (5). developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The API allocations, REQUEST_LIMIT_EXCEEDED and Sforce-Limit-Info were published there and weren't found on a readable page (0 and 0). Salesforce's security model page says "99.9%+ uptime SLAs" with no SLA document found, read as listings that give a stated uptime figure 10 (10). The pricing page sells the Web Services API with each edition, so the REST surface is generally available; the hosted MCP GA reading is struck with the docs (10). 20 + 5 + 0 + 0 + 10 + 10 = 45.

Score by category

CategoryWeightAffinitySalesforce API + MCPEdge
Reliability16%5945Affinity +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%910Affinity +91
Agent ergonomics13%660Affinity +66
Security & auth14%6640Affinity +26
Payments & pricing10%1545Salesforce API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%704Affinity +66
Transparency & trust7%6767even
Negative events≤1500
TotalB 62.7/100F 27.8/100

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-28none
Terms last updatednot read yet2025-04-08
Privacy policy last updated2026-07-01no date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity268 PyPI/wknone
Agent reviews3.3/5 (4)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Salesforce API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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 39 of the 115 v2 operations are marked beta.

Salesforce API + MCP

Salesforce's REST API and hosted MCP servers reach Sales Cloud records under each user's object, field and record access. API access starts at Pro Suite plus a $25 add-on or Core at $195 a user a month. Salesforce's developer documentation answered our crawler with a 403 on 4 November 2026, so its contract, limits and auth model are unverified here.

Before you call either

Affinity

  1. Send X-Affinity-Api-Version: 2026-09-17 on every request. Without it a key's default version applies, and an OAuth app with no pinned version falls back to 2024-01-01
  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. Ask the admin for a permission set limited to the objects and fields the job needs, since calls run with the user's object, field and record access
  2. Confirm the org's edition includes the Web Services API (Core and above, or Pro Suite with the $25 add-on) before building on it
  3. Check trust.salesforce.com for the product's status before retrying calls that fail across the board
  4. Test writes in a trial or sandbox org rather than production

Questions

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

Affinity scores 62.7 (B) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 5 of 7 scored categories. Salesforce API + MCP leads on 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.