MCP server proxy for mcpd daemon
Most developer tooling work still happens through a UI a human drives. Mcpd MCP server moves it into the conversation instead. MCP server proxy for mcpd daemon.
An MCP (Model Context Protocol) server that acts as a proxy between IDEs and the mcpd daemon, exposing all mcpd-managed MCP servers through a unified interface.
mcpd-proxy aggregates tools, resources, and prompts from multiple MCP servers managed by mcpd into a single MCP interface, making it easy for IDEs to access all capabilities without managing individual server connections.
The server publishes 6 tools. What each one is for:
time__get_current_time — get_current_time tool from time servergithub__create_issue — create_issue tool from github serverfetch__get_url — get_url tool from fetch serverTools — This naming convention prevents tool name collisions between servers and makes it clear which server provides each toolResources — Resources use a custom URI scheme: mcpd://{server}/{resource_uri}Prompts — Prompts follow the same naming convention as tools: {server}__{prompt_name}The server ships on npm as npx, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: MCPD_ADDR, MCPD_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Node.js 22.10.0 or higher (latest 22.x recommended) - mcpd daemon running and accessible - mcpd SDK (automatically installed as a dependency)This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mcpd's toolset — time__get_current_time, github__create_issue, fetch__get_url and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| time__get_current_time | get_current_time tool from time server |
| github__create_issue | create_issue tool from github server |
| fetch__get_url | get_url tool from fetch server |
| Tools | This naming convention prevents tool name collisions between servers and makes it clear which server provides each tool. |
| Resources | Resources use a custom URI scheme: mcpd://{server}/{resource_uri} |
| Prompts | Prompts follow the same naming convention as tools: {server}__{prompt_name} |
{
"mcpServers": {
"mcpd": {
"command": "npx",
"args": ["@mozilla-ai/mcpd-proxy"],
"env": {
"MCPD_ADDR": "http://localhost:8090"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Node.js 22.10.0 or higher (latest 22.x recommended) - mcpd daemon running and accessible - mcpd SDK (automatically installed as a dependency)| Variable | Description | Required |
|---|---|---|
| MCPD_ADDR | Configuration value read at startup. | Optional |
| MCPD_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.