Model Context Protocol setup

Publicly available for any merchant to connect a compatible MCP client to three read-only Open Border Sandbox tools using your own Sandbox Test secret key.

Written against: Open Border MCP 0.1
Who owns what: The MCP server translates read-only tool calls; the Open Border Sandbox API remains the authority for authentication and merchant-scoped data.

Availability

Resources and readiness

Public Public MCP servicePublicly available. No approval or admission request is required. Connect your client to https://mcp-sandbox.openborderpayments.com/mcp.
Not supported Setup videoNo public setup video is published yet. Owner: Open Border integrations
Next: Use this written guide with the client-specific connection instructions.

Step 1

Before you start

Use the public MCP endpoint at https://mcp-sandbox.openborderpayments.com/mcp; no admission request is required.
Use an Open Border Sandbox Test secret key beginning sk_test_. Live and publishable keys are rejected.
Use a client that supports stateless Streamable HTTP and Bearer authentication.

Step 2

Get your test keys

Create or use a Test secret key in the Open Border dashboard. Keep it in your MCP client secret store; never paste it into a tool argument, prompt, URL, or support message.

Step 3

Install

The server is remote, so there is no Open Border package to install. Follow your compatible MCP client’s remote-server connection flow.

Step 4

Configure

Configuration fields
Field	What it does	Set it to
`Server URL`	https://mcp-sandbox.openborderpayments.com/mcp	Yes
`Authorization`	Bearer plus your Sandbox sk_test_ secret.	Yes

Step 5

Connect webhooks

No webhook setup is needed or available through this read-only MCP service. Configure commerce webhooks through the supported integration or dashboard workflow.

Step 6

Run a test payment

The MCP server cannot run a payment. Create any Sandbox payment through an existing supported checkout integration, then use openborder_get_payment_intent to read its status.

Step 7

Go live

Step 8

Troubleshooting

Reference
Symptom	Check
401 invalid_token	Confirm the credential is a current Sandbox Test secret key and is stored as a Bearer secret.
403 invalid_origin	Use a server-side or desktop MCP client without a browser Origin header. Browser origins remain blocked unless explicitly allowlisted.
404 or payment-intent error	Confirm the intent belongs to the merchant represented by the Test key.
429 rate_limited	Wait for the Retry-After interval before sending another request.

Step 9

Upgrade and remove

1 Remove the connection Delete the remote server entry from the MCP client.
2 Revoke the credential Revoke the Test key in the Open Border dashboard if it is no longer used elsewhere.
3 Review expanded access Treat any future tool or live-mode expansion as a separate security and product decision.