MCP.so
Sign In

Claude MCP Configuration

@carloslluberes

Basic information

Category

AI & Agents

Transports

stdio

Author

carloslluberes

About Claude MCP Configuration

Working MCP server configurations for Claude - 16 servers functional

Claude MCP Configuration config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Claude MCP Configuration tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

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.

Frequently asked questions

1

Which servers use `npx -y`?

12 servers in the configuration use `npx -y` as their command type.

2

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.

3

What command does the Mailgun server use?

The Mailgun server uses `node`.

4

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.

5

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.

Comments

More AI & Agents MCP servers