> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solvapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> SolvaPay quick facts:
> - REST API base URL: https://api.solvapay.com. All public endpoints are under /v1/sdk/ (for example GET https://api.solvapay.com/v1/sdk/products). Sandbox and production share this URL.
> - Auth: send a secret key as `Authorization: Bearer <secret key>` (the REST API also accepts `X-API-Key: <secret key>`).
> - Secret key prefixes: `sk_sandbox_` (sandbox, test payments) and `sk_live_` (production). The prefix selects the environment.
> - Get keys in SolvaPay Console (https://app.solvapay.com) > Developers > API Keys. Use a sandbox key while building.
> - Admin MCP Server: https://mcp.solvapay.com/mcp (Streamable HTTP). Connect with OAuth: add the URL and sign in with the SolvaPay account; no API key needed. OAuth sessions use the live account; for sandbox data or headless clients, send `Authorization: Bearer <secret key>` (X-API-Key is ignored).
> - Install the SolvaPay agent skills: `npx skills add https://solvapay.com` (skills CLI older than 1.5.7: `npx skills add solvapay/skills`).
> - TypeScript SDK setup: `npx solvapay@latest init`. The SDK reads SOLVAPAY_SECRET_KEY and defaults to https://api.solvapay.com.
> - Plans take an options[] array (billingCycle, charge, limit, ...). Retired plan fields price, freeUnits and billingCycle are rejected.
> - Step-by-step from zero to a first paid call: Managed MCP https://docs.solvapay.com/build/managed-mcp.md, TypeScript SDK https://docs.solvapay.com/build/typescript-sdk.md, agent skill https://docs.solvapay.com/build/agent-skill.md.
> - Details: https://docs.solvapay.com/api-reference/authentication.md. OpenAPI spec: https://docs.solvapay.com/api-reference/openapi.json.

# SolvaPay in Claude

> How SolvaPay checkout, account pages and MCP UIs work when your MCP server runs in Claude on the web and in Claude Desktop.

Claude renders MCP UIs inside the chat, so customers see SolvaPay's plan and account views without leaving the conversation. Claude does not allow the card form inside that UI, so checkout opens as a SolvaPay-hosted page in Claude's built-in browser. Account pages open there too.

## What works

* Text and links: supported.
* MCP UIs: rendered inline in the chat.
* Payment form: hosted page, in Claude's built-in browser.
* Account pages: hosted page, in Claude's built-in browser.

## Checkout

When a paid tool is blocked, the response text states the limit and links to hosted checkout. If the customer opens checkout from the MCP UI, the UI hands the link to Claude, which opens it in its built-in browser. After payment, the customer returns to the chat and the next call to the paid tool runs.

## Account pages

Plan, usage and billing history always live on SolvaPay-hosted pages. Claude opens them in its built-in browser.

## MCP UIs

Claude supports MCP Apps, so the SolvaPay `account` tool renders its plan, checkout and top-up views inline. See the [MCP App integration guide](https://docs.solvapay.com/sdks/typescript/guides/mcp-app.md) to build or customize them.

## Connect your MCP server

1. In Claude, go to **Customize** > **Connectors**.
2. Select **+**, then **Add custom connector**.
3. Enter your MCP server URL and select **Add**.
4. Select **Connect** and sign in when prompted.

Team and Enterprise owners add the connector under **Organization settings** > **Connectors** first. See Claude's [custom connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for plan-specific steps.

## Known limitations

* Claude's sandbox blocks the embedded card form, so card entry always happens on the hosted page.
* Claude's sandbox also blocks pop-ups. Links inside the MCP UI open through Claude rather than a new browser tab. The SolvaPay React components handle this for you.
* Hosted checkout links expire after 15 minutes. Ask the assistant for a new link if one has expired.

Last tested: 2026-09-30


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.