Invoiced MCP connector
The Invoiced connector brings customers, invoices, payments and balances into Claude, ChatGPT and Cursor, so once connected, each person can create, send and check invoices inside their own Invoiced access with every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which customers are overdue on their latest invoice balance.
Working in Invoiced with Elaichi
-
Get single Invoiced customer by ID
-
Invoiced customers get balance
-
List all Invoiced customers
How to connect Invoiced to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Invoiced MCP connector for 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.
Invoiced MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Invoiced MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Invoiced MCP connector for 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.
Invoiced MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Invoiced 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.
What teams do with Invoiced through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Invoiced is logged.
-
Accounts receivable
Send a statement to a late payer
Ask for a customer's outstanding balance in Invoiced, then send them a statement by email, text message or letter without leaving the conversation.
-
Finance
Record a payment that arrived by wire
Log the payment against the right Invoiced invoice the moment the bank shows it, then confirm the customer's balance has dropped to zero.
-
Sales
Raise the invoice right after closing
Create the customer in Invoiced if they are new, draft the invoice with the agreed line items, and email it before the follow-up call is over.
-
Customer success
Consolidate open invoices into one
Roll a customer's scattered Invoiced invoices into a single consolidated invoice so they pay once instead of juggling five separate documents.
-
Support
Answer 'what do I owe you' quickly
Pull up a customer's balance and open invoices in Invoiced while they are on the phone, and resend the invoice by email or text on the spot.
-
Operations
Void a duplicate invoice before it ships
Find the duplicate in Invoiced, void it, and correct the customer record so the mistake never reaches the mailbox.
Try asking
- “Which customers are overdue on their latest invoice balance.”
- “Draft a statement email for our top five customers.”
- “Summarize invoices created this week by team.”
What connecting Invoiced gets you
6 screens from Elaichi, each doing one job for your Invoiced account.
Ask Elaichi to work across your apps.
Which customers are overdue on their latest invoice balance.
Draft a statement email for our top five customers.
Summarize invoices created this week by team.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Invoiced questions, get answers instantly.
Type a plain language question and get answers pulled straight from live Invoiced records.
Copy the endpoint
AI apps
One endpoint, every client, no shared keys.
Claude, ChatGPT, Cursor and Microsoft Copilot all connect to Invoiced through a single governed org endpoint.
Tool catalog
110 Invoiced tools, zero custom code.
Every customer, invoice and payment method Invoiced exposes is covered, ready to call.
Toolboxes
Every team gets its own Invoiced toolbox.
Finance, sales and support each work from a toolbox scoped to their Invoiced needs.
Shared connections
Delegated Invoiced access, no shared passwords.
Teammates use a shared Invoiced connection without ever seeing the underlying credential.
Audit log
Every Invoiced call is logged and traceable.
See who touched which customer or invoice and when, down to the method called.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Invoiced digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
Invoiced
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 Jake Morgan
Approve Deny -
Post the digest
Invoiced
Queued
Automations
A schedule fires, Invoiced work runs itself.
Records are fetched, grouped and drafted into a digest a person approves before it posts back.
Invoiced 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 NA 34%
Finance EMEA 27%
Sales 21%
Support 18%
Collections and dashboards
Invoiced health, refreshed on a schedule.
Four metrics and a 14 day chart of records created, broken down by team automatically.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Invoiced
All three can connect Invoiced to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Invoiced tools | Allow or restrict single Invoiced tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Invoiced call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Invoiced tools for your AI agents
110 tools are ready to call through Elaichi's MCP endpoint the moment you connect Invoiced, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Invoiced to Claude?
Connect Invoiced in Elaichi by pasting in an API key from your Invoiced settings. 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. Sign in to Elaichi when Claude asks and your Invoiced customers, invoices and payments are ready to work with.
Does Invoiced work with ChatGPT and Cursor as well as Claude?
Yes. Once Invoiced is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Invoiced once and every client picks it up.
What can an AI agent actually do with my Invoiced data?
It can look up a customer in Invoiced and tell you their balance, create or update customers and invoices, send an invoice or statement by email, text message or letter, record a payment, consolidate several invoices into one, and void an invoice raised by mistake. Invoiced offers a lot of actions, so short concrete asks such as 'send Acme their statement by email' work better than long paragraphs.
Does connecting Invoiced give the AI access to my whole billing account?
No. Every call to Invoiced runs as the person who signed in, so the agent can only see and change the customers, invoices and payments that person could already reach in Invoiced. Elaichi can narrow that further, for example to reading balances only, but it never widens what someone is allowed to do.
Can I stop an agent from deleting or voiding things in Invoiced?
Yes. Restrictions in Elaichi work per action, so you can allow creating and sending invoices in Invoiced while restricting deleting customers, voiding invoices or changing payments. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to an Invoiced connection when someone leaves?
Offboarding that person in Elaichi ends their access to Invoiced through every client at once. A shared Invoiced connection keeps working for everyone else on the team. If you ever want Invoiced gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Invoiced MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Invoiced is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Invoiced?
Yes. Both let Claude, ChatGPT or Cursor use Invoiced. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Invoiced call.
How is Elaichi different from Composio for Invoiced?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Invoiced: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Invoiced in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot