Getting Connected

The server speaks streamable HTTP MCP. All requests require authentication — see Authentication.

Note: MCP access must be enabled for your account (merchant or partner). If you don't see the option in your dashboard, contact your Resolve representative.

There are two ways to connect, depending on who (or what) is using the MCP:

1. Native AI assistants (Claude, ChatGPT) — connect through an interactive OAuth sign-in using your own Resolve account, the same one you use for the dashboard. See Web App Authentication.
2. Custom MCP clients and agents — authenticate with a machine-to-machine (M2M) bearer token minted from an MCP access key. No interactive login required. See Machine-to-Machine (M2M) Authentication.

1. In the Merchant Dashboard, generate a Web App MCP access key and copy its client_id and client_secret — see Get an MCP API access key.
2. In Claude, go to Settings > Connectors > Add custom connector.
3. Enter the server URL https://mcp.resolvepay.com/mcp, then add the client_id and client_secret from step 1 in the connector's OAuth settings.
4. Claude redirects you to the Resolve login. Sign in (including Google login) and approve access. Claude stays connected using rotating refresh tokens — no need to sign in on every conversation.

For the best experience, also install the Resolve MCP skill.

1. In the Merchant Dashboard, generate a Web App MCP access key and copy its client_id and client_secret — see Get an MCP API access key.
2. In ChatGPT, enable Developer Mode (Settings > Apps & Connectors), then choose Create / Add connector.
3. Enter the server URL https://mcp.resolvepay.com/mcp, choose User-Defined OAuth Client, and enter the client_id and client_secret from step 1.
4. Sign in to Resolve and approve access.

For the best experience, also install the Resolve MCP skill.

1. In the Merchant Dashboard, generate an M2M MCP access key and copy its client_id and client_secret — see Get an MCP API access key.
2. Exchange the key for a bearer token, then point your client at the server URL. Full walkthrough with example config in Authentication.

The MCP enforces one load-bearing principle: the AI sees only what the authenticated user can already see in the Resolve dashboard — nothing more.

• Every tool call runs under the identity of the authenticated user (Web App Authentication) or the account that owns the access key — merchant or partner — (M2M) — M2M calls impersonate that account owner with no further auth, so keep access keys behind your own gated access.
• Permissions mirror your dashboard roles: read-only logins get read tools only; write tools require a write-capable role. See the Tool Reference for merchants or partners.
• There is no visibility into accounts you don't already have access to, and no AI-only data path. On a partner account that scope includes your own sub-merchants, matching your partner dashboard.
• All MCP activity is audit-logged.
• You can revoke access at any time: disconnect the connector in Claude/ChatGPT, or revoke the MCP access key in Merchant Dashboard.