Skip to main content
Connect an AI agent to Relay MCP in four steps. The server uses Streamable HTTP with JSON responses only, so your client must support remote MCP servers over HTTP. Every request is stateless and must carry its own Authorization header.

​
Setup steps

1

Add the remote MCP server

Configure your client with the Relay MCP endpoint: https://mcp.relayfi.com/mcp
2

Receive 401 and discover the authorization server

Your first unauthenticated request returns HTTP 401 with a WWW-Authenticate header pointing to /.well-known/oauth-protected-resource/mcp. Read that document to find the authorization server and supported scopes.
3

Complete OAuth

Authenticate against the advertised authorization server. Request a token with the RFC 8707 resource parameter set to the MCP endpoint so the token is audience-bound. The token will carry fixed scopes and a fixed list of organizations.
4

Call initialize and list tools

Send initialize, then tools/list with a valid Authorization: Bearer <token> header. After that, call list_organizations to see which organizations the token can access, then call any tool using a valid organizationId. Every tool call must also include an intent argument describing what the user asked for and why the call serves it. See Common tool arguments.

​
Client configuration

Relay supports Claude and ChatGPT. Other MCP clients can’t connect.
Ask Claude about your Relay business banking — balances, transactions, and card spend across every account, in plain language.Add Relay as a custom connector in Claude’s connector settings, using this URL:
Claude prompts you to sign in to Relay and approve access, then handles initialize and tools/list automatically. See Get started with custom connectors using remote MCP for the current steps.

​
Rate limits and retries

Relay MCP may return HTTP 429 or 503 when rate limits or temporary issues occur. Both are retryable. Check the Retry-After header and wait that many seconds before retrying the same request with the same token.

Transport

Review the Streamable HTTP transport details and supported methods.

Authentication

Learn how to obtain audience-bound tokens and handle 401 responses.