> ## 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.

# FAQ

> Frequently asked questions about the SolvaPay MCP Server.

## General

**How many tools are available?**

27 tools across 8 domains: Customer, Product, Plan, Purchase, Payment, Revenue, Usage, and Transaction.

**What AI assistants are supported?**

Any assistant that supports the Model Context Protocol with Streamable HTTP transport. This includes Cursor, Claude Desktop, Windsurf, and others. See [Installation](./installation) for setup instructions.

**Is my data isolated?**

Yes. Every tool call is scoped to the provider account associated with your credentials. You cannot access another provider's data.

## Authentication

**What authentication methods are supported?**

The MCP server supports two authentication methods:

* **OAuth login** — For clients that support OAuth (Claude.ai, Claude Desktop). You sign in with your SolvaPay dashboard credentials (email code, Google, or GitHub) and authorize the connection. No API key needed.
* **API key** — For config-based clients (Cursor, VS Code). Pass your API key via the `X-API-Key` header or the `Authorization: Bearer` header.

**Can only existing providers connect?**

Yes. The OAuth flow only allows sign-in — it does not create new accounts. You must already have a SolvaPay provider account to connect.

**Can I use both sandbox and production keys?**

Yes. Configure separate MCP server entries in your client — one with a sandbox key for testing and another with a production key. See [Installation](./installation#using-multiple-environments) for details.

**What happens if my API key is compromised?**

Revoke the key immediately in your SolvaPay dashboard under **Settings > API Keys**, then generate a new one and update your MCP configuration.

**What happens if my OAuth session expires?**

Remove the connector from your client and re-add it. You'll be redirected to the SolvaPay login page to sign in again.

## Technical

**What transport does the MCP server use?**

Streamable HTTP. The server operates in stateless mode — every request is independently authenticated. No sessions or cookies are required.

**Is there a rate limit?**

Rate limits depend on your plan. If a customer's usage limits are exceeded, the `check_limits` tool will indicate this and can provide a checkout URL for the customer to upgrade.

**What happens if the server is down?**

Tool calls will fail with a connection error. The SolvaPay MCP Server runs on Google Cloud with multiple replicas for high availability. Check [status.solvapay.com](https://status.solvapay.com) for service status.

**Are requests encrypted?**

Yes. All communication between your MCP client and the SolvaPay server uses HTTPS (TLS 1.2+).

## Error Handling

**What does a tool error look like?**

Failed tool calls return a JSON error:

```json theme={null}
{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Customer with reference cus_INVALID not found"
  }
}
```

**What are the common error codes?**

| Code               | Description                                             |
| ------------------ | ------------------------------------------------------- |
| `NOT_FOUND`        | The requested resource does not exist                   |
| `VALIDATION_ERROR` | Invalid or missing parameters                           |
| `UNAUTHORIZED`     | Invalid or expired credentials (API key or OAuth token) |
| `INTERNAL_ERROR`   | Server-side error — retry or contact support            |