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 the no-code MCP integration if you want SolvaPay to host auth, checkout, and paywall enforcement for your MCP server.

​
Quick comparison

For SDK integration, start with one command from your project root:
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: no-code MCP integration

The no-code MCP integration is SolvaPay’s hosted auth and monetization path for MCP servers. 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.

​
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 the no-code MCP integration 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:
Use platform-specific setup only if you prefer Cursor- or Claude-native flows.

​
Next steps