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

# Admin MCP Server getting started

> Connect the SolvaPay admin MCP Server to your AI assistant to manage your provider account and generate checkout sessions.

The SolvaPay admin MCP Server lets providers manage a SolvaPay account directly from any AI assistant that supports MCP.

Instead of switching between your IDE and the SolvaPay Console, you can ask your assistant to create customers, check revenue, process refunds, manage purchases, and generate checkout sessions.

## What is MCP?

The Model Context Protocol is an open standard that allows AI assistants (like Cursor, Claude, and others) to connect to external tools and data sources. When you connect SolvaPay as an MCP server, your AI assistant gains access to tools that cover the full SolvaPay API.

## Prerequisites

* A SolvaPay account — [sign up here](/get-started/create-account) if you don't have one
* An AI assistant that supports MCP (Claude.ai, Cursor, Claude Desktop, Windsurf, etc.)

## Authentication

How you authenticate depends on your MCP client:

* **OAuth-capable clients** (Claude.ai, Claude Desktop) — You log in with your SolvaPay Console credentials directly. No API key required. The MCP server redirects you to the SolvaPay login page, and after you sign in and authorize, the client receives a token automatically.

* **Config-based clients** (Cursor, VS Code, other editors) — These clients don't support OAuth for MCP. You'll need an API key from **Settings > API Keys** in [SolvaPay Console](https://app.solvapay.com) and add it to your client configuration.

API keys are prefixed with `sk_sandbox_` (sandbox / test data) or `sk_live_` (production). Use sandbox keys during development and testing.

## What can you do?

Once connected, you can manage your entire SolvaPay account through natural conversation:

* **"Create a customer for [jane@acme.com](mailto:jane@acme.com)"** — creates a customer record
* **"How much revenue has support-bot generated?"** — checks product revenue
* **"Refund \$25 from transaction txn\_D7E8F9G0"** — processes a partial refund
* **"Check if customer cus\_A1B2C3D4 has hit their usage limits"** — checks billing limits

See the full list of [available tools](/mcp-server/tools) and [detailed examples](/mcp-server/examples).

## Claude.ai connector

SolvaPay works as a native Claude.ai connector. Add it in **Settings > Connectors** — no local setup, config files, or API keys required. Claude handles the OAuth flow automatically and redirects you to the SolvaPay login page to sign in. See the [installation guide](/mcp-server/installation#claudeai-web--mobile) for details.

## Admin MCP Server vs the no-code MCP integration

The **SolvaPay admin MCP Server** is for provider account operations. Think of it as a conversational admin layer for your SolvaPay account.

The [no-code MCP integration](/no-code-mcp/overview) is a separate path for hosted auth and monetization of your own MCP servers.

## Next steps

1. [Install and configure](/mcp-server/installation) the MCP server in your AI assistant
2. Browse the [available tools](/mcp-server/tools)
3. Try the [usage examples](/mcp-server/examples)