MCP Guide
Copy-ready JSON config snippets for common Model Context Protocol reference servers.
Snippets use the mcpServers object format used by Claude Desktop and most MCP clients. Replace /path/… placeholders with real paths on your machine; restart the client after editing.
How to use it
- Scroll the list or search by server name or capability.
- Read the short description so you know what the server does before connecting it.
- Click Copy to put the JSON snippet on your clipboard.
- Paste it into your client's config file, merging it under the existing mcpServers object.
- Replace /path/... placeholders with real paths and API keys, then restart the client.
Common use cases
- First MCP setup - start with the filesystem server and confirm your client loads it.
- Giving agents web access - add fetch or brave-search so the model can read pages or search.
- Repository work - connect the git server so agents can inspect history without shell access.
- Debugging a client - use the everything server, which exercises the full MCP feature set.
Why it stays private
The snippets are embedded in this page and copying runs locally in your browser. The page makes no network requests, and no configuration or key you paste elsewhere is transmitted by this tool.
FAQ
Q: Which config file do these snippets go into? A: For Claude Desktop, the claude_desktop_config.json file documented by Anthropic. Most other MCP clients (editors, CLIs) read an equivalent mcpServers object from their own settings; check your client's docs for the exact file path.
Q: Why do some snippets use npx and others uvx? A: It matches how each reference server is distributed: Node-based servers run through npx, Python-based ones through uvx. Both download on first run, so the first launch may take a moment.
Q: Is it safe to give an agent filesystem access? A: Scope it. The filesystem server only exposes the directories you list in args, so pass the narrowest folder that works - never your home directory - and remember the agent runs with your user's permissions.
Your data stays on this device
MCP Guide runs 100% locally. Everything you paste or drop is processed by your own browser and never transmitted. Nothing is stored on our servers — close the tab and it is gone.
Nothing you type is sent to a server, logged, or used for analytics. The page works even with your network disconnected after first load.