Your command deck for MCP servers. MCP Deck is an intelligent MCP (Model Context Protocol) router: it spawns your child MCP servers, embeds their
Meta MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Your command deck for MCP servers. MCP Deck is an intelligent MCP (Model Context Protocol) router: it spawns your child MCP servers, embeds their tools, and exposes them to an MCP client through a single connection — either proxying every.
Once Meta MCP is connected, these are the calls the assistant has available:
serve — Run the MCP server over stdio for Claude Desktop/Code (see above)start — Dashboard/full-stack mode with auto-setup + web UI (default command)run — Start the server without auto-setup or config auto-detectionlist-strategies — List available tool-selection strategiesdebug-vector — Run a test query against the vector search indexregenerate-embeddings — Recompute tool embeddings (--force to clear and rebuild)init-config — Write a default mcpdeck.yamlhealth — Check system health and dependenciesThe server ships on PyPI as mcpdeck, 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.
uvx and uv commands used throughout this README. If you only have pipx, run pipx install uv to get uvx. - Docker or Apple Container (macOS Apple Silicon) — needed to run Qdrant, which backs vector-based tool selection. Optional if you only everPlenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Meta MCP's toolset — serve, start, run and 5 more — is a fair guide to whether it matches your workflow. It is maintained by anirudhlath; 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 |
|---|---|
| serve | Run the MCP server over stdio for Claude Desktop/Code (see above) |
| start | Dashboard/full-stack mode with auto-setup + web UI (default command) |
| run | Start the server without auto-setup or config auto-detection |
| list-strategies | List available tool-selection strategies |
| debug-vector | Run a test query against the vector search index |
| regenerate-embeddings | Recompute tool embeddings (--force to clear and rebuild) |
| init-config | Write a default mcpdeck.yaml |
| health | Check system health and dependencies |
{
"mcpServers": {
"mcpdeck": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/anirudhlath/mcpdeck",
"mcpdeck",
"serve",
"--mcp-servers-json",
"/absolute/path/to/mcp-servers.json"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
uvx and uv commands used throughout this README. If you only have pipx, run pipx install uv to get uvx. - Docker or Apple Container (macOS Apple Silicon) — needed to run Qdrant, which backs vector-based tool selection. Optional if you only everKill 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.