Subscription Platform
Billsby MCP connector
The Billsby connector brings your Billsby customers, subscriptions, invoices, payments, plans, products, add ons and allowances into Claude, ChatGPT, Cursor and any MCP client, so your team can look up accounts, fix billing problems and set up plans by asking in plain language.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Billsby to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Billsby once
-
Open Connections, choose Add connection, and pick Billsby.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Billsby API key. One person generates a token in Billsby and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Billsby to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Billsby to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Billsby to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Billsby to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Billsby through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Chase and settle unpaid invoices
Pull up every open Billsby invoice, retry the card on the ones that failed, and mark the ones paid by bank transfer as paid offline, all from one conversation.
-
Finance
Write off or refund a disputed invoice
When a customer disputes a charge, find the Billsby invoice, check the payments against it, then issue the refund or write it off with a clear record of who did it.
-
Support
Answer a billing question mid-ticket
Look up the Billsby customer by ID while the ticket is open, see their invoices, payments, add ons and allowances, and give the customer a straight answer without switching tabs.
-
Support
Catch the customer record up after a call
Update a Billsby customer's contact details or account information right after speaking with them, so the next invoice goes to the right person.
-
Sales
Set up a new customer on Billsby
Create the Billsby customer as soon as the deal closes, with the right product and plan, instead of handing a spreadsheet row to billing.
-
Product
Launch a new plan or product
Create a Billsby product, add the plans that sit under it, and review the existing add ons and allowances so the new pricing lines up with what is already on offer.
Try asking
- “List Billsby invoices unpaid for more than 30 days.”
- “Reattempt payment on last week's failed Billsby invoices.”
- “Which add-ons do our top 20 customers hold?”
AI tools
Billsby tools for your AI agents
53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Billsby, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Billsby gets you
6 screens from the product, each doing one job for your Billsby account.
The agent
Ask about invoices, get real answers.
Plain language questions run against live Billsby customers, invoices and payments.
- customers
- invoices
- payments
- add-ons
Ask Elaichi to work across your apps.
List Billsby invoices unpaid for more than 30 days.
Reattempt payment on last week's failed Billsby invoices.
Which add-ons do our top 20 customers hold?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Billsby.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
53 Billsby tools ready to call.
Customers, invoices, payments and add-ons are covered without writing custom code.
- List all Billsby customers
- Delete a Billsby customer by ID
- Get single Billsby customer by ID
- Update a Billsby customer by ID
Toolboxes
Every team gets its own toolbox.
Finance, support and revenue each see a curated slice of Billsby.
- Finance
- Billing operations
- Customer support
- Sales
Shared connections
Teammates bill without touching a credential.
One connected Billsby account, shared with named teams and members, keys stay hidden.
- Finance EMEA
- Billing ops
- Support tier 1
- Sales US
Audit log
Every refund is written down.
When, who, what happened, type and resource for each Billsby call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your dunning digest.
Billsby invoices are fetched, grouped, drafted, approved by a person, then posted back.
Billsby digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch customers
Billsby
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Billsby
Queued
Collections and dashboards
Billing numbers arrive before you ask.
Four metrics, 14 days of new customers and a team breakdown, refreshed on schedule.
Billsby health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Invoices
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Finance EMEA 34%
Billing ops 27%
Support tier 1 21%
Sales US 18%
FAQ
Frequently asked questions
How do I connect Billsby to Claude?
Connect Billsby in Elaichi first: Billsby connects with an API key, so you paste a key from your Billsby account into Elaichi and the connection is live. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and Billsby is ready to use.
Does Billsby work with ChatGPT and Cursor as well as Claude?
Yes. Once Billsby is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Billsby once and every client picks it up, with the same restrictions and the same audit log.
What can an AI agent actually do with my Billsby data?
An agent connected to Billsby can list and look up customers, create new ones and update their details, and remove a customer if that is allowed. It can find invoices and payments, refund an invoice, retry a failed payment, mark an invoice as paid offline or write it off, and browse or create products and plans, including add ons and allowances. Because Billsby exposes a lot of actions, short concrete asks such as "refund invoice 4821" work better than long paragraphs.
Does connecting Billsby give the AI access to my whole billing account?
The connection can do only what the Billsby API key it was set up with is allowed to do, and Elaichi can narrow that further but never widen it. Every person still signs in to Elaichi as themselves, so each call is tied to a named user, and restrictions in Elaichi decide which Billsby actions that user's team can reach at all.
Can I stop an agent from deleting or changing things in Billsby?
Yes. Restrictions in Elaichi work per action, so you can allow looking up Billsby customers and invoices while blocking deleting customers, issuing refunds or writing off invoices. A blocked action is never shown to the AI client in the first place, so no prompt, however worded, can reach it.
What happens to a Billsby connection when someone leaves?
Offboarding a person in Elaichi ends their access to Billsby at once, across Claude, ChatGPT, Cursor and every other client they used. If they connected a Billsby account that was shared with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Billsby once in Elaichi removes it from every client.
Put Billsby in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.