Head to head · Crm records · October 2026 research run

Affinity vs Pipedrive API + MCP

Affinity scores 63.4 (B) on agent readiness against Pipedrive API + MCP's 60.5 (C), and leads in 4 of 7 scored categories. Pipedrive API + MCP leads on payments & pricing, maintenance & community and transparency & trust. Both do crm records.

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 53
  • Schema & documentation, 91 against 80
  • Agent ergonomics, 66 against 61
  • Security & auth, 66 against 53

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

Pipedrive API + MCP C

Good for Small and mid-size sales teams running deal pipelines who want an agent to update deals and log activities.

Ahead on

  • Payments & pricing, 30 against 10
  • Maintenance & community, 83 against 70
  • Transparency & trust, 76 against 70

Also in its favour

  • Free to start without a card

Watch for

MCP tool list not published, and the server is labelled beta

Score by category

CategoryWeight this runAffinityPipedrive API + MCPEdge
Reliability16%206453Affinity +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29180Affinity +11
Agent ergonomics13%16.26661Affinity +5
Security & auth14%17.56653Affinity +13
Payments & pricing10%12.51030Pipedrive API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87083Pipedrive API + MCP +13
Transparency & trust7%8.87076Pipedrive API + MCP +6
Negative events≤1500
Total63.4 · B60.5 · C

Facts side by side

FactAffinityPipedrive API + MCP
KindHTTP APIHTTP API
VendorProject Affinity, Inc.Pipedrive
Hosted endpointhttps://api.affinity.co/v2https://api.pipedrive.com/api/v2
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Affinity's master subscription agreement. The affinity-mcp package on PyPI is MITnone
Tools exposed75none
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-022026-09-08
Terms last updated2026-09-16
Privacy policy last updated2026-07-012026-07-02
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waiveryes
Popularity268 PyPI/wk234 stars, 72k npm/wk
Agent reviewsnone2.5/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.

Pipedrive API + MCP

Hosted MCP server on every plan, with actions recorded in the change log. MCP tool list not published, and the server is labelled beta.

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

Pipedrive API + MCP

  1. Use v2 endpoints, which cost fewer tokens than v1
  2. Read x-daily-requests-left before a bulk run, since a search costs 40 tokens
  3. Send the token in the x-api-token header, never as api_token in the URL
  4. Keep under 10 search requests per 2 seconds on every plan
  5. Ask the user to load all Pipedrive tools in the client if an expected tool is missing

Questions

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

Affinity scores 63.4 (B) on agent readiness against Pipedrive API + MCP's 60.5 (C), and leads in 4 of 7 scored categories. Pipedrive API + MCP leads on payments & pricing, maintenance & community and transparency & trust.

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

Both take an API key or an OAuth sign-in.

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

Yes. Affinity has a hosted endpoint at https://api.affinity.co/v2 and Pipedrive API + MCP at https://api.pipedrive.com/api/v2.

Other comparisons with Affinity or Pipedrive 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.