Your agent solution, available over MCP.

Compose tools and published Workflows into an MCP endpoint. Give each audience the capabilities, authentication, and autonomy policy it needs.

One set of resources.
Access shaped for each audience.

Choose the audience to see how the endpoint, tool catalog, and policy change.

Gateway audience

Illustrative Gateways and tool catalogs.

/mcp/partner-support

Only the tools this audience needs.

Selected actions for support partners. The underlying order and return integrations remain shared resources.

Authentication
OAuth 2.1
Autonomy
Supervised
  • orders.get Connector

    Look up an order and its delivery status.

  • returns.start Workflow

    Start the published return process.

Calls that require human approval are denied; Gateways have no approval path.

/mcp/internal-operations

A different catalog. Its own policy.

An internal team can use a broader set of actions, with separate credentials and an explicit autonomy posture.

Authentication
API key
Autonomy
Full autonomy
  • orders.get Connector

    Look up an order and its delivery status.

  • refunds.issue Connector

    Issue a refund through the payment integration.

  • returns.reconcile Workflow

    Run the reconciliation process.

Full autonomy still enforces intrinsic protections and explicit deny rules.

Compose the endpoint.

Reuse what’s already connected, then decide how clients see it.

Attach capabilities and Workflows

Use platform tools, WASM plugins, external connectors, and published Workflows. Each retains its own credentials, limits, execution boundary, and version.

Set authentication and policy

Resolve the caller before exposing the tool catalog. Use a public endpoint or authenticate private access with OAuth 2.1 or API keys.

Choose the tool presentation

Expose tools directly, provide search/describe/execute through Discovery, or use a single natural-language dispatcher. Adaptive mode switches to Discovery at 30 tools.

Live access. A record of every call.

Gateway policy and bindings are evaluated for each request.

How admission works

Unbind a capability or deactivate a resource, and the next request reflects it. The journal attributes outcomes to the Gateway, caller, and capability, with latency and cost.

What happens when an action needs approval?

Gateways do not currently have a trusted human approval path. A call that would pause for approval is denied instead. Full autonomy still respects intrinsic protections and deny rules.

How are caller identity and workspaces isolated?

Credentials are scoped to the Gateway. Authenticated callers receive isolated workspaces; anonymous callers do not share a workspace. Unsupported tools are withheld from the catalog. Dynamic client registration is supported.

Does the journal replay Gateway calls?

No. The Gateway journal is an audit record, not a replay stream that reruns calls. Its catalog is live per request, while an agent thread’s tool presentation is pinned.