AI and MCP integrations

Pontoon exposes a standard Streamable HTTP endpoint at https://pontoon.dev/mcp. The same endpoint works with ChatGPT/OpenAI API, Claude, Gemini/ADK, Cursor, and other MCP clients without a vendor-specific server.

Available tools

Tool	Authorization	Purpose
get_platform_capabilities	Public	Read products, chains, docs, and safety boundaries
get_account_balance	Bearer API key	Read merchant prepaid balance
get_checkout_intent	Bearer API key	Read hosted-checkout state by merchant order ID
create_intent	Bearer API key	Create a hosted checkout intent and return payUrl

Read tools can be listed publicly. Write tools (create_intent) require a Bearer API key on the HTTP request — never put secrets in tool arguments. Prefer REST for high-volume automation.

Generic MCP test

bash

curl https://pontoon.dev/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

OpenAI Responses API

javascript

const response = await openai.responses.create({
  model: "gpt-5",
  tools: [{
    type: "mcp",
    server_label: "pontoon",
    server_url: "https://pontoon.dev/mcp",
    authorization: process.env.PONTOON_API_KEY,
    require_approval: "always"
  }],
  input: "Check my prepaid balance"
});

Claude and other clients

Add https://pontoon.dev/mcp as a custom remote MCP server. Clients that support custom headers can initially send Authorization: Bearer <API-KEY>.

One-click OAuth

After deploying a real OAuth 2.1 authorization server, set PONTOON_OAUTH_ISSUER. Pontoon publishes RFC 9728 resource metadata at /.well-known/oauth-protected-resource/mcp. The issuer must support PKCE, RFC 8414, dynamic or pre-registered clients, and audience binding to https://pontoon.dev/mcp. Add browser-client origins to PONTOON_MCP_ALLOWED_ORIGINS.