Read, create, update and cancel order quotes for public bodies in Chorus Pay. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Chorus Pay connector, then ask in plain words. The AI picks the tools.
For suppliers that send quotes to public bodies and follow their acceptance in Chorus Pay.
List the orders that still wait for the client to accept. Open one order to read its status and client.
Read an order to get its Chorus Pay link and status. Pass the link to the procurement team.
Create an order quote in draft status. The quote is not sent to the client. Repeating the same call does not create a second quote.
Changes dataChange the redirect URL or the metadata of an order. Metadata keys you send are added or overwritten; other keys stay.
Changes dataCancel an order in Chorus Pay. The client gets an email. The cancel fails once the invoice is filed on Chorus Pro.
Changes dataThe login page asks for your Chorus Pay live API key.
Create it in Chorus Pay → Paramètres → Clés API. The key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"chorus-pay": {
"url": "https://chorus-pay.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"chorus-pay": {
"type": "http",
"url": "https://chorus-pay.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Chorus Pay live API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Chorus Pay server only. Ask your AI to run choruspay_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with choruspay_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with choruspay_upgrade before then undoes the cancel. Or write to [email protected].
choruspay_list_orderschoruspay_get_orderchoruspay_create_orderchoruspay_update_orderchoruspay_cancel_orderchoruspay_usage_statuschoruspay_request_featurechoruspay_upgradechoruspay_cancel_subscriptionTrack the quotes waiting for client acceptance. Copy the payment link for a procurement team. Create a quote for a public body. Update the redirect URL or metadata of an order. Cancel an order the client withdrew. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Chorus Pay. The server calls the Chorus Pay API with your own Chorus Pay access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Chorus Pay live API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Chorus Pay live API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Chorus Pay API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Chorus Pay.
Yes, if you approve it. 3 of the 5 Chorus Pay tools can create or change data. The other 2 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Chorus Pay server only. Cancel any time: your paid plan then runs to the end of the paid period. Run choruspay_usage_status to see how many calls you used.
Ask the AI to run choruspay_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run choruspay_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with choruspay_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.