Ecosystem insights

What the MCP ecosystem actually wires up, observed across public repositories that committed a client config. Public data — every number is re-derivable; repositories that opt out of listing are counted but never named.

13,665
Servers catalogued
6,605
Observed in the wild
referenced by a real repo
5,890
Consumer repositories
18,218
Usage edges
config placements

Most-adopted servers

by distinct public repositories

How servers are distributed

identity kind of referenced servers
  • npm (1794)2,735 (34%)
  • local command (3273)2,606 (32%)
  • remote endpoint (748)1,281 (16%)
  • PyPI (622)1,130 (14%)
  • OCI / Docker (168)273 (3%)

Bar width is by repos observed; the count in parentheses is distinct servers of that kind. A registry keyed only on npm would miss the majority — local commands, remote endpoints, PyPI and Docker servers all show up here.

Client landscape

which agent clients commit these configs
  • unknown2,624 repos
  • claude-code1,531 repos
  • kiro763 repos
  • cursor436 repos
  • claude-desktop313 repos
  • windsurf148 repos
  • cline102 repos
  • vscode99 repos
  • kilocode24 repos
  • continue7 repos

Frequently used together

server pairs sharing the most repositories