Skip to main content
The currently usable release is local stdio MCP. There is no enabled remote connection URL in this release.
The prepared remote implementation uses Streamable HTTP and OAuth authorization code with S256 PKCE. The intended flow is to link an account in the browser, select workspaces and scopes, use the catalog enabled by the remote deployment, and disconnect the grant from account settings.

​
Availability

Remote account linking is not enabled in the current beta. The planned connection will let you choose workspaces and permissions in the browser, then revoke access from your account settings. The changelog will announce availability and supported setup instructions when the connection is ready. Until then, use local MCP with your own scoped API key. There is no remote URL to configure yet.

​
Continue today

Use local MCP in a stdio-capable host, or use the CLI in a terminal. Both accept existing scoped keys and preserve customer/agency boundaries.