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
160
Tools
465
Categories
11
Contributors
142
MCP server for DuckDB, the fast in-process analytical database. Lets AI agents run analytical SQL over local files (CSV, Parquet, JSON), attach databases, inspect schemas, and profile queries. Ideal for ad-hoc data analysis, ETL prototyping, and querying large columnar files without a separate database server.
Official MCP server for DuckDB and MotherDuck. Lets AI assistants run SQL analytics directly against local DuckDB files, in-memory databases, S3-hosted data, and MotherDuck cloud warehouses. Supports read and write queries, browsing database catalogs, and switching between connections on the fly, making it well suited for conversational data exploration and lightweight analytics.
Skills vs MCP servers
what's the difference?Skillsthe “what to do”
A skillA reusable, structured prompt/workflow with recommended models, an example prompt, and compatible tools. packages know-how — instructions, an example promptA ready-to-use prompt template that demonstrates how to invoke the skill., and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP serverModel Context Protocol server — a standard way to expose tools, resources, and prompts to AI agents and IDEs. gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transportHow the client talks to the server: stdio (local process), SSE, or HTTP streaming.. 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.