Read clients, offers and invoices; create clients and offer drafts in Billify. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Billify connector, then ask in plain words. The AI picks the tools.
For businesses that send offers and track clients and invoices in Billify.
Search the newest 100 clients by company name, and read one client's contact details and number of invoices.
Create a client, or get the existing client with the same name. Then create an offer draft for them. You send the offer in Billify after you check the preview.
Changes dataList the newest offers with their line items, filtered by client or status. Open one for its amounts and dates.
List the newest invoices and open one for its amounts, dates, payment status and QR reference.
The login page asks for your Billify API key.
The Billify API needs the Business plan (CHF 49/month or CHF 490/year). A company admin creates the key in Billify under Settings → Team → API Schlüssel. Billify shows it only once. The key stops working if the admin who created it is removed or demoted. It is used only to call the Billify API on your behalf and 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": {
"billify": {
"url": "https://billify.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"billify": {
"type": "http",
"url": "https://billify.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 Billify 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 Billify server only. Ask your AI to run billify_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 billify_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 billify_upgrade before then undoes the cancel. Or write to [email protected].
billify_list_clientsbillify_get_clientbillify_list_offersbillify_get_offerbillify_list_invoicesbillify_get_invoicebillify_create_clientbillify_create_offerbillify_usage_statusbillify_request_featurebillify_upgradebillify_cancel_subscriptionFind a client before you add one. Create a client and an offer draft. Review open offers. Check invoice payment status. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Billify. The server calls the Billify API with your own Billify 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 Billify 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 Billify 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 Billify 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 Billify.
Yes, if you approve it. 2 of the 8 Billify tools can create or change data. The other 6 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 Billify server only. Cancel any time: your paid plan then runs to the end of the paid period. Run billify_usage_status to see how many calls you used.
Ask the AI to run billify_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 billify_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 billify_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.