MCP Directory
Back to Directory

MCP Servers for Claude

Configure MCP servers in Claude Desktop using claude_desktop_config.json.

Claude Desktop is one of the most widely documented MCP clients. Anthropic ships native MCP support in the desktop app, and the official Model Context Protocol servers repository documents the exact configuration format you need. WHAT IS MCP IN CLAUDE DESKTOP? Model Context Protocol (MCP) lets Claude Desktop launch external tools — file readers, memory stores, Git helpers, and more — as separate processes that Claude can call during a conversation. Each server exposes tools (and sometimes resources or prompts) over stdio. Claude Desktop reads a JSON config file, starts the listed servers when you open the app, and routes tool calls to them. PREREQUISITES Before editing your config, install the runtime each server needs: - Node.js 18 or newer for TypeScript reference servers started with npx (Filesystem, Memory, Sequential Thinking, Everything). - uv / uvx for Python reference servers (Git, Fetch, Time). Install uv from https://docs.astral.sh/uv/getting-started/installation/ Verify Node: node --version Verify uvx: uvx --version CONFIG FILE LOCATION Claude Desktop stores MCP settings in claude_desktop_config.json: - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - Windows: %APPDATA%\Claude\claude_desktop_config.json - Linux: ~/.config/Claude/claude_desktop_config.json If the file does not exist, create it with an empty mcpServers object and add entries below. OFFICIAL CONFIG FORMAT The official modelcontextprotocol/servers README shows this pattern (commands verified from that repository): { "mcpServers": { "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] } } } WINDOWS NOTE FOR NPX On Windows, wrap npx with cmd /c as documented in the official README: { "mcpServers": { "memory": { "command": "cmd", "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"] } } } Leave uvx-based servers unchanged — only npx entries need the cmd wrapper on Windows. EXAMPLE: FILESYSTEM + MEMORY This example adds two official reference servers. Filesystem requires at least one allowed directory path. Replace paths with directories you trust Claude to read and write. macOS / Linux: { "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects" ] }, "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] } } } Windows: { "mcpServers": { "filesystem": { "command": "cmd", "args": [ "/c", "npx", "-y", "@modelcontextprotocol/server-filesystem", "C:\\Users\\you\\projects" ] }, "memory": { "command": "cmd", "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"] } } } Standalone install commands from the official repo (for testing in a terminal): npx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir npx -y @modelcontextprotocol/server-memory APPLYING CHANGES 1. Quit Claude Desktop completely (check the system tray on Windows). 2. Save claude_desktop_config.json with valid JSON (no trailing commas). 3. Relaunch Claude Desktop. 4. Start a new conversation and look for the MCP / tools indicator showing connected servers. TROUBLESHOOTING - Invalid JSON: Claude may silently ignore the config. Validate JSON in an editor first. - Server fails to start: Run the same command in a terminal to see stderr (missing Node, wrong path, permission denied). - Filesystem errors on startup: The server requires at least one allowed directory via args or MCP Roots from a capable client. - Windows path issues: Use double backslashes in JSON or forward slashes. SECURITY Official reference servers are educational examples, not production-hardened services. Scope filesystem access to project folders only. Memory persists data locally — understand where it stores the knowledge graph on disk. Review each server's README in the modelcontextprotocol/servers repository before granting access to sensitive paths. FURTHER READING - Official servers README: https://github.com/modelcontextprotocol/servers - MCP specification and client concepts: https://modelcontextprotocol.io - Claude Desktop MCP documentation (may update independently): check Anthropic's latest docs for UI changes.

Browse by category

File System

MCP servers that provide file system access for reading, writing, and managing files and directories. Enable AI assistants to interact with your local or remote file systems safely.

Databases

MCP servers for database operations including PostgreSQL, MySQL, SQLite, and MongoDB. Query, manage, and introspect databases directly from your AI assistant.

Web Search

MCP servers that provide web search capabilities. Enable AI assistants to search the web, retrieve real-time information, and access current data.

Developer Tools

MCP servers for developer productivity including code analysis, version control, CI/CD, and development environment integration.

Cloud Services

MCP servers for AWS, Azure, GCP, Cloudflare, Vercel and other cloud platforms.

Automation

Browser automation, scraping and workflow MCP servers for repetitive tasks.

AI & ML

Memory, reasoning, RAG, embeddings and machine-learning MCP servers.

Communication

Slack, Discord, email and messaging MCP servers for team communication.

Productivity

Notes, docs, calendars and task-management MCP servers.

Monitoring

Observability, logs, metrics and alerting MCP servers.

Security

Auth, secrets management and security tooling MCP servers.

Data Processing

ETL, analytics and data-pipeline MCP servers.