Skip to main content

Start here

Toolhost Gateway is the Gateway product: a Go MCP gateway, an operator console, a Gateway App, and a separate Connector Runtime for local stdio servers. It is intended to sit between MCP clients and operator-configured upstream servers.

This documentation is deliberately conservative. It describes only the product boundary and interfaces that are present in the repository today; it does not claim that a public hosted gateway, signup flow, catalog, particular backend, OAuth journey, or production deployment is ready for use.

Product boundary​

  • The Gateway runtime exposes MCP at /mcp and reports process liveness and deploy readiness at /healthz/live and /healthz/ready.
  • The operator Console and Gateway App are product surfaces, but their end-to-end hosted journeys require separate verification.
  • The Connector Runtime is a separate process for local-development stdio servers. Production Gateway backends are remote Streamable HTTP or SSE services.
  • The MCP Registry and the public marketing Site are separate products; neither is part of Gateway runtime or deployment documentation.

Before you connect an agent​

Use a locally verified Gateway configuration and non-production credentials. Confirm both health endpoints locally, especially /healthz/ready; a live process is not sufficient evidence that its configured backends are usable. Connection instructions will be published only after that end-to-end path is exercised against a release artifact.

Documentation map​

The planned information architecture is intentionally small:

  • Start here
  • Connect your first agent
  • Gateway concepts
  • Operate Gateway
  • Reference

Only Start here is published in this baseline. The remaining sections will be added after their claims are tied to tested Gateway behavior and the release/deployment contract.