MCP Server | Solvimon | Documentation

The Solvimon MCP (Model Context Protocol) server lets AI assistants — such as Claude — interact directly with your Solvimon account using natural language. You can create pricing plans, set up meters, and generate checkout links without writing any API calls manually.

Connect via Claude Code (terminal)

If you are using Claude Code, run the following command to register the Solvimon MCP server:

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

Replace <your-api-key> with your test API key from Settings → API keys.

Connect via Claude Desktop

Claude Desktop requires Node.js to be installed on your machine.

Check if Node.js is installed:

$ node --version

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:

1 {
2   "mcpServers": {
3     "solvimon-test": {
4       "command": "npx",
5       "args": [
6         "mcp-remote",
7         "https://test.mcp.solvimon.com",
8         "--header",
9         "X-API-KEY:replace-only-this-text-with-api-key"
10       ]
11     }
12   }
13 }

Save the file and restart Claude Desktop. The Solvimon tools will be available in your next conversation.

Test environment only. The MCP server currently connects to test.mcp.solvimon.com. Use your test API key — live keys will not work against this endpoint.

Available tools

`get_solvimon_account`

Verifies that your credentials are valid and lists the billing entities available to the current API key. This is a good first call to confirm the server is correctly configured.

`create_flat_plan`

Creates a flat recurring pricing plan with a single fixed charge — useful for simple monthly or annual subscriptions and platform fees.

Parameter	Required	Description
`name`	Yes	Display name for the plan (e.g. `"Pro plan"`)
`amount.quantity`	Yes	Price as a decimal string (e.g. `"79.00"`)
`amount.currency`	Yes	ISO 4217 currency code (e.g. `"EUR"`)
`reference`	No	Unique reference slug. Auto-generated if omitted.
`billing_in_advance`	No	Whether to bill in advance. Default `true`.
`billing_entity_id`	No	`bile_...` id. Uses your default billing entity if omitted.

`create_usage_plan`

Creates a pay-per-unit usage plan where customers are charged a flat rate for each reported unit. Requires an existing meter value calculation — use create_meter_setup first.

Parameter	Required	Description
`name`	Yes	Display name for the plan
`meter_value_calculation_id`	Yes	`mvc_...` id from `create_meter_setup`
`unit_amount.quantity`	Yes	Price per unit as a decimal string (e.g. `"0.002"`)
`unit_amount.currency`	Yes	ISO 4217 currency code
`reference`	No	Unique reference slug. Auto-generated if omitted.
`billing_in_advance`	No	Default `false` (usage billed after accrual).
`billing_entity_id`	No	`bile_...` id. Optional.

`create_tiered_plan`

Creates a usage-based plan with graduated pricing tiers. The final tier should omit up_to to be unbounded. Requires an existing meter value calculation.

Parameter	Required	Description
`name`	Yes	Display name for the plan
`meter_value_calculation_id`	Yes	`mvc_...` id from `create_meter_setup`
`tiers`	Yes	Ordered array of tier objects: `{ up_to?, amount: { quantity, currency } }`
`pricing_type`	No	Tier strategy: `TIERED` (graduated, default), `TOP_TIERED`, or `STAIR_STEP`
`reference`	No	Unique reference slug. Auto-generated if omitted.
`billing_in_advance`	No	Default `false`.
`billing_entity_id`	No	`bile_...` id. Optional.

`create_hybrid_plan`

Creates a pricing plan composed of multiple line items in a single call. Each item can be a fixed fee, flat-rate usage, or tiered usage — useful for plans that combine a recurring platform fee with consumption-based charges.

Parameter	Required	Description
`name`	Yes	Display name for the plan
`items`	Yes	Array of item objects. Each item requires `type` (`FIXED`, `USAGE`, `USAGE_FLAT`, or `USAGE_TIERED`), `name`, and either `amount`, `unit_amount`, or `tiers` depending on type. Usage items also require `meter_value_calculation_id`.
`reference`	No	Unique reference slug. Auto-generated if omitted.
`billing_entity_id`	No	`bile_...` id. Optional.

`create_meter_setup`

Creates a meter, a meter value, and a meter value calculation in one step. The returned meter_value_calculation_id is used when creating usage-based or tiered plans.

Parameter	Required	Description
`meter_name`	Yes	Display name for the meter (e.g. `"API requests"`)
`meter_reference`	Yes	Unique reference slug (e.g. `"api-requests"`)
`value_name`	Yes	Display name for the meter value (e.g. `"count"`)
`value_reference`	Yes	Unique reference for the meter value
`calculation_type`	No	Aggregation method: `SUM` (default), `MAX`, `MIN`, `AVERAGE`, or `UNIQUE`
`calculation_name`	No	Defaults to `"<meter_name> <calc>"`
`calculation_reference`	No	Defaults to `"<meter_reference>-<calc>"`
`value_type`	No	Data type of the meter value. Default `NUMBER`.
`persist`	No	Whether to persist the calculation output. Default `false`.

`create_checkout_link`

Generates a hosted checkout URL that an end-customer can open to complete payment against an existing pricing plan version. No customer record needs to exist beforehand.

Parameter	Required	Description
`pricing_plan_version_id`	Yes	`ppve_...` id of the plan version to activate
`billing_entity_id`	No	`bile_...` id. Defaults to your first billing entity.
`billing_period.type`	No	`MONTH`, `YEAR`, `WEEK`, or `DAY`
`billing_period.value`	No	Number of period units (e.g. `1`, `3`, `12`)
`billing_time`	No	`EXACT` (default) or `END_OF_PERIOD`
`expiry_days`	No	Link lifetime in days. Default `30`.
`success_url`	No	HTTPS URL to redirect the customer to after checkout

`solvimon_api_call`

A raw escape hatch for any Solvimon API request not covered by the dedicated tools above.

Parameter	Required	Description
`method`	Yes	HTTP method: `GET`, `POST`, `PATCH`, `PUT`, or `DELETE`
`path`	Yes	API path starting with `/v1/...` (e.g. `/v1/customers`)
`body`	No	Request body as a JSON string
`query`	No	Query parameters as a JSON map of `string → string`
`target`	No	Solvimon service to call: `CONFIG` (default), `TRANSACTION`, `EVENT`, or `IDENTITY`

Example prompts

Once connected, you can interact with Solvimon using plain language. Here are a few examples:

“Check my Solvimon account and list my billing entities.”
“Create a flat monthly plan called Starter at €29/month.”
“Set up a meter for API requests, then create a usage plan at €0.002 per request.”
“Create a hybrid plan with a €99 platform fee and tiered pricing for active seats.”
“Generate a checkout link for pricing plan version ppve_abc123 with a 7-day expiry.”