OurPay provides a hosted Model Context Protocol server at:
The server uses OAuth 2.1 to connect to your OurPay account. It exposes merchant read tools and tools for creating an unpaid checkout and preparing buyer-supplied billing details. It cannot debit a wallet, issue a refund, or change a subscription. Checkout creation requires checkouts:write; existing read-only authorizations must be renewed to grant this permission. For isolated test data, first switch your dashboard to Sandbox, then connect to:
Sandbox authorization and API calls stay in sandbox. Live tokens are not accepted there.

​
Connect with a remote MCP URL

Clients that accept a remote MCP server URL need only the endpoint above. Name the connection OurPay, complete the browser authorization flow, and choose the OurPay account you want to use. If a client requires a local command instead of a URL, bridge to the remote endpoint:

​
Cursor

Add the server to .cursor/mcp.json:

​
Codex

Add the server to ~/.codex/config.toml:
Then authorize it:

​
Claude Code

​
OpenCode

Add the server to opencode.jsonc:

​
Other clients

For clients with a custom-connector screen, enter https://mcp.ourpay.dev/mcp as the remote MCP URL and complete OAuth when prompted. Your client must support remote HTTP MCP servers and OAuth.

​
Prepare an agent purchase

  1. Use ourpay_create_checkout with an authorized product ID and a payment processor. Save the returned ID and reuse it on retries; this creates an unpaid checkout.
  2. For USDC, use ourpay_prepare_usdc_checkout with the checkout client secret and billing details supplied by the buyer.
  3. Read the exact amount, network and recipient with ourpay_get_payment_collection.
  4. The buyer approves that exact collection and spending limit in the separate OurPay agent gateway. The agent receives a scoped grant token, not a wallet key.
  5. The gateway returns an order receipt only after finalized USDC settlement and OurPay fulfillment.
The hosted merchant connection and the buyer’s local signing gateway have separate credentials and responsibilities. PayPal and domestic payment tools prepare checkout for human completion; they do not grant an agent authority to charge those methods.

​
Troubleshooting

  • Open https://mcp.ourpay.dev/healthz to confirm that the service is reachable.
  • Re-run your client’s OAuth login if it reports an expired or invalid bearer token.
  • Make sure the configured path is exactly /mcp; the root URL is a status endpoint, not the MCP transport.
  • If checkout creation returns 403, renew OAuth with checkouts:write and select an organization you can access.