Route MCP requests intelligently to multiple backend servers.
Route MCP requests intelligently to multiple backend servers. Exposed over MCP by the mcpware mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
black on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
backend_name — (Optional) Specific backend to queryPrerequisites — The Prerequisites tool exposed by this serveruse_tool — Parameters: - backend_server: Name of the backend server - server_tool: Name of the tool to call - tool_arguments: Arguments to pass to the tooldiscover_backend_tools — Parameters: - backend_name: (Optional) Specific backend to queryYou will need 4 environment variables: GITHUB_PERSONAL_ACCESS_TOKEN, BUILDKITE_API_TOKEN, REDIS_HOST, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty 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. Mcpware's toolset — backend_name, Prerequisites, use_tool and 1 more — is a fair guide to whether it matches your workflow. It is maintained by delexw; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| backend_name | (Optional) Specific backend to query |
| Prerequisites | The Prerequisites tool exposed by this server. |
| use_tool | Parameters: - backend_server: Name of the backend server - server_tool: Name of the tool to call - tool_arguments: Arguments to pass to the tool |
| discover_backend_tools | Parameters: - backend_name: (Optional) Specific backend to query |
{
"mcpServers": {
"mcpware": {
"command": "uvx",
"args": ["black"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-value",
"BUILDKITE_API_TOKEN": "your-value",
"REDIS_HOST": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| BUILDKITE_API_TOKEN | Credential the server authenticates with. | Yes |
| REDIS_HOST | Endpoint or connection string the server talks to. | Optional |
| ANTHROPIC_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.