Getting Connected

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

Note: MCP access must be enabled for your merchant account. 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.

Claude Code (recommended: plugin). The Resolve plugin bundles the MCP connector and the skill in one install — add the resolvepay/resolve-mcp-plugin marketplace and install resolve-mcp (see the Claude Code plugins documentation). On first use, Claude Code opens the Resolve sign-in. See Skills & Plugins for the optional domain plugins.

Claude (web / desktop), or manual setup:

1. In Claude, go to Settings > Connectors > Add custom connector.
2. Enter the server URL: https://mcp.resolvepay.com/mcp.
3. Claude redirects you to the Resolve login. Sign in with your Resolve account credentials (including Google login).
4. Approve the requested 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 ChatGPT, enable Developer Mode (Settings > Apps & Connectors), then choose Create / Add connector.
2. Enter the server URL: https://mcp.resolvepay.com/mcp.
3. ChatGPT redirects you to the Resolve login. Sign in and approve access.

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

The Resolve plugin marketplace works in Codex too — add the resolvepay/resolve-mcp-plugin repo as a plugin marketplace and install resolve-mcp (see the Codex plugins documentation). The plugin includes the MCP connector and the Codex-variant skill.

Codex prompts you to authenticate when the plugin installs. For headless or CI use, authenticate with an M2M token instead.

Generate an MCP access key in the Merchant Dashboard, exchange it for a bearer token, and 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 merchant user (Web App Authentication) or the merchant that owns the access key (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 Tool Reference.
• There is no cross-merchant visibility and no AI-only data path.
• 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.