On this page

Most MCP statistics I find are one number in one article: a server count from a directory, a download figure from a launch post, a vendor list from a conference keynote. Each was true on the day it was written. None of them tells you whether adoption is speeding up or flattening out.

This page measures the trend. A script reads the official MCP Registry, the npm and PyPI download logs and GitHub every day, keeps every reading, and rebuilds the numbers below. The vendor table is checked by hand against each company's own announcement. A2A, the agent-to-agent protocol Google introduced in April 2025, sits alongside so you can compare the two on the same measures.

It is a census, not a directory. If you want to browse or search servers, Agenstry, the official registry and Smithery do that well. If you want the concepts first, AI agent vs MCP server explains what a server is, and MCP vs A2A vs ACP explains how the protocols differ.

Headline numbers
  1. The official MCP Registry lists 65,877 servers as of 17 November 2026, up 20,970 (+47%) in 30 days. 68% of them are remote endpoints you connect to over HTTP rather than packages you install.
  2. The MCP TypeScript SDK was downloaded 89.5 million times from npm in the week to 15 November 2026, +969% on the same week a year earlier. The Python SDK (mcp) added 80.5 million downloads on PyPI in the week to 16 November 2026, +493% year on year.
  3. MCP SDKs out-download the A2A SDKs 17 to 1: 170.0 million a week for MCP on npm and PyPI combined against 10.1 million for A2A, although A2A is growing faster from its smaller base: its Python SDK's weekly downloads are up 928% year on year.
  4. 44,430 public GitHub repos carry the mcp-server topic, against 640 tagged a2a-protocol (2,561 tagged a2a), counted on 17 November 2026.
  5. 22 of the 23 AI vendors I track have a dated, sourced MCP announcement; 8 ship A2A in a product, and 8 do both.

Updated . Refreshed daily from the MCP Registry, npm, PyPI and GitHub APIs.

Cite this page: "MCP and A2A adoption census", Gravity, updated , https://gravity.fast/data/mcp-adoption-statistics/. Data licensed CC BY 4.0: reuse it anywhere, commercially too, with credit and a link. The monthly series is in data.csv.

MCP vs A2A at a glance

The same measures for both protocols, read on the same day. Where a measure does not exist for A2A, such as an official server registry, the row says so.

MeasureMCPA2ASource
SDK downloads, last 7 days, npm89.5 million6.8 millionnpm downloads API, week to 15 November 2026
Change on the same week a year earlier, npm+969%+2654%npm downloads API
Change over 4 weeks, npm+127%+191%npm downloads API
SDK downloads, last 7 days, PyPI80.5 million (mcp) plus 16.9 million (fastmcp)3.3 million (a2a-sdk)ClickPy (PyPI download logs), week to 16 November 2026
Change on the same week a year earlier, PyPI+493%+928%ClickPy
Servers in the official registry65,877 (1,052 deprecated)No official registryMCP Registry API
Servers listed on Smithery20,751n/aSmithery registry API
GitHub repos by topic44,430 mcp-server, 45,315 model-context-protocol, 121,807 mcp640 a2a-protocol, 2,561 a2aGitHub search API
Stars on the spec repo9,70726,562MCP spec, A2A spec
Stars on the Python SDK repo24,8762,247GitHub API
Stars on the TypeScript or JS SDK repo13,774655GitHub API
Stars on the reference servers repo92,062n/amodelcontextprotocol/servers

All figures read on 17 November 2026 unless the row gives another date. Downloads are raw registry counts, which include CI systems and dependency installs, so they measure how widely the SDKs are built into software, not how many people use MCP. GitHub topic counts cover public repos that chose to tag themselves.

SDK downloads over time

Weekly downloads of the official SDKs are the longest clean series available for either protocol: npm keeps daily counts back to the TypeScript SDK's first release in November 2024, and the PyPI logs go back as far. The chart covers the last 52 weeks.

Weekly SDK downloads, MCP vs A2A Weekly downloads, 7-day totals, for the 52 weeks to 2026-11-15. MCP TypeScript SDK on npm 89.5 million in the last week; MCP Python SDK on PyPI 80.5 million; A2A SDKs on npm and PyPI 10.1 million. WEEKLY SDK DOWNLOADS, MCP VS A2A 0 24M 48M 72M 97M 2025-11 2025-12 2026-02 2026-03 2026-06 2026-11 MCP TypeScript SDK (npm) MCP Python SDK (PyPI) A2A SDKs (npm + PyPI)
Non-overlapping 7-day totals from the npm downloads API and ClickPy's copy of the PyPI download logs, to 15 November 2026. The A2A line adds the JavaScript and Python SDKs together.

Two things stand out in the series. In the latest full week, MCP's downloads ran about 13 times A2A's on npm and about 25 times on PyPI. A2A is growing faster in percentage terms, from a far smaller base, which is what you would expect from a protocol adopted mainly inside enterprise agent platforms rather than by individual developers wiring tools to a model. The year-on-year figures for both are in the table above.

The official MCP Registry

The MCP Registry launched in preview on 8 September 2025 as the protocol's own catalogue, with a public API. Publishers register a server under a namespace they can prove they own, either a domain or a GitHub account. That makes it the cleanest growth signal for MCP: each entry is a deliberate act by a publisher, not a crawler's guess.

Registry measureCountShare
Servers listed (latest version of each)65,877100%
First published in the last 30 days20,97032%
Remote endpoint (streamable HTTP or SSE)44,73868%
Ships an installable package25,25538%
Package type: npm17,12226%
Package type: PyPI5,5488%
Package type: container image (OCI)1,9243%
Package type: MCP bundle (.mcpb)1,7903%
Package type: NuGet1830%
Package type: Cargo1370%
Published under a GitHub namespace (io.github.*)36,56155%
Marked deprecated1,0522%

Read from the public /v0/servers API of the official registry on 17 November 2026. A server can list both a remote endpoint and packages, so shares overlap. "First published" uses the earliest publish date of any version of the server, as the registry reports it.

Servers in the official MCP Registry, by month Servers listed at each month end (the current month to date): 2025-09 456, 2025-10 753, 2025-11 927, 2025-12 1206, 2026-01 1596, 2026-02 2756, 2026-03 4707, 2026-04 7259, 2026-05 10298, 2026-06 14194, 2026-07 19294, 2026-08 25943, 2026-09 37845, 2026-10 54001, 2026-11 66493. SERVERS IN THE OFFICIAL MCP REGISTRY, BY MONTH 0 17,953 35,906 53,859 71,812 2025-09 2025-11 2026-01 2026-03 2026-05 2026-07 2026-09 2026-11 Servers listed, cumulative
Servers still listed in the registry on the day of the latest read, counted by the month their first version was published; daily reads since 4 October 2026 add servers on the day they first appear. Servers removed from the registry before then are not counted.

The shape is steep. The registry took until January 2026 to pass 1,500 servers, then added 16,156 in October 2026 alone, its largest month, more than in its first 10 months combined (14,194). Most listed servers are remote: endpoints a client connects to over HTTP, with no package to install. That fits how MCP is now used, with hosted products exposing their own server rather than developers running a local process.

Which vendors support MCP and A2A

One row per vendor, each "Yes" linked to the vendor's own announcement, docs, release notes or press release, with the earliest date I could confirm. I record what was announced, not what any one product does today, and I list A2A launch partners separately from vendors that shipped A2A in a product.

VendorMCP supportFirst announcedA2A supportFirst announced
AnthropicYes: Created and open-sourced MCP; Claude Desktop supports local MCP servers source25 November 2024Not confirmedn/a
OpenAIYes: Agents SDK v0.0.7 adds MCP support source26 March 2025Not confirmedn/a
Google (Gemini API / Google Cloud / ADK)Yes: Agent Development Kit launches with MCP tool support source9 April 2025Yes: Native A2A in ADK; deploy A2A agents to Agent Engine, Cloud Run, GKE source1 August 2025
Microsoft (Copilot Studio / Azure AI Foundry / Windows)Yes: Copilot Studio agents can connect to MCP servers source19 March 2025Yes: A2A announced for Azure AI Foundry and Copilot Studio (preview) source7 May 2025
AWS (Bedrock / AgentCore)Yes: Open-source AWS MCP Servers for code assistants source1 April 2025Yes: Bedrock AgentCore Runtime supports the A2A protocol source11 November 2025
MetaYes: Llama Stack v0.1.0 Tools API ships an MCP provider source24 January 2025Not confirmedn/a
Mistral AIYes: Agents API SDK can use MCP tools source27 May 2025Not confirmedn/a
xAIYes: xAI API Remote MCP Tools in chat via API source2025-11 (month)Not confirmedn/a
CohereYes: Official SDK for building MCP servers for Cohere North source2025-05 (month)Launch partner: Named A2A launch partner source9 April 2025
IBMYes: ContextForge MCP Gateway first public release source5 June 2025Yes: ContextForge v0.6.0 adds A2A agent integration source22 August 2025
SalesforceYes: Agentforce 3 adds a native MCP client source23 June 2025Yes: MuleSoft MCP and A2A support, GA July 2025 source23 June 2025
SAPYes: SAP Build local MCP servers for Cursor, Claude Code, others source4 November 2025Yes: Joule Studio agent builder adds A2A and MCP support source5 November 2025
ServiceNowYes: AI Agent Fabric connects agents and tools over MCP source6 May 2025Yes: AI Agent Fabric supports agent-to-agent over A2A source6 May 2025
GitHubYes: Official open-source GitHub MCP server in public preview source4 April 2025Not confirmedn/a
Hugging FaceYes: smolagents v1.4.1 loads MCP server tools as ToolCollection source17 January 2025Not confirmedn/a
PerplexityYes: Official Perplexity API MCP server source2025-03 (month)Not confirmedn/a
Alibaba Cloud (Qwen)Yes: Qwen3 launch strengthens MCP support via Qwen-Agent source29 April 2025Not confirmedn/a
DeepSeekNot confirmedn/aNot confirmedn/a
OracleYes: MCP Server for Oracle Database via SQLcl source16 July 2025Yes: Oracle AI Data Platform catalog supports A2A and MCP agents source14 October 2025
AtlassianYes: Remote MCP Server (beta) for Jira and Confluence source1 May 2025Launch partner: Named A2A launch partner source9 April 2025
CloudflareYes: Build and deploy remote MCP servers on Cloudflare source25 March 2025Not confirmedn/a
BlockYes: goose open-source agent connects to systems via MCP source28 January 2025Not confirmedn/a
DockerYes: Docker MCP Catalog and MCP Toolkit announced source22 April 2025Not confirmedn/a

Each "Yes" links to the vendor's own announcement, docs or changelog, checked on 4 October 2026. "Launch partner" means the vendor was named among A2A's launch partners, which is a statement of intent rather than a shipped product. "Not confirmed" means I found no primary source; it is not a claim that support is absent.

The pattern is clear even with the caveats. MCP support is close to universal among large AI and software vendors (22 of 23), and it came early: 18 of the 22 dated announcements fall in the first half of 2025. A2A support is concentrated in enterprise agent platforms, where agents built by different vendors need to hand work to each other. Several model providers, including Anthropic, OpenAI, Meta and Mistral AI, have no A2A announcement I could find.

Change log and timeline

Protocol governance events, each with its primary source, followed by the movements the daily data picks up: registry milestones and GitHub topic milestones.

  1. : Official registry passed 65,000 servers (65,125).
  2. : Official registry passed 64,000 servers (64,354).
  3. : Official registry passed 63,000 servers (63,269).
  4. : Official registry passed 61,000 servers (62,485).
  5. : Official registry passed 62,000 servers (62,485).
  6. : Official registry passed 58,000 servers (60,671).
  7. : Official registry passed 59,000 servers (60,671).
  8. : Official registry passed 60,000 servers (60,671).
  9. : Official registry passed 56,000 servers (57,788).
  10. : Official registry passed 57,000 servers (57,788).
  11. : Official registry passed 55,000 servers (55,713).
  12. : Official registry passed 54,000 servers (54,316).
  13. : Official registry passed 53,000 servers (53,545).
  14. : Official registry passed 52,000 servers (52,294).
  15. : Official registry passed 51,000 servers (51,666).
  16. : GitHub repos tagged mcp-server passed 40,000 (40,272).
  17. : Official registry passed 50,000 servers (50,295).
  18. : Official registry passed 49,000 servers (49,226).
  19. : Official registry passed 48,000 servers (48,180).
  20. : Official registry passed 46,000 servers (47,407).
  21. : Official registry passed 47,000 servers (47,407).
  22. : Official registry passed 45,000 servers (45,188).
  23. : GitHub repos tagged mcp-server passed 40,000 (40,013).
  24. : Official registry passed 44,000 servers (44,466).
  25. : Official registry passed 43,000 servers (43,298).
  26. : GitHub repos tagged mcp-server passed 35,000 (35,527).
  27. : Official registry passed 42,000 servers (42,220).
  28. : Official registry passed 41,000 servers (41,400).
  29. : Official registry passed 40,000 servers (40,758).
  30. : Census launched. 39,238 servers in the official registry, 32,944 GitHub repos tagged mcp-server.

What the numbers do not show

Downloads are not users. npm and PyPI count every install, including CI runs, container builds and packages that depend on the SDK. The weekly figures say how deeply MCP is built into software, and they are good for comparing trends. They are not a count of people.

Registry size is not the size of the ecosystem. Many servers are never published to any registry, and many listed servers are experiments. Crawlers that index every public endpoint they find report far more than the official registry: on 4 October 2026 Agenstry showed 204,020 MCP servers indexed and 12,579 responding to its live checks, and 7,229 A2A agents with a valid agent card. Those counts answer a different question, how much is out there, while the registry answers how fast publishers are choosing to list.

A vendor announcement is not a product you can use today. Some A2A rows record a preview or a "coming soon". The table dates the first announcement because that is the verifiable event.

I run Gravity, an agent platform in public beta, and agents on it call tools, so MCP's adoption matters to me in a practical way. I have no stake in which protocol wins, and the page reports both on the same footing. For what agent platforms charge, see the AI agent pricing index and the cheapest AI agent platforms.

Methodology

  • Registry size: every server in the official registry's public /v0/servers API, latest version of each, read daily and paged to the end. Growth uses each server's first-publish date: for servers listed on 4 October 2026, the earliest publish date of any version (from a full crawl of all 132,432 published versions); for servers that appear later, the day this tracker first sees them. Servers removed from the registry before 4 October 2026 are not counted, so early months may read slightly low.
  • Smithery: the totalCount its public registry API returns, read daily.
  • SDK downloads: daily counts from the npm downloads API for @modelcontextprotocol/sdk and @a2a-js/sdk, and from ClickPy, ClickHouse's public copy of the PyPI download logs, for mcp, fastmcp and a2a-sdk. The PyPI name mcp belonged to an unrelated package before the SDK took it over, so the series starts in November 2024. Weekly figures are the last seven complete days; year-on-year compares with the seven days ending 364 days earlier.
  • GitHub: repository search counts for the topics mcp-server, model-context-protocol, mcp, a2a-protocol and a2a, read daily. The monthly history in the CSV counts repos that exist today by the month they were created, so deleted repos and topics added later blur it slightly. Stars on the spec and SDK repos come from the GitHub GraphQL API.
  • Vendor support: checked by hand against each vendor's own blog, docs, changelog or press release, or the protocol's official announcement; the date of the latest check is in the note under the vendor table. A row says "Not confirmed" when I found no primary source. Corrections are welcome at support@gravity.fast with the source link.

The refresh runs daily. Sibling dataset: the open-source AI agent framework leaderboard uses the same collector for the main open-source agent frameworks. For broader numbers on agents, see AI agent statistics for 2026.

FAQ

How many MCP servers are there?

It depends on who counts. The official MCP Registry listed 65,877 servers on 17 November 2026. Smithery listed 20,751. Crawlers that index every public endpoint they can find report far more: on 4 October 2026 Agenstry showed 204,020 MCP servers indexed, of which 12,579 responded to its live checks. GitHub had 44,430 public repos tagged mcp-server. The registry is the only count that grows through deliberate publishing, which is why this page tracks it daily.

Is MCP adoption still growing?

Yes, on every measure this page tracks. 20,970 of the 65,877 servers in the official registry were first published in the 30 days to 17 November 2026, and October 2026 added 16,156, the largest month on record. The MCP TypeScript SDK's npm downloads are +969% on the same week a year earlier and the Python SDK's are +493%; GitHub repo counts are in the headline numbers above.

How does A2A adoption compare with MCP?

MCP is far ahead on developer adoption. In the week to 15 November 2026 the MCP TypeScript SDK was downloaded about 89.5 million times from npm against about 6.8 million for the A2A JavaScript SDK, and GitHub had 44,430 repos tagged mcp-server against 640 tagged a2a-protocol. A2A's support comes mostly from enterprise platforms such as Google, Microsoft, AWS, IBM, Salesforce, SAP, ServiceNow and Oracle, which ship it inside their agent products.

Which companies support MCP?

Of the 23 vendors in the support table, 22 have a dated primary source for MCP support, including Anthropic, OpenAI, Google, Microsoft, AWS, Meta, Mistral AI, xAI, Cohere, IBM, Salesforce, SAP, ServiceNow, GitHub and Hugging Face. The one exception is DeepSeek, for which no official MCP client, server or announcement was found. Each row links to the vendor's own announcement or docs.

Do download counts measure how many people use MCP?

No. npm and PyPI count every install, including CI pipelines, container builds and other packages that depend on the SDK. The counts measure how deeply the SDKs are built into software. They are useful for trends and comparisons, such as MCP against A2A, and not as a count of users.

Where does the data come from, and can I reuse it?

From public APIs, read daily: the official MCP Registry, Smithery's registry, the npm downloads API, ClickPy's copy of the PyPI download logs, and the GitHub search and GraphQL APIs. Vendor support rows are checked by hand against primary sources. Everything is published under CC BY 4.0, with a CSV of the monthly series.

Sources

  1. Official MCP Registry API (/v0/servers), read daily from 4 October 2026; full version crawl on 4 October 2026.
  2. Introducing the MCP Registry, MCP blog, 8 September 2025.
  3. Smithery registry API (registry.smithery.ai/servers), read daily.
  4. npm download counts API, daily counts since November 2024.
  5. ClickPy, ClickHouse's public dataset of PyPI downloads, daily counts since November 2024.
  6. GitHub search API and GraphQL API, read daily.
  7. Agenstry index counts, read 4 October 2026.
  8. Introducing the Model Context Protocol, Anthropic, 25 November 2024.
  9. Announcing the Agent2Agent Protocol (A2A), Google for Developers, 9 April 2025.
  10. Linux Foundation announces the Agentic AI Foundation, 9 December 2025.
  11. Vendor announcements: linked row by row in the vendor table; the date of the latest check is in the table note.