Claude
Connect Claude to your Solvimon account and manage billing in plain language: build pricing plans, generate checkout links, and answer revenue questions without writing an API call.
Why this matters
The Solvimon MCP (Model Context Protocol) server turns Claude into a billing copilot for your Solvimon account. This is not a read-only integration: describe a pricing model in plain language and Claude builds it in Solvimon for you. It creates flat, usage-based, tiered, and hybrid pricing plans, sets up the meters behind them, and generates hosted checkout links. It can also answer revenue questions directly from your analytics data.
The MCP server includes analytics. Ask about MRR, revenue recognition, or invoice data and Claude queries 10 analytics datasets on your behalf.
Example prompts
Once connected, you can interact with Solvimon using plain language. Here are a few examples:
Pricing and checkout
- Set up a checkout page to gather donations from my customers
- Create three flat monthly pricing plans called Starter, Pro, and Enterprise
- Create a metered plan that charges $0.002 per API request, with the first 10,000 requests free
Analytics
- How did my MRR develop over the last 6 months?
- Which 10 customers generated the most invoiced revenue this year?
- Compare recognised vs deferred revenue for last quarter
- Show me the invoice totals for customers X and Y side by side
Connect via Claude Desktop
You’ll need a test API key (Desk → Settings → API keys) and Node.js installed on your machine.
Check that Node.js is installed
If nothing is returned, download and install Node.js from nodejs.org.
Configure the MCP server
Open Claude Desktop and go to Settings → Developer → Edit Config. Add the following entry inside mcpServers, replacing replace-only-this-text-with-api-key with your test API key. If your configuration doesn’t have an mcpServers section yet, create it.
Connect via Claude Code
If you work in the terminal with Claude Code, run the following command, replacing your-api-key with your test API key:
Test environment. The test.mcp.solvimon.com endpoint connects to your test sandbox, so you can experiment freely without touching live billing data. Use your test API key; live keys will not work against this endpoint. Production access is enabled per account; see Get access.
What Claude can do
The MCP server exposes tools covering the full billing lifecycle: the product catalog, meters and usage events, pricing plans, customers, subscriptions, checkout links, invoices and payments, wallets and credits, and read-only analytics. Anything the tools don’t cover directly, Claude can reach through a raw API passthrough.
Resources Claude creates are real: pricing plans, meters, and checkout links show up in Desk immediately, ready to review, edit, or activate.
For the full tool reference, including per-tool parameters and examples, see Developing for Solvimon. That page also covers connecting the MCP server from other tools such as Cursor and VS Code, and using our docs with LLMs via llms.txt.
Get access
You can try the MCP server in your test sandbox today; connect with your test API key as described above and experiment freely. The server is already running in production for a group of Solvimon customers. Because Claude creates real plans and checkout links, production access is set up by Solvimon for each account to prevent mistakes. Contact us to get set up, or head over to solvimon.com/forai/mcp to learn more about what Solvimon is building for AI-driven billing.