Agentic Gateways

Parent: Agentic.

Agentic Gateways are the front door for agent invocations and MCP tool surfaces: registry, auth, routing, and policy at the agent boundary. Under Agentic they differ from LLM Gateway (models) and complement Agent Protocols (wire formats). If every agent is a private localhost process, you do not have an operable workforce.

Mechanically look for discovery registries, session bridging, multi-tenant isolation, and how tool manifests are published. Failure modes: open MCP ports without identity, registries that drift from running servers, and gateways that rewrite tool schemas silently.

Members include Agent Gateway, FastMCP, Supergateway, and registry/reference packs (MCP Gateway Registry, MCP Registry, MCP Servers (reference)). Prefer a gateway when agents must be called across teams; prefer raw protocols when you are still proving a single tool server.

Features such as APIs, SDKs & MCP Extensibility, Agent Identity & Interoperability, and MCP Tools name the contract: discoverable, authenticated tool/agent surfaces — not ad-hoc SSH into a demo laptop.

Inline members for audit: Agent Gateway FastMCP MCP Gateway Registry MCP Registry MCP Servers (reference) Supergateway. Features: APIs, SDKs & MCP Extensibility Agent Identity & Interoperability MCP Tools. Related terms referenced: Agent Protocols, LLM Gateway, Tool Integration.

For this research catalog the acceptance test is boring and strict: after wiring the pack, can a second person replay the same scenario and get the same measurable outcome? If not, the page is still a brochure. Document the scenario, the expected number, and the log line that proves it. That habit is what separates a deepened taxonomy cell from a landscape screenshot.

Also record what you refused: tools not connected, corpora not ingested, metrics not collected. Refusals keep the cell honest when marketing pages claim universality. A taxonomy essay that only lists winners teaches less than one that names the skip conditions next to the install path.

Keep the essay technical enough that an engineer can argue install order — and short enough that a reader finishes it before opening the right-rail member list. Prefer primary docs and repo evidence over landscape blurbs when the right-rail packs disagree.

Operational discipline for this cell: name the install artifact, the health check, and the rollback. Prefer one golden path documented against a member pack in the right rail over five half-wired demos. When packs disagree, believe the primary repository README and a failing test you can re-run — not the landscape one-liner. Measure latency, cost, and error rate on a frozen scenario before declaring the subcategory “covered.” If you cannot point at a log line that proves the scenario, the essay is unfinished even when the word count clears the audit floor.

Cross-link greedily but honestly: every taxonomy wikilink should change a reader’s next click, and every pack slug should resolve to a real pack. Do not invent members to decorate the prose. Prefer fewer true links over many decorative ones. Keep Monday-shaped typing out of the runtime story; observation and ledger remain senior to any agent UI that retypes reality.