Skip to main content
Console’s authorization-code method requires a compatible public Client ID Metadata Document, S256 PKCE and exact MCP resource binding. It provides MCP-only tokens lasting at most one hour and no refresh token. A client’s support for remote MCP alone does not establish end-to-end compatibility; if its authorization flow cannot meet the contract, use a supported key-capable client. Never downgrade to anonymous paid access.

Prerequisites

  • Permission to add a custom remote connector in your Claude account or workspace.
  • A funded Console organization and a client authorization flow compatible with the Console guide.
Complete Console onboarding before protected paid use.

Connection steps

  1. Open the client’s Connectors settings and add a custom remote connector with the URL below.
  2. Use the client’s supported authorization flow. Review the exact Console organization, MCP access and spending limits before human approval.
  3. Inspect the connected tool inventory. If authentication is unsupported, stop and use Claude Code or another documented key-capable client.
  4. Reauthorize when the MCP-only token expires; do not expect a refresh token.

Copy configuration

Agent instructions

Verify the connection

Inspect the live tool inventory and schema before quoting work. Keep the organization, permitted inputs, maximum charge and actual run/settlement separate. A successful connection is not a payment or an accepted execution.

References

Protocol guide · Specialized prompts