Skip to main content
This reference gives the facts of the MCP server. To connect a client, see Connect an MCP client.

Check what an MCP client can do.

Endpoint

Other clients

A client must support:
  • Remote MCP over Streamable HTTP.
  • OAuth 2.1 with the authorization code grant and PKCE (S256).
  • A Client ID Metadata Document (CIMD): an HTTPS URL as its client_id. Dynamic client registration is off.
An access token works for 15 minutes. With the offline_access scope, the client gets a refresh token. An agent can also get a token without a browser sign-in, with agent registration. Its tokens work with the same tools and limits.

Access

The client acts as you. Two things limit it:
  • The scopes that you allow on the consent screen.
  • Your role in each workspace. See roles.

Tools

Each tool that works on one workspace takes an organization argument: the URL slug of the workspace, from list_organizations.

Errors