Before connecting
- Sign in to the intended Console account and confirm the organization that will own the credential, wallet and results.
- Confirm at least $1,000 of initial prepaid wallet funding has been credited. A checkout redirect or payment in progress is not confirmed balance.
- Read the operation’s required scopes in the live catalog. For the SEC financial research example, create a Console-issued credential with company.read, the selected API or MCP channel, and explicit per-request and daily spending limits. Keep human sign-in tokens separate from machine credentials.
- Keep credentials in your client’s secret or environment settings. Do not paste them into prompts, source control, public documentation or support feedback.
- Inspect the current tool catalog, confirm customer purchasing and organization eligibility, and obtain a quote before authorizing paid work. A catalog description or published scope description is not proof that an operation is activated for your organization.
Choose your client
- Claude Code: Connect a remote Console MCP server using a privately supplied Console key.
- Claude Desktop: Use a remote custom connector when your account and client authorization method support it.
- ChatGPT where supported: Connect a custom MCP server only where your workspace permits it and the client can satisfy Console authorization.
- Cursor: Configure Console MCP with an environment-backed Bearer header.
- Generic MCP clients: Use the actual Streamable HTTP resource and discover tools at runtime.
- Custom API agents: Read the actual REST catalog with an API-channel credential before requesting a quote.
- A2A-compatible agents: Discover the public Altss reader and preserve its public-only scope.