Claude | Solvimon | Documentation

Connect Claude to your Solvimon account to manage billing in plain language. Claude can build pricing plans and generate checkout links in your test sandbox. It can also answer revenue questions without an API call from you.

Why this matters

The Solvimon MCP (Model Context Protocol) server turns Claude into a billing copilot for your Solvimon account. On the test server (test.mcp.solvimon.com), describe a pricing model in plain language and Claude builds it in your test sandbox 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. On the live server (mcp.solvimon.com) Claude reads all your live billing data, and sales reps can draft quotes and customers, including straight from a signed order form. Sending, accepting, signing and converting a quote stay in Desk, see Test and live.

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. Prompts that read data or draft a quote work on both servers. Prompts that build pricing, checkout links or other setup only work on the test server, see Test and live. Here are a few examples:

Billing overview

These only read data, so they work on both the test and the live server.

Give me an overview of all my products and how they are being charged.
What is my MRR over the past 6 months, and which portion is recurring, one-off and usage-based?
How many invoices are overdue, and how long are they overdue for?
Which customers still live on deprecated plans, and who is close to a renewal?

Quotes

These draft a quote, so they work on the test server and, for signed-in users, on the live server.

Create a quote for Acme Corp on the Growth plan: 12 months, billed monthly, platform fee at €2,500 instead of €3,000
Preview the first invoice for the Acme quote
Give me a PDF of the Acme quote
Here is the signed order form. Turn it into a draft quote and show me where it differs from our pricing
Does this quote need approval before I can finalize it?
Which quotes are waiting for my approval?

Billing run

Get a view of your monthly billing run: what has been invoiced, what is still outstanding, and what needs your attention before the run closes.

How is this month’s billing run looking? Anything blocking it?
Is it safe to bulk-finalize this month’s run?
List invoices that are stuck in draft or on hold from this month’s run
Which customers’ invoices changed most compared to last month, and why?

Look up a record

Ask for a single customer, invoice, quote or subscription and Claude shows it as a card, with a link to Desk.

Show me the latest invoice for Globex
What’s the status of Initech’s subscription and when is the next invoice?
Pull up customer Umbrella Ltd and their unpaid invoices

Pricing and checkout

These only work on the test server.

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

Catalog guidance

Draft agent guidance for each of our active pricing plans and show it to me before saving
Which plan should a 200-seat company that needs SSO be on, according to our guidance?

Analytics

Ask for revenue, usage and billing insights without building a report first.

What was our recurring revenue last month?
Which 10 customers generated the most usage this month?
Show me revenue by pricing plan this quarter
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

The MCP server uses OAuth. You add the server URL to Claude, sign in with your Solvimon Desk account in the browser, and approve access. There is no API key to create, copy, or rotate.

Claude then acts as you: the permissions you have in Desk are the permissions Claude gets, and nothing more. If your role cannot edit pricing plans in Desk, Claude cannot either.

Endpoint	Connects to
`https://test.mcp.solvimon.com`	Your test sandbox, read and write
`https://mcp.solvimon.com`	Live billing data: read everything, draft quotes and customers. Live access is enabled per account, see Get access

If you approve access to more than one platform (for example a test and a live platform), the server won’t pick one for you. In Claude Desktop and on claude.ai, connectors can’t send custom headers, so approve a single platform per connector. In Claude Code you can instead name the platform with the X-PLATFORM-ID header, see Connect via Claude Code.

Connect via Claude Desktop or claude.ai

Connectors belong to your Claude account, so a connector you add in Claude Desktop is also available on claude.ai in the browser, and the other way around. The steps are the same in both.

Add a custom connector

Open Customize, go to Connectors, click Add, and select Add custom connector. Name it Solvimon (test) and enter the URL https://test.mcp.solvimon.com.

The URL decides which environment the connector reaches. To connect live billing data, add a second connector named Solvimon (live) with https://mcp.solvimon.com once live is enabled for your account.

On Team and Enterprise plans, an owner may need to add the connector for your organization first. The Free plan allows one custom connector, so you can connect either test or live, not both.

Start a conversation

The Solvimon tools are available in your next conversation. Start by asking Claude to verify the connection, for example “Which Solvimon billing entities can you see?”.

Let Claude guide you through the setup

Claude can walk you through these steps itself. Open a new chat with the setup prompt, or paste the prompt below into Claude Desktop or claude.ai. Claude reads this page, takes you through adding the connector and signing in, checks which billing entities it can see, and then suggests a few prompts to start with.

Setup prompt for Claude

Help me connect the Solvimon MCP server to you, step by step. Solvimon (solvimon.com) is billing and monetization infrastructure, and its MCP server lets you read and change my billing data: customers, pricing plans, subscriptions, quotes, invoices, credits and revenue analytics. There are two server URLs: https://test.mcp.solvimon.com for my test sandbox and https://mcp.solvimon.com for live billing data (enabled per account). The setup docs are at https://docs.solvimon.com/integrations/ai-assistants/claude, read those first for the exact steps. Then walk me through adding the server URL as a custom connector in this app, signing in with my Solvimon Desk account and approving access to a single platform. Once it's connected, confirm which Solvimon billing entities you can see, then offer me these starter prompts to try:
- Give me an overview of all my products and how they are being charged.
- What is my MRR over the past 6 months, and which portion is recurring, one-off and usage-based?
- How many invoices are overdue, and how long are they overdue for?
- Which customers still live on deprecated plans, and who is close to a renewal?

Connect Claude Desktop with an API key instead

Use an API key when you cannot add a custom connector, for example because your organization does not allow them. This only works in Claude Desktop, not on claude.ai. You need an API key (Desk → Developers → API keys) and Node.js. Open Settings → Developer → Edit Config and add the following inside mcpServers:

claude_desktop_config.json

{
  "mcpServers": {
    "solvimon-test": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://test.mcp.solvimon.com",
        "--header",
        "X-API-KEY:${SOLVIMON_API_KEY}"
      ],
      "env": {
        "SOLVIMON_API_KEY": "<apiKey>"
      }
    },
    "solvimon-live": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.solvimon.com",
        "--header",
        "X-API-KEY:${SOLVIMON_API_KEY}"
      ],
      "env": {
        "SOLVIMON_API_KEY": "<apiKey>"
      }
    }
  }
}

Use a test API key in the solvimon-test entry and a live API key in the solvimon-live entry. The key goes in the env block because Claude Desktop doesn’t pass your shell’s environment variables to the server, and mcp-remote fills in ${SOLVIMON_API_KEY} from that block. On macOS the file is often at ~/Library/Application Support/Claude/claude_desktop_config.json. Restart Claude Desktop after saving.

Connect via Claude Code

If you work in the terminal with Claude Code, add the server by URL:

claude mcp add --transport http solvimon-test https://test.mcp.solvimon.com

Then run /mcp inside Claude Code, select the Solvimon server, and choose Authenticate. Your browser opens the Solvimon login page. Sign in and approve access. Claude Code then keeps the token.

If you approved more than one platform, name the one to use with the X-PLATFORM-ID header. The platform ID is in the Desk address bar. It is the part of the path that starts with plat_, for example https://test.desk.solvimon.com/plat_.../overview. Remove the server first if you already added it:

Pin Claude Code to one platform

claude mcp remove solvimon-test
claude mcp add --transport http solvimon-test https://test.mcp.solvimon.com --header "X-PLATFORM-ID: <platformId>"

Connect with an API key instead

For non-interactive use, such as CI, pass an API key in the X-API-KEY header instead of signing in:

Add Solvimon's test MCP with an API key

claude mcp add --transport http solvimon-test https://test.mcp.solvimon.com --header "X-API-KEY: <apiKey>"

Test vs. live. The test.mcp.solvimon.com endpoint connects to your test sandbox, so you can experiment freely without touching live billing data. The mcp.solvimon.com endpoint connects to live billing data: Claude can read everything and draft quotes and customers, but not send, accept, convert or bill anything, see Test and live. If you use API keys, a test key only works against the test endpoint and a live key only against the live endpoint. A live API key only reads; drafting needs the sign-in.

What Claude can do

The MCP server has tools for the full billing lifecycle:

The product catalog, coupons, meters, usage events and usage limits
Pricing plans, customers and subscriptions
Quotes, approvals, signing, order-form import and checkout links
Invoices, payments, wallets and credits
The health of your monthly billing run
Workflows, webhooks, integrations, users, audit records, reports and analytics

Read tools and write tools are separate. Claude can thus read data without restrictions while you approve every change. In Claude, an invoice, customer, quote, subscription, product or pricing plan is shown as a card, and every record comes with a link to its page in Desk.

Test and live

	Test (`test.mcp.solvimon.com`)	Live (`mcp.solvimon.com`)
Read your billing data, analytics, billing run, audit records and reports	Yes	Yes
Draft customers and quotes, including from a signed order form	Yes	Yes, signed-in users
Finalize a DRAFT quote, after you confirm	Yes	Yes, signed-in users
Accept, sign, send or convert a quote	Yes	In Desk
Build pricing, meters, catalog, checkout links, subscriptions and invoices	Yes	In Desk

On live, everything Claude drafts stays DRAFT, and your own Desk role still applies. When something has to be done in Desk, Claude says so and gives you the link. If you connected the live server before drafting was available, disconnect and reconnect it to get the drafting tools. Write access on live beyond drafting is enabled per customer, on request. The tool reference lists which tools each server has.

On the test server, the resources that Claude creates are real. Pricing plans, meters and checkout links appear immediately in your test sandbox in Desk. You can then review, edit or activate them.

Teach Claude your catalog

Claude sees the name and price of your plans, products and quote templates. It cannot see why each one exists. To give Claude this data, fill in the Guidance field on those resources in Desk (agent_context in the API). Claude reads the guidance before it selects a plan or template. Examples of guidance are “pick this over Starter once they ask for SSO”, “annual enterprise deals only” and “never combine with the legacy plan”. A request such as “quote Acme on our most extensive plan” then selects the correct plan. Guidance is advisory. It never overrides you, your Desk permissions, or an approval. See Agent context.

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; sign in with your Desk account as described above and experiment freely. The server is already running in production for a group of Solvimon customers. In production Claude reads your live billing data and drafts quotes and customers, but can’t create plans, checkout links or anything else. Production access is set up by Solvimon for each account, and further write access on live is enabled on a customer-by-customer basis, on request. Contact us to get set up or to request write access, or head over to solvimon.com/forai/mcp to learn more about what Solvimon is building for AI-driven billing.