mcpd-proxy

What it does

mcpd-proxy acts as a unified MCP gateway between your IDE (VS Code, Cursor, etc.) and the mcpd daemon. Instead of configuring each MCP server individually in every editor, you run mcpd to manage your servers and point your IDE at this single proxy. It aggregates all tools, resources, and prompts across every mcpd-managed server into one MCP interface.

The architecture is: IDE ↔ mcpd-proxy (stdio/MCP) ↔ mcpd daemon (HTTP/REST) ↔ individual MCP servers.

Tools

The proxy dynamically exposes tools from all connected mcpd servers using a server__tool naming convention to prevent collisions:

• time__get_current_time — from the time server
• github__create_issue — from the github server
• fetch__get_url — from the fetch server

Same convention applies to resources (mcpd://server/resource_uri) and prompts (server__prompt_name). The full tool list is determined at runtime by whatever mcpd has registered.

Installation

npx @mozilla-ai/mcpd-proxy

VS Code — add to your MCP settings file:

{
  "servers": {
    "mcpd": {
      "type": "stdio",
      "command": "npx",
      "args": ["@mozilla-ai/mcpd-proxy"],
      "env": { "MCPD_ADDR": "http://localhost:8090" }
    }
  }
}

Cursor — create/edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "mcpd": {
      "command": "npx",
      "args": ["@mozilla-ai/mcpd-proxy"],
      "env": { "MCPD_ADDR": "http://localhost:8090" }
    }
  }
}

Requires mcpd daemon running at the configured address (default: http://localhost:8090).

Supported hosts

VS Code Copilot and Cursor are explicitly documented in the README with config examples.