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
When to Use MCP Pay
Hosted MCP Pay Product (No-Code Managed MCP)
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 MCP Pay Works
When Hosted MCP Pay 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 meter event against a
tool:{toolName}meter. Quota enforcement uses real-time meter aggregation. - Billing - Hosted checkout and billing flows with support for recurring, usage-based, hybrid, and one-time plans
- Dynamic Client Registration - MCP clients can auto-register OAuth clients
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 Hosted MCP Pay unless overridden |
| Hosted MCP Pay | Optional managed mode for auth, identity, billing, and payment |
| Meter | A metric definition that tracks usage (e.g. tool:search_documents). Auto-created for each discovered MCP tool. |
| Meter event | A timestamped data point recorded each time a tool is called. Powers quota enforcement and billing. |
Tool-to-plan mapping semantics
Hosted MCP access uses a clear precedence model:noPlan: trueon 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
defaultPlanId
- the tool’s
defaultPlanId is always an additional fallback allowlist for protected tools.
For API-first setup, the POST /v1/sdk/products/mcp/bootstrap endpoint lets you define:
- product
- free-plan settings (
freePlan) - paid plans (
paidPlans) - origin URL
- tool mapping in one request
Next Steps
- Quick Start - Set up hosted MCP monetization
- Create a Hosted MCP Pay Product - Product flow for no-code managed MCP
- Authentication - OAuth and client connection details