The MCP Discovery Problem and Why Compatibility Matrices Matter
The MCP Discovery Problem and Why Compatibility Matrices Matter
The idea of an App Store for MCP integrations is overdue. But the real challenge is not building the marketplace - it is solving the discovery and compatibility problem that makes MCP adoption harder than it needs to be.
The Discovery Problem
Right now, finding MCP servers means searching GitHub, reading blog posts, or asking in Discord servers. There is no central registry. No standardized way to describe what a server does, what permissions it needs, or what clients it works with.
This means developers waste hours evaluating servers that turn out to be incompatible with their setup. You find a promising MCP server for database access, clone it, configure it, and discover it only works with Claude Desktop but not with your preferred client. That is time you do not get back.
Why a Compatibility Matrix Is Essential
Not all MCP clients implement the full spec. Some support tool calling but not resource subscriptions. Some handle stdio transport but not SSE. Some support prompt templates, others do not.
A compatibility matrix would show at a glance:
- Which clients the server has been tested with
- Which transport protocols it supports
- Which MCP features it uses (tools, resources, prompts, sampling)
- Which versions of the protocol it targets
Without this information, every MCP server installation is a gamble. You do not know if it will work until you try it, and debugging compatibility issues across the MCP protocol is not trivial.
What a Good MCP Registry Needs
Beyond compatibility, an effective registry needs:
- Security audits - MCP servers get access to your system, so trust matters
- Usage metrics - which servers are actually being used vs abandoned
- Configuration templates - copy-paste configs for popular clients
- Version tracking - know when a server updates and if it breaks compatibility
The MCP ecosystem is growing fast. Without proper discovery and compatibility tooling, it risks fragmenting into incompatible islands of functionality.
Fazm is an open source macOS AI agent. Open source on GitHub.