Skip to main content
The no-code MCP integration is SolvaPay’s hosted 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 no-code path when you want SolvaPay to run auth, billing, checkout, and paywall enforcement for your MCP server.

​
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 the no-code MCP integration when you want SolvaPay to run managed auth, identity, billing, and payment for your MCP server.

​
When to use the no-code path

​
No-code 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 the no-code MCP integration 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

​
Tool-to-plan mapping semantics

No-code 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 (PAYG) — topup-first. A customer with enough credits for at least one unit is activated; a zero-balance customer receives topup_required and is routed into the top-up step via topup / createTopupPaymentIntent. The plan purchase is created as part of a successful top-up.
  • Recurring / hybrid — returns payment_required when the customer has no credit balance and no card on file. Route them to checkout before granting access.
The MCP App surface exposes this policy directly: when activate_plan returns topup_required, the agent surfaces the topup intent, and the paywall clears once the top-up succeeds. 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 no-code MCP product for request modes and examples.

​
Next steps