MCP is quickly becoming the standard for agentic systems, but… once you go past a couple servers it turns into the same problems for every team:
- M×N config sprawl (every client wired to every server, each with its own JSON + ports + retries) - Token + tool bloat (dumping tool definitions into every prompt doesn’t scale) - Credentials + blast radius (tokens scattered across clients, hard to audit, hard to revoke) - No single place to debug (latency, errors, “what tool did it call, with what params?”)
MCP Mesh sits between MCP clients and MCP servers and collapses that mess into one production endpoint you can actually operate.
What it does:
- One endpoint for Cursor / Claude / VS Code / custom agents → all MCP traffic routes through the mesh - RBAC + policies + audit trails at the control plane (multi-tenant org/workspace/project scoping) - Full observability with OpenTelemetry (traces, errors, latency, cost attribution) - Runtime strategies as “gateways” to deal with tool bloat: Full-context (small toolsets), Smart selection (narrow toolset before execution), Code execution (load tools on-demand / run code in a sandbox) - Token vault + OAuth support, proxying remote servers without spraying secrets into every client - MCP Apps + Bindings so apps can target capability contracts and you can swap MCP providers without rewriting everything
A small but surprisingly useful thing: the UI shows every call, input/output, who ran it, and lets you replay calls. This ended up being our “Wireshark for MCP” during real workflows.
It’s open-source + self-hosted (run locally with SQLite; Postgres or Supabase for prod).
You can start with `npx @decocms/mesh` or clone + run with Bun.
We’d love your feedback!
Links below:
Repo: https://github.com/decocms/mesh
Landing: https://www.decocms.com/mcp-mesh
Blog post: https://www.decocms.com/blog/post/mcp-mesh
edit: layout
No comments yet.
