Nexus-Dev Gateway

Gateway-style MCP tool router described in ^[src-041]. Instead of injecting every backend tool schema into the agent’s prompt, Nexus-Dev exposes a small routing interface and loads service-specific schemas lazily when the agent actually needs them.

Key facts

• Type: MCP gateway / tool router
• Pattern: Single router schema in context, backend schemas loaded on demand
• Measured fixed overhead: about 20 tokens in the article’s GitHub experiment ^[src-041]
• Trade-off: Slightly higher per-call envelope cost than native MCP, but far lower idle cost across multi-service sessions ^[src-041]

Why it matters

Nexus-Dev represents the Gateway MCP Pattern: keep MCP-quality structured outputs, but avoid paying the full Tool Schema Tax for every connected service on every prompt.

Related concepts

• Gateway MCP Pattern
• G/N Ratio Tool Selection
• MCP vs CLI Token Trade-off
• Model Context Protocol (MCP)

Source references

• ^[src-041] Marco Mornati — “The Future of Agentic Tooling: MCP Servers vs. CLI A Data-Driven Comparison” (2026-04-27)