What MCP servers provide
MCP servers expose:- Tools — Actions Claude can invoke (e.g., query a database, call an API)
- Resources — Data Claude can read (e.g., files, database rows, documents)
- Prompts — Reusable prompt templates
Managing MCP servers
Use the/mcp command to manage server connections:
Adding a server
Configure the server
For stdio servers, provide the command to launch the server process.
For HTTP servers, provide the endpoint URL.
Server types
stdio servers
Local processes that communicate over stdin/stdout. Most MCP servers are stdio-based:HTTP servers
Remote servers accessible over HTTP/HTTPS. Claude Code connects to the MCP endpoint URL.Using MCP tools
Once a server is connected, its tools appear alongside Claude Code’s built-in tools. Claude selects the right tool automatically based on context:Official MCP servers
Claude Code can connect to servers from the official MCP registry. Run/mcp to browse available official servers.
Popular official servers include integrations for:
- Filesystem access
- GitHub
- Databases (PostgreSQL, SQLite)
- Slack
- Browser automation
MCP resources
Beyond tools, MCP servers can expose resources that Claude reads directly:ListMcpResourcesTool and ReadMcpResourceTool — Claude invokes these automatically when accessing MCP resources.
MCP server connections are scoped to your user account, not the project. Servers you add are available across all your Claude Code sessions.
Troubleshooting
Run/doctor to check MCP server connectivity. If a server shows as disconnected, verify the server process is running and the configuration is correct.
See MCP Protocol for details on building your own MCP server.