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

Source references

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

Robin Cartier perspective

This page is part of Robin Cartier's working AI knowledge graph: a practical research layer for production AI, recommendation systems, experimentation, GEO, and agentic web readiness.

The useful next step is to connect this concept back to applied product leadership and operating models.

Recommended next

Keep reading from this thread

From 500 indexed pages and articles.

  1. Wiki concept Gateway MCP Pattern Tool-access architecture where the agent sees one small MCP router while backend service schemas are loaded or invoked lazily. Related by nexus
  2. Wiki concept Tool Schema Tax The fixed context cost paid when an agent runtime injects tool schemas into every prompt, regardless of whether those tools are used in Related by gateway
  3. Wiki concept G/N Ratio Tool Selection Decision framework for choosing between CLI, on-demand skill files, Gateway MCP, and Native MCP by estimating how often a service is actually Related by gateway