> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.solvimon.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.solvimon.com/_mcp/server. # Claude 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. The live server (`mcp.solvimon.com`) is read-only by default: Claude can read your live billing and analytics data, but it can't create or change anything. Solvimon enables write access on live per customer, on request, see [Get access](#get-access). > **Launch** > > 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 create or save something, such as the pricing and checkout examples, only work on the test server unless Solvimon has enabled write access on live for your account, because the live server is read-only by default. 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? **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 **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** * 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 --- ## How sign-in works 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-only by default. Live access, and write access on live, are enabled per customer on request, see [Get access](#get-access) | > **Note** > > 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-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](https://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. > **Tip** > > 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. #### Sign in with Solvimon Click **Connect**. A browser window opens on the Solvimon login page. Sign in with your Desk account, choose a single platform, and approve access. A connector that has access to more than one platform can't tell which one you mean, see [How sign-in works](#how-sign-in-works). #### 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](https://claude.ai/new?q=Help%20me%20connect%20the%20Solvimon%20MCP%20server%20to%20you%2C%20step%20by%20step.%20Solvimon%20%28solvimon.com%29%20is%20billing%20and%20monetization%20infrastructure%2C%20and%20its%20MCP%20server%20lets%20you%20read%20and%20change%20my%20billing%20data%3A%20customers%2C%20pricing%20plans%2C%20subscriptions%2C%20quotes%2C%20invoices%2C%20credits%20and%20revenue%20analytics.%20There%20are%20two%20server%20URLs%3A%20https%3A%2F%2Ftest.mcp.solvimon.com%20for%20my%20test%20sandbox%20and%20https%3A%2F%2Fmcp.solvimon.com%20for%20live%20billing%20data%20%28enabled%20per%20account%29.%20The%20setup%20docs%20are%20at%20https%3A%2F%2Fdocs.solvimon.com%2Fintegrations%2Fai-assistants%2Fclaude%2C%20read%20those%20first%20for%20the%20exact%20steps.%20Then%20walk%20me%20through%20adding%20the%20server%20URL%20as%20a%20custom%20connector%20in%20this%20app%2C%20signing%20in%20with%20my%20Solvimon%20Desk%20account%20and%20approving%20access%20to%20a%20single%20platform.%20Once%20it%27s%20connected%2C%20confirm%20which%20Solvimon%20billing%20entities%20you%20can%20see%2C%20then%20offer%20me%20these%20starter%20prompts%20to%20try%3A%0A-%20Give%20me%20an%20overview%20of%20all%20my%20products%20and%20how%20they%20are%20being%20charged.%0A-%20What%20is%20my%20MRR%20over%20the%20past%206%20months%2C%20and%20which%20portion%20is%20recurring%2C%20one-off%20and%20usage-based%3F%0A-%20How%20many%20invoices%20are%20overdue%2C%20and%20how%20long%20are%20they%20overdue%20for%3F%0A-%20Which%20customers%20still%20live%20on%20deprecated%20plans%2C%20and%20who%20is%20close%20to%20a%20renewal%3F), 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`** ```text title="Setup prompt for Claude" wordWrap 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`** ```json title="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": "" } }, "solvimon-live": { "command": "npx", "args": [ "mcp-remote", "https://mcp.solvimon.com", "--header", "X-API-KEY:${SOLVIMON_API_KEY}" ], "env": { "SOLVIMON_API_KEY": "" } } } } ``` 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](https://claude.ai/code), add the server by URL: **`Add Solvimon's test MCP to Claude Code`** ```bash title="Add Solvimon's test MCP to Claude Code" claude mcp add --transport http solvimon-test https://test.mcp.solvimon.com ``` **`Add Solvimon's live MCP to Claude Code`** ```bash title="Add Solvimon's live MCP to Claude Code" claude mcp add --transport http solvimon-live https://mcp.solvimon.com ``` **`Remove Solvimon's MCP from Claude Code`** ```bash title="Remove Solvimon's MCP from Claude Code" claude mcp remove solvimon-test claude mcp remove solvimon-live ``` 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`** ```bash title="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: " ``` #### 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`** ```bash title="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: " ``` > **Warning** > > **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 and is read-only by default, so Claude can't create or change anything there. Production access is enabled per account, and write access on live is enabled per customer on request, see [Get access](#get-access). If you use API keys, a test key only works against the test endpoint and a live key only against the live endpoint. --- ## What Claude can do The MCP server has tools for the full billing lifecycle: * The product catalog, meters and usage events * Pricing plans, customers and subscriptions * Quotes, approvals and checkout links * Invoices, payments, wallets and credits * Workflows and read-only analytics Read tools and write tools are separate. Claude can thus read data without restrictions while you approve every change. On the test server, Claude can use a read-only raw API passthrough to read data that the tools do not include. The test server (`test.mcp.solvimon.com`) has all 29 tools, read and write. The live server (`mcp.solvimon.com`) is read-only by default: it has 13 read tools covering your account and billing entities, product catalog, pricing plans, agent guidance, meters and usage events, customers, subscriptions, quotes and approvals, invoices and payments, wallets and credits, workflows, and analytics. It has no write tools, no user lookup and no raw API passthrough, so Claude can't create or change anything on live unless Solvimon has enabled write access for your account. The [tool reference](/platform-guides/for-developers/developing-for-solvimon#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](/mcp-server/agent-context). For the full tool reference, including per-tool parameters and examples, see [Developing for Solvimon](/platform-guides/for-developers/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 the server is read-only by default: Claude can read your live billing data but can't create plans, checkout links or anything else. Production access is set up by Solvimon for each account, and write access on live is enabled on a customer-by-customer basis, on request. [Contact us](https://www.solvimon.com/contact) to get set up or to request write access, or head over to [solvimon.com/forai/mcp](https://www.solvimon.com/forai/mcp) to learn more about what Solvimon is building for AI-driven billing.