MCP server for Claude Code — multi-AI orchestration across local + cloud LLMs, intelligent backend routing, council-driven workflows, and
Connect Smart Ai Bridge to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Claude Code — multi-AI orchestration across local + cloud LLMs, intelligent backend routing, council-driven workflows, and token-saving file operations. The smart ai bridge mcp server is what makes that connection.
Smart AI Bridge is an MCP server that sits between Claude Code and your AI backends. It provides 18 tools for token-saving file operations, multi-AI workflows, code quality checks, and intelligent routing -- all configured through a single JSON file.
The server ships on npm as vitest, 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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Infrastructure — The Infrastructure tool exposed by this serverEnable — The Enable tool exposed by this serverConfiguration is passed through the environment: NVIDIA_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, GROQ_API_KEY, CRUSH_EVAL_BASE_URL, MY_PROVIDER_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.
Plenty of cloud and infrastructure 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. Smart Ai Bridge's toolset — Infrastructure, Enable — is a fair guide to whether it matches your workflow. It is maintained by platano78; 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 |
|---|---|
| Infrastructure | The Infrastructure tool exposed by this server. |
| Enable | The Enable tool exposed by this server. |
{
"mcpServers": {
"smart-ai-bridge": {
"command": "npx",
"args": ["-y", "vitest"],
"env": {
"NVIDIA_API_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"GEMINI_API_KEY": "your-value",
"GROQ_API_KEY": "your-value",
"CRUSH_EVAL_BASE_URL": "your-value",
"MY_PROVIDER_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NVIDIA_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| GROQ_API_KEY | Credential the server authenticates with. | Yes |
| CRUSH_EVAL_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MY_PROVIDER_API_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.