List MCP Connections
Who has connected their own upstream account to a delegated-OAuth MCP server.
auth.mode: "delegated"). KnoxCall holds their refresh token
envelope-encrypted under your tenant key and mints a short-lived access token per
call.
No response here carries a token — not redacted, not truncated, absent.
has_refresh_token is the only thing said about them; false means the
connection cannot outlive its current access token and the person should
reconnect.
Creating a connection is not an API operation. Consent has to be given by the
person whose credential it is, so the flow starts from a signed-in KnoxCall
session on the MCP server’s page in the console. An API key is not a person: an
endpoint that started a flow “for alice@acme” would let whoever holds the key
finish it with their own upstream account, and the connection would hold the
key holder’s credential under Alice’s name.
Requires the read capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.Authorizations
OAuth 2.1 authentication — recommended for new integrations. Access tokens
(kc_ prefix) are minted at the root-host token endpoint
https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>.
Public clients must use PKCE with the authorization_code grant; confidential
clients may use client_credentials. The first-party SDKs and the
knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.
Path Parameters
The MCP server UUID.
Query Parameters
Page number for pagination. Clamped server-side so the derived offset never exceeds 100,000 rows -- the effective maximum is floor(100000 / per_page) + 1, i.e. 1,001 at per_page=100. A larger value returns that last page, and meta.page reports it.
x >= 1Number of items per page (max 100).
1 <= x <= 100