MCP Servers
The open registry for Model Context Protocol servers. Find the right tools, resources, and prompts for your AI agents — filtered by category, transport, or use case.
Servers
187
Tools
493
Categories
11
Contributors
164
A Model Context Protocol server for Apache Kafka implemented in Go. Lets AI assistants inspect clusters, list and describe topics and consumer groups, produce test messages, and consume recent records, making it easier to debug and operate event-streaming pipelines from natural language.
MCP server for searching and accessing arXiv research papers. Enables AI agents to search papers with filters for date ranges and categories, download full paper content, read papers in markdown format, and perform semantic search across locally stored papers. Supports citation graph exploration via Semantic Scholar and research alert watches for tracking new publications on topics of interest.
Confluent's open-source MCP server that connects AI assistants to Confluent Cloud, Confluent Platform, and standalone Apache Kafka deployments. Provides tools to manage Kafka topics and connectors, work with Schema Registry, and run Flink SQL statements through natural language, helping teams operate streaming data platforms from an MCP client.
Skills vs MCP servers
what’s the difference?Skillsthe “what to do”
A skill packages know-how — instructions, an example prompt, and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP server gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transport. MCP adds connections and actions, not task instructions.
Rule of thumb: reach for a skill when you need the model to do a task well, and an MCP server when you need it to reach a tool or system. They compose — a skill can rely on tools an MCP server provides.
Built an MCP server?
Submit it to the registry — it’s open source and community-maintained.