DOCUMENTATION API v2

MCP Server

Connect an AI development assistant to Tyga Pay through the Model Context Protocol. Search the API reference, create and retrieve orders, inspect payment receipts, and manage checkout sessions from a compatible MCP client.

Match each key to its MCP URL

Each key belongs to one merchant workspace and API environment. If you use more than one, give each connection a distinct name and use the matching URL and key.

Connect your assistant

  1. Sign in to the developer portal and create an API key with the order scopes your assistant needs.
  2. Use a client that supports Streamable HTTP and custom request headers. Add one uniquely named MCP server entry for each key. The exact settings format can vary by client.
  3. Replace the placeholders in the example with the matching keys in your client’s private configuration. If you belong to multiple workspaces, repeat the entries for each workspace. Never put keys in a prompt, repository or browser code.
  4. Choose the intended named connection, then connect and list the available tools. Start with search_docs, use check_order_reference before creating an order, and look up an existing order by its ID or merchant reference.
One connection per workspace and environment
{
  "mcpServers": {
    "tyga-pay-<workspace>-sandbox": {
      "url": "https://mcpapi-kj4lhbgxiq-uc.a.run.app/mcp",
      "headers": {
        "x-api-key": "YOUR_SANDBOX_KEY_FOR_THIS_WORKSPACE"
      }
    },
    "tyga-pay-<workspace>-production": {
      "url": "https://mcpapi-rdqehkur6a-uc.a.run.app/mcp",
      "headers": {
        "x-api-key": "YOUR_PRODUCTION_KEY_FOR_THIS_WORKSPACE"
      }
    }
  }
}

The example shows the two available MCP URLs. Use each URL only with a key issued for its environment. Your MCP client selects a connection by name; individual tool calls do not switch environments.

OAuth login connections are not supported in this release. A client that only accepts an OAuth server URL cannot use this API-key connection. Browser origins are rejected.

Available tools

search_docsRead only
Search the merchant API reference and error guidance. Requires a valid key with an order scope.
check_order_referenceorders_read
Check whether a merchant reference is already used in the account tied to your key. This is a read-only preflight; the final order creation still needs idempotency.
get_orderorders_read
Retrieve an order belonging to your merchant using exactly one of orderId or merchantReference.
get_checkout_sessionorders_read
Read session status and timestamps by sessionId. Checkout URLs and bearer tokens are never returned.
get_order_payment_historyorders_read
Read payment status and canonical transaction receipt records for an order. Results are paged with nextCursor; this is on-chain transaction evidence, not an invoice or tax document.
create_orderorders_write
Create a USD order for your merchant account. Supply an order object and a stable idempotencyKey. amountMinor must be at least 100 (USD 1.00) and item totals, plus optional taxMinor and shippingMinor and minus optional discountMinor, must reconcile to it; items may be empty, and optional successUrl/cancelUrl values must be registered for the merchant.
cancel_orderorders_write
Cancel an active order that is not fully paid. This does not refund or reverse payment; any funds already received are marked for review.
create_checkout_sessionorders_write
Create a checkout link using orderId and idempotencyKey. Optional expiresAt must remain within the order expiry.
revoke_checkout_sessionorders_write
Disable a checkout link using sessionId. This does not cancel an order or refund a payment.

Keep control of changes

Require your assistant to ask before creating orders, cancelling orders, or creating and revoking checkout links. MCP tool annotations describe the action; your client controls approval prompts.

Use a dedicated, minimally scoped key. Each request uses the merchant account and permissions tied to that key. Existing IP restrictions and rate limits apply. Revoking a key blocks subsequent requests.

Before a write, confirm the assistant is using the intended named connection. Use a separate key and connection for each merchant workspace.

Reuse the same idempotency key and unchanged arguments when retrying a creation request. Checkout URLs are bearer secrets: only share them with the intended customer. Tool results may be retained by your AI client.

This release cannot execute payments or manage API keys. An open order is not proof of payment.

Authentication · Retries and idempotency