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

# Managed MCP overview

> Managed MCP is SolvaPay's managed auth and monetization path for MCP servers.

Managed MCP is SolvaPay's managed auth and monetization path.

You keep ownership and hosting of your MCP server; SolvaPay sits in front of it as a reverse proxy
and handles OAuth, paywall enforcement, and billing.

Use the managed path when you want SolvaPay to run auth, billing, checkout, and paywall enforcement
for your MCP server. No code required.

## Product-first model

Every monetized offering starts as a **Product**. By default, new products are immediately:

* Available for **SDK integration**
* Active in **SolvaPay MCP Distribution**

You can optionally enable **Managed MCP** when you want SolvaPay to run managed auth,
identity, billing, and payment for your MCP server.

## When to use the managed path

### Managed MCP product

Use this when you want to connect an origin MCP server URL and let SolvaPay host authentication,
authorization, billing pages, and paywall enforcement via a managed proxy endpoint.

## How it works

When Managed MCP is enabled, SolvaPay acts as a reverse proxy between MCP clients
and your origin MCP server.

* **Authentication** - OAuth 2.0 with Google and GitHub sign-in
* **Authorization** - Purchase-plan checks per tool
* **Usage tracking** - Every tool call is automatically recorded as a [usage event](/plans/glossary) against a `tool:{toolName}` meter. Included-usage enforcement uses real-time meter aggregation.
* **Billing** - Hosted checkout and billing flows with support for recurring, usage-based, hybrid, and one-time [plans](/plans/overview)
* **Dynamic Client Registration** - MCP clients can auto-register OAuth clients

```mermaid theme={null}
flowchart LR
  A[MCP client (AI agent)]
  B[SolvaPay proxy]
  C[Origin MCP server]
  D[Auth]
  E[Plan check]
  F[Included]
  G[Tracking]

  A --> B --> C
  B --> D
  B --> E
  B --> F
  B --> G
```

## Terminology

| Term                      | Meaning                                                                                                                             |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Product**               | The core entity in SolvaPay used for monetization and plan assignment                                                               |
| **Origin MCP server URL** | Your actual MCP endpoint that SolvaPay proxies to                                                                                   |
| **Signup default plan**   | The plan automatically assigned to new users                                                                                        |
| **Server default plan**   | The default plan used for tool access in Managed MCP unless overridden                                                              |
| **Managed MCP**           | Optional managed mode for auth, identity, billing, and payment                                                                      |
| **Meter**                 | A [metric definition](/plans/glossary) that tracks usage (e.g. `tool:search_documents`). Auto-created for each discovered MCP tool. |
| **Usage event**           | A [timestamped data point](/plans/glossary) recorded each time a tool is called. Powers included-usage enforcement and billing.     |

## Tool-to-plan mapping semantics

Managed MCP access uses a clear precedence model:

* `noPlan: true` on a tool means the tool is public
* otherwise, access is allowed when the customer's purchase plan matches:
  * the tool's `planIds`, or
  * the MCP server `defaultPlanRef`

This means `defaultPlanRef` is always an additional fallback allowlist for protected tools.

## Plan activation policy

When a customer calls `activate_plan` / `POST /v1/sdk/activate`, the response depends on the plan type:

* **Free** — `activated` immediately.
* **Usage-based (metered, no billing cycle)** — `activated` immediately. A zero balance is not an activation gate. Empty-wallet access is enforced later as `topup_required` at usage time.
* **Paid recurring, hybrid, or one-time** — `payment_required`. Complete checkout before the plan activates.

The MCP App surface routes customers to add credits via the `account` viewer with `view: "topup"` when a usage-time paywall returns `topup_required`.

For API-first setup, the `POST /v1/sdk/products/mcp/bootstrap` endpoint lets you define:

* product
* plans (free and paid in one array)
* origin URL
* tool mapping in one request

After bootstrap, use `PUT /v1/sdk/products/:productRef/mcp/plans` to replace plans and remap tool
access without recreating the product.
See [Create a Managed MCP product](/no-code-mcp/create-no-code-mcp-product) for request modes
and examples.

## Next steps

* [Quick start](/no-code-mcp/quick-start) - Set up Managed MCP monetization
* [Create a Managed MCP product](/no-code-mcp/create-no-code-mcp-product) - Product flow for
  the managed path
* [Authentication](/no-code-mcp/authentication) - OAuth and client connection details