# MCP Logto OAuth Policy

:::note{title="MCP Gateway Policy"}

This policy is for use with the [MCP Gateway](/mcp-gateway/introduction). See
the MCP Gateway documentation to learn how to proxy and secure MCP servers with
Zuplo.

:::

Authenticate MCP gateway requests using a gateway-issued OAuth access token,
with browser login delegated to Logto.

This is a Logto-friendly wrapper around `McpOAuthInboundPolicy`. Provide
`logtoEndpoint` + `clientId` + `clientSecret`, and Logto's `/oidc` issuer, JWKS
URL, and browser login endpoints are derived automatically.

## Configuration

The configuration shows how to configure the policy in the 'policies.json' document.

```json title="config/policies.json"
{
  "name": "my-mcp-logto-oauth-inbound-policy",
  "policyType": "mcp-logto-oauth-inbound",
  "handler": {
    "export": "McpLogtoOAuthInboundPolicy",
    "module": "$import(@zuplo/runtime)",
    "options": {
      "browserLoginOverrides": {
        "remoteTimeoutMs": 10000,
        "sessionTtlSeconds": 28800,
        "stateTtlSeconds": 900
      },
      "clientId": "$env(LOGTO_CLIENT_ID)",
      "clientSecret": "$env(LOGTO_CLIENT_SECRET)",
      "gateway": {
        "accessTokenTtlSeconds": 900,
        "cimdEnabled": true,
        "refreshTokenTtlSeconds": 2592000
      },
      "logtoEndpoint": "https://your-tenant.logto.app",
      "scope": "openid profile email"
    }
  }
}
```

### Policy Configuration

- `name` <code className="text-green-600">&lt;string&gt;</code> - The name of your policy instance. This is used as a reference in your routes.
- `policyType` <code className="text-green-600">&lt;string&gt;</code> - The identifier of the policy. This is used by the Zuplo UI. Value should be `mcp-logto-oauth-inbound`.
- `handler.export` <code className="text-green-600">&lt;string&gt;</code> - The name of the exported type. Value should be `McpLogtoOAuthInboundPolicy`.
- `handler.module` <code className="text-green-600">&lt;string&gt;</code> - The module containing the policy. Value should be `$import(@zuplo/runtime)`.
- `handler.options` <code className="text-green-600">&lt;object&gt;</code> - The options for this policy. [See Policy Options](#policy-options) below.

### Policy Options

The options for this policy are specified below. All properties are optional unless specifically marked as required.

- `logtoEndpoint` **(required)** <code className="text-green-600">&lt;string&gt;</code> - Your Logto tenant endpoint or custom domain, without the /oidc path. The OIDC issuer, JWKS URL, authorization URL, and token URL are derived from this.
- `clientId` **(required)** <code className="text-green-600">&lt;string&gt;</code> - The Logto application client_id registered for the gateway's browser login flow.
- `clientSecret` **(required)** <code className="text-green-600">&lt;string&gt;</code> - The Logto application client_secret. Use $env(...) to source from a secret environment variable.
- `scope` <code className="text-green-600">&lt;string&gt;</code> - OIDC scopes requested during browser login. Defaults to `"openid profile email"`.
- `gateway` <code className="text-green-600">&lt;object&gt;</code> - Gateway-side OAuth token settings. The gateway issuer and advertised URLs are derived from the incoming request origin.
  - `accessTokenTtlSeconds` <code className="text-green-600">&lt;integer&gt;</code> - Lifetime of access tokens issued by /oauth/token. Defaults to `900`.
  - `refreshTokenTtlSeconds` <code className="text-green-600">&lt;integer&gt;</code> - Lifetime of refresh tokens issued by /oauth/token. Defaults to `2592000`.
  - `cimdEnabled` <code className="text-green-600">&lt;boolean&gt;</code> - Whether to advertise client_id_metadata_document_supported in AS metadata. Defaults to `true`.
- `browserLoginOverrides` <code className="text-green-600">&lt;object&gt;</code> - Optional overrides for the derived browser-login settings.
  - `remoteTimeoutMs` <code className="text-green-600">&lt;integer&gt;</code> - No description available. Defaults to `10000`.
  - `stateTtlSeconds` <code className="text-green-600">&lt;integer&gt;</code> - No description available. Defaults to `900`.
  - `sessionTtlSeconds` <code className="text-green-600">&lt;integer&gt;</code> - No description available. Defaults to `28800`.

## Using the Policy

# MCP Logto OAuth Inbound

Authenticate MCP gateway requests using a gateway-issued OAuth access token,
with browser login delegated to Logto.

This is a thin Logto-friendly wrapper around the generic
`McpOAuthInboundPolicy`. Use it when you want to configure browser login with
`logtoEndpoint` + `clientId` + `clientSecret` instead of the full set of OIDC
URLs.

## Derived configuration

Given `logtoEndpoint: "https://acme.logto.app"`, the wrapper derives:

| Generic field                                      | Derived value                       |
| -------------------------------------------------- | ----------------------------------- |
| `oidc.issuer`                                      | `https://acme.logto.app/oidc`       |
| `oidc.jwksUrl`                                     | `https://acme.logto.app/oidc/jwks`  |
| `browserLogin.url`                                 | `https://acme.logto.app/oidc/auth`  |
| `browserLogin.tokenUrl`                            | `https://acme.logto.app/oidc/token` |
| `browserLogin.clientId` / `clientSecret` / `scope` | from policy options                 |

These endpoint shapes come from Logto's OIDC provider mounted at `/oidc` and its
discovery document at
`https://<your-logto-endpoint>/oidc/.well-known/openid-configuration`.

## Configuration

```json
{
  "name": "logto-managed-oauth",
  "policyType": "mcp-logto-oauth-inbound",
  "handler": {
    "module": "$import(@zuplo/runtime)",
    "export": "McpLogtoOAuthInboundPolicy",
    "options": {
      "logtoEndpoint": "https://your-tenant.logto.app",
      "clientId": "$env(LOGTO_CLIENT_ID)",
      "clientSecret": "$env(LOGTO_CLIENT_SECRET)"
    }
  }
}
```

`logtoEndpoint` must be the HTTPS tenant base URL or custom domain. Do not
include `/oidc`, `/.well-known/openid-configuration`, or any trailing path.

## Pairing

Pair this policy with `McpTokenExchangeInboundPolicy` and `McpProxyHandler`, the
same as `McpOAuthInboundPolicy`. Only one MCP OAuth policy is allowed per
project; attach the same policy by name to every MCP route.

Read more about [how policies work](/articles/policies)