Claude MCP Configuration
@carloslluberes
About Claude MCP Configuration
Working MCP server configurations for Claude - 16 servers functional
Basic information
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Claude MCP Configuration?
This repository contains the working configuration for Claude MCP servers after extensive testing, including 16 validated servers. It is intended for users setting up the Claude desktop application with Model Context Protocol servers, providing configuration files and a guide detailing command types, lessons learned, and error avoidance.
How to use Claude MCP Configuration?
Use claude-desktop-config.json as your working configuration. Consult MCP-WORKING-CONFIG-GUIDE.md for step‑by‑step setup and lessons learned, and server-command-reference.json to quickly determine the correct command (npx, uvx, or node) for each server.
Key features of Claude MCP Configuration
- 16 working MCP servers validated in a single configuration.
- Three command types documented: NPX (12 servers), UVX (3 servers), NODE (1 server).
- Detailed guide with critical lessons learned during integration.
- Quick‑reference JSON for server‑to‑command mapping.
- Explicit warnings about command type mismatches (e.g., fetch, time, cli must use uvx).
Use cases of Claude MCP Configuration
- Setting up Claude desktop with a reliable, pre‑tested set of MCP servers.
- Avoiding common failures by referencing the command‑type matrix before adding servers.
- Troubleshooting MCP server failures by consulting the documented lessons and known pitfalls.
FAQ from Claude MCP Configuration
Which servers use npx -y?
12 servers in the configuration use npx -y as their command type.
Which servers must use uvx?
Three servers (fetch, time, and cli) require the full path /Users/carloslluberes/.local/bin/uvx and will fail if run with npx.
What command does the Mailgun server use?
The Mailgun server uses node.
What were the two server failures encountered?
The desktop-commander server does not exist under the package name @modelcontextprotocol/server-desktop-commander, and the fetch server fails when invoked with npx instead of uvx.
What is the success rate of the tested configuration?
Starting from 9 servers, 7 were added, for a total of 16 working servers, with 2 known failures out of the attempted servers.
More AI & Agents MCP servers
MCP-LLM Bridge
patruffBridge between Ollama and MCP servers, enabling local LLMs to use Model Context Protocol tools
1Panel
1Panel-dev🔥 1Panel is a modern, open-source VPS control panel — and the only one with native AI agent support. Run Ollama models, deploy OpenClaw agents, and manage your entire server stack from one clean web interface.
Gemini MCP Server
aliargunMCP server implementation for Google's Gemini API
MCP Client for Ollama (ollmcp)
joniglHarness the power of local LLMs with this TUI MCP Client for Ollama. Featuring all core MCP primitives (tools, prompts, resources), agent mode, multi-server, model switching, streaming responses, human-in-the-loop, thinking mode, model params config, system prompts, and saved pre
MCP Server - Remote MacOs Use
baryhuangThe only general AI agent that does NOT requires extra API key, giving you full control on your local and remote MacOs from Claude Desktop App
Comments