Skip to main content
Use this page to choose your primary integration path before you build.

​
Decide in 10 seconds

  • Choose TypeScript SDK if you want to add monetization in your own code.
  • Choose MCP Pay if you want SolvaPay to host auth, checkout, and paywall enforcement for your MCP server.

​
Quick comparison

FeatureTypeScript SDKMCP Pay
Code changes requiredYesNone
Fastest setupnpx solvapay initConsole setup
AuthenticationCustom or OAuthOAuth (Google/GitHub)
Supported platformsAny API, MCP, or web appMCP servers only
HostingYour infrastructureManaged by SolvaPay
CustomizationFull programmatic controlConfiguration-based
For SDK integration, start with one command from your project root: 
npx solvapay init
This is the fastest way to authenticate, set your secret key, and install core SDK packages. Use the SDK setup docs for full command behavior and framework-specific next steps.

​
Get started

After CLI setup, create or confirm your product and plans in the Console:

​
Path B: hosted MCP Pay (no-code)

MCP Pay is SolvaPay’s hosted MCP auth and monetization solution for MCP servers.

​
Choose this path if you:

  • You want to launch quickly without code changes
  • You are monetizing an MCP server
  • You are comfortable with OAuth sign-in for end users

​
Get started

​
Can I use both?

Yes. Some teams use MCP Pay for MCP server access while using the SDK for web apps or APIs. Both share the same plans, customers, and billing in your SolvaPay account.

​
Using an AI coding agent?

Start with one command for guided integration in any compatible AI coding tool: 
npx skills add solvapay/skills
Use platform-specific setup only if you prefer Cursor- or Claude-native flows.

​
Next steps