MCP Gateways

An MCP gateway makes an Application an OAuth-protected MCP Resource. It has a route key, canonical OAuth Resource URI, authorization digest, and lifecycle state.

The gateway does not itself grant upstream access. Administrators attach Connectors with capability and scope ceilings. Delegated User consent can narrow those attachments into Grants; an autonomous Application can use only eligible attachments on its own gateway.

Request path

MCP client
  -> audience-bound Axec gateway token
  -> /g/{gateway_key}/mcp
  -> live authority evaluation
  -> policy and approval when applicable
  -> selected Connector capability
  -> upstream result
  -> Data Protection when applicable

The bearer must target the gateway’s exact Resource. On each MCP operation, Axec reloads current tenant, principal, Application, credential, gateway, root or attachment, Connector, and credential-source state.

Gateway roles are explicit

In delegated authorization, the client Application requesting access can differ from the Application that owns the gateway. In an Application-principal Client Credentials flow, client and gateway must be the same Application.

Gateway configuration does not currently enforce an allowed-group list. Directory group facts do not independently grant MCP authority.

Continue with Connectors or Grants and GrantBundles.