How to Integrate MCP Servers with Claude Desktop: A Complete Configuration Guide

Integrating MCP servers with Claude Desktop requires selecting a compatible server from the catalog, launching it locally via npm or Docker, and adding the server's HTTP endpoint to Claude Desktop's MCP Servers settings panel.

The awesome-mcp-servers repository on GitHub maintains a comprehensive registry of open-source Model Context Protocol servers, many explicitly tested with Claude Desktop to extend its capabilities with external APIs, databases, and browser automation. According to the README.md source code, this integration follows a standardized three-step workflow that connects Claude's natural-language interface to custom toolchains through JSON-RPC endpoints.

Selecting a Claude-Compatible MCP Server

Before configuration, identify a server that provides your required toolset. The README.md file in the punkpeye/awesome-mcp-servers repository categorizes servers by compatibility, with several entries explicitly optimized for Claude Desktop integration.

Option 1: WayStation-ai Gateway

WayStation-ai/mcp provides a "one-click" gateway that bundles popular SaaS integrations including Notion, Slack, and Airtable into a single endpoint. According to the source catalog, this reduces setup complexity by exposing multiple services through one JSON-RPC interface.

# Install and launch via npx (requires Node.js ≥18)

npx -y @waystation/mcp

# Server starts on http://localhost:3000/mcp

Option 2: ViperJuice Meta-Server

ViperJuice/mcp-gateway functions as a dynamic meta-server that provisions additional MCP servers on-demand, reducing initial tool bloat in Claude Desktop's interface. This approach delays loading specific tools until they are requested, improving startup performance.

Other Claude-specific entries in the README.md catalog include Claude-skills-mcp, Claude-for-Safari, and various SQLite tutorial implementations, each marked with explicit "Claude" compatibility tags.

Running the MCP Server Locally

Most servers in the repository distribute as npm packages, Python wheels, or Docker images. The README.md specifies that servers must expose a JSON-RPC endpoint and a manifest file that Claude Desktop can discover automatically.

# Python-based server example (Claude-skills-mcp)

pip install claude-skills-mcp
claude-skills-mcp --host 0.0.0.0 --port 8080

The server will expose:

• JSON-RPC Endpoint: Typically http://localhost:3000/mcp or http://localhost:8080/mcp
• Manifest: Either /mcp_manifest.json or /.well-known/ai-market.json describing available tools, input schemas, and cost metadata

Configuring Claude Desktop Settings

Once the local server is running, configure the connection through Claude Desktop's interface.

Adding Server Details

Navigate to Claude Desktop → Settings → MCP Servers, then click "Add Server" and populate the following fields:

• Name: Descriptive label (e.g., "WayStation-ai" or "Local SQLite")
• URL: The HTTP endpoint shown by your running server (e.g., http://localhost:3000/mcp)
• Authentication: Leave blank for local development; paste JWT or API key if the server README requires token-based auth

Example Configuration:
Name: WayStation Gateway
Endpoint: http://localhost:3000/mcp
Auth: (empty for local development)

Manifest Discovery

Upon saving, Claude Desktop automatically fetches the server's tool manifest from the /.well-known/ai-market.json or /mcp_manifest.json path. This populates the Toolbox UI with available functions like create_notion_page, send_slack_message, or list_tasks, enabling autocomplete and schema validation for tool arguments.

Invoking Tools from the Chat Interface

After configuration, tools appear as native capabilities within Claude's chat interface. You invoke them through natural language, and Claude Desktop translates these requests into structured JSON-RPC calls to your local server.

User: "Create a new Notion page titled 'Project Roadmap' and add a bullet list with milestones."
Claude: [Auto-detects create_notion_page tool → sends JSON-RPC call to localhost:3000]
Claude: "Your page has been created at https://www.notion.so/..."

The MCP server handles all business logic, database connections, and third-party API calls, while Claude Desktop acts as a thin presentation layer that formats responses for the conversation.

Key Architectural Components

Component	Role	Interaction with Claude Desktop
MCP Server	Implements MCP JSON-RPC spec (list, get, call methods) wrapping concrete APIs	Receives HTTP POST requests with JSON-RPC payloads; returns typed tool definitions and execution results
Manifest File	Located at /mcp_manifest.json or /.well-known/ai-market.json; describes tool schemas and metadata	Read by Claude Desktop on startup to populate the Toolbox UI and validate tool inputs
Claude Desktop	MCP client translating natural language to structured calls	Routes user requests to appropriate server endpoints and renders responses in chat

Summary

• Selection: Reference README.md in punkpeye/awesome-mcp-servers to find Claude-compatible servers like WayStation-ai or ViperJuice gateway
• Execution: Launch servers via npx, pip, or Docker to expose JSON-RPC endpoints on localhost
• Configuration: Add the local endpoint to Claude Desktop's Settings → MCP Servers without requiring authentication for development environments
• Operation: Claude Desktop reads the server's manifest to discover tools, then routes natural-language requests to the appropriate JSON-RPC endpoints

Frequently Asked Questions

What file formats does Claude Desktop require for MCP server configuration?

Claude Desktop does not require local configuration files; instead, it reads the manifest (/.well-known/ai-market.json or /mcp_manifest.json) directly from the running server's HTTP endpoint. This JSON file, as documented in the README.md source, contains tool definitions, input schemas, and cost metadata that Claude uses to populate its interface.

Can I run multiple MCP servers simultaneously with Claude Desktop?

Yes. The README.md catalog indicates that Claude Desktop supports multiple concurrent server connections. You can add several endpoints in Settings → MCP Servers, such as http://localhost:3000/mcp for WayStation-ai and http://localhost:8080/mcp for a Python-based SQLite server. Claude aggregates all tools from connected servers into a unified Toolbox.

Do I need authentication for local MCP servers?

Most local development servers listed in punkpeye/awesome-mcp-servers run unauthenticated on localhost. The repository's CONTRIBUTING.md guidelines suggest that authentication (JWT or API keys) is only required when connecting to remote production instances; local servers typically operate without tokens to streamline development workflows.

Where can I find additional language-specific examples?

The repository includes translated documentation in README-zh.md and other localization files that mirror the English catalog. For codebase-level contributions or advanced integration patterns, consult CONTRIBUTING.md, which outlines how to submit new Claude-compatible servers to the registry.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}