What is an MCP server?
An MCP server is a program built on the Model Context Protocol that wraps a tool, data source, or API — like file access, a database, or web search — into a capability an AI assistant can discover and call.
Discover awesome MCP servers.
modelcontextprotocol
Visual testing tool for MCP servers
modelcontextprotocol
A community driven registry service for Model Context Protocol (MCP) servers.
Anthropic
Control Google Chrome browser tabs, windows, and navigation
Anthropic
Let Claude access your filesystem to read and write files.
Anthropic
Simple MCP server using UV runtime
Model Context Protocol
A reference MCP extension demonstrating best practices and all available features
modelcontextprotocol-ce
A MCP server to interact with Server Clipboard, research purpose only!
Model Context Protocol
A simple calculator MCP server compiled from Rust
Anthropic
A Python MCP server for file operations
Common questions about MCP servers, tools, and integrations
An MCP server is a program built on the Model Context Protocol that wraps a tool, data source, or API — like file access, a database, or web search — into a capability an AI assistant can discover and call.
Every server's detail page includes ready-to-paste config snippets for Claude Desktop, Cursor, VS Code, and other common clients — most installs take just a couple of minutes.
Most servers listed here are free and open source. Some wrap third-party APIs (cloud services, paid data providers, etc.) that require your own API key or subscription.
A local MCP server runs on your device and usually connects over stdio, giving you more direct control over data but requiring a runtime and installation. A remote MCP server is hosted by a provider and connects over HTTP, making setup easier while adding network and provider availability dependencies.
Claude Desktop, Claude Code, Cursor, VS Code, Codex, and other AI clients that support the Model Context Protocol can connect to MCP servers. Configuration formats and supported transports vary by client.
Review the source repository, maintenance activity, dependencies, requested permissions, and data-handling documentation before installation, and prefer official or trusted maintainers. Use least-privilege credentials for sensitive access such as files, databases, shells, and production systems.