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
177
Tools
471
Categories
11
Contributors
155
Provides AI agents with access to ClickHouse analytical databases through the Model Context Protocol. Enables running analytical queries, exploring table schemas, inspecting materialized views, and monitoring query performance. Designed for OLAP workloads with support for large result sets and query profiling.
MCP server for interacting with a Tinybird Workspace from any MCP client. Lets AI agents explore data sources, call published API endpoints, run SQL queries over real-time data, and push datafiles, making Tinybird's analytics readily available to LLM-driven workflows.
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.