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
Enables AI agents to interact with Amazon Web Services through the Model Context Protocol. Provides access to core AWS services including S3, Lambda, DynamoDB, CloudWatch, and IAM. Supports resource discovery, log analysis, and infrastructure management with proper credential handling and region awareness.
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 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.