Building and Connecting an MCP Server to Claude Desktop

Description and use

Building and connecting an MCP server to Claude Desktop enables developers to quickly integrate external resources and tools into LLMs without writing separate adapters.

Problem

Developers need a standardized way to expose external resources and tools to LLM hosts like Claude Desktop without writing custom adapters for each integration.

Outcome

After following the workflow, developers can run an MCP server locally or expose it publicly, register it with Claude Desktop, and leverage real‑time file access, memory, and tool invocation without writing custom adapters.

Workflow

• 1. Install Claude Desktop and enable MCP/Extensions in settings.
• 2. Prepare a development environment (Node.js ≥16 or Python 3.10+, optional ngrok).
• 3. Clone the reference MCP servers from https://github.com/modelcontextprotocol/servers or create a new project folder.
• 4. If cloning, navigate to a server folder (e.g., memory), run npm install and npm run dev to start the server (default http://localhost:3000).
• 5. If creating a new server, run npm init -y, npm install @modelcontextprotocol/server, and create a server.js with a minimal tool implementation.
• 6. Start the server with node server.js and verify the manifest endpoint and tool response.
• 7. Open Claude Desktop → Settings → Developer (or Connectors).
• 8. For local testing, locate or create claude_desktop_config.json in the appropriate OS folder and add the server manifest URL or token.
• 9. Grant any requested permissions in the client prompt.
• 10. Verify the server appears in the MCP/Extensions panel and can be used in prompts.

Evidence

MCP has moved quickly from concept to practical ecosystem: an open specification and multiple reference servers are available

Source

Claude Desktop settings → Developer (or Connectors) to add a remote/local MCP server

Source