Connect other MCP clients to Coinrule

The Coinrule MCP is a standards-compliant remote MCP server, so any client that supports the Model Context Protocol over Streamable HTTP with OAuth 2.1 can connect — not just Claude, ChatGPT, and Grok. This page covers the technical details for other clients and developers.

Endpoints

Most clients only need the MCP server URL — they discover the OAuth endpoints automatically from the protected-resource metadata.

OAuth requirements

The authorization server supports:

• Grants: authorization_code and refresh_token.
• PKCE: required, S256 only.
• Client registration: Dynamic Client Registration (DCR) via POST /oauth/register, and Client ID Metadata Documents (CIMD) for clients that use an HTTPS URL as their client_id.
• Public clients: token_endpoint_auth_method is none.
• Scopes: coinrule:read and coinrule:write (see scopes and permissions).

Access tokens are short-lived; refresh tokens rotate. Every request to /mcp must carry the bearer token your client obtains through the OAuth flow.

Connection flow

1. Discover metadata

   Fetch the protected-resource metadata to learn the authorization server, then fetch the authorization-server metadata for the authorize, token, and registration endpoints.

2. Register (DCR or CIMD)

   Register a client via POST /oauth/register, or present an HTTPS client_id metadata document if your client uses CIMD.

3. Authorize with PKCE

   Send the user through /oauth/authorize with an S256 code challenge. They sign in with Coinrule and choose read-only or read+write.

4. Exchange the code

   Exchange the authorization code at /oauth/token for an access token and refresh token.

5. Call tools

   Open the MCP session at https://cloud.coinrule.com/mcp with Authorization: Bearer <token> and call tools.

Next steps

• Tools reference — every tool and its parameters.
• Scopes and permissions — read vs write.
• Troubleshooting.