I maintain Bifrost (OSS MCP Gateway), and we’ve been using it a lot with Claude Code lately. Thought I’d share something that became obvious once we started scaling agentic coding setups. Claude Code + MCP tools is great… until you have a bunch of servers and integrations floating around. What we ended up doing was putting an MCP gateway in the middle so Claude Code connects once, and everything else sits behind it. This is what that changed in practice: First, tool access becomes centralized. Instead of wiring filesystem MCP, database MCP, internal APIs, etc directly into Claude Code, we connect them to the gateway. Claude Code just talks to one endpoint and all tools show up automatically. Second, you’re not locked to one model anymore. Claude Code sends requests in Anthropic format, and the gateway can route that to other providers if needed. Makes it easier to experiment with different models without changing your dev setup. Another big one: observability. When everything flows through a gateway, you can actually see what the agent is doing. Requests, tool calls, tokens, latency. Debugging agent workflows gets way easier. And once you start using multiple MCP servers, orchestration becomes the real challenge. We’ve been leaning on Code Mode where the model writes code to coordinate tools instead of juggling dozens of schemas directly. That cuts token usage a lot and scales better when you add more servers. Net effect: Claude Code still feels the same from the outside, but under the hood you get centralized tools, model routing, governance, and better scaling for agentic workflows. If you want to check it out: Code: https://git.new/bifrost Docs: https://getmax.im/docspage submitted by /u/dinkinflika0
Originally posted by u/dinkinflika0 on r/ClaudeCode
You must log in or # to comment.