Rillet MCP connector
The Rillet connector brings your chart of accounts, subsidiaries, customers, products and contracts to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and update Rillet records inside their own access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me contracts created this quarter and their invoice schedules.
Working in Rillet with Elaichi
-
List all Rillet accounts
-
List all Rillet subsidiaries
-
Get single Rillet subsidiary by ID
How to connect Rillet to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Rillet 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.
Rillet 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.
Rillet 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.
Rillet 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.
Rillet 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 Rillet 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 Rillet through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Rillet is logged.
-
Finance
Preview an invoice schedule before signing
Ask for the invoice schedule a new contract would produce before it is created in Rillet, and check the billing dates and amounts line up with what the customer agreed.
-
Accounting
Check the chart of accounts across subsidiaries
Pull up every account in Rillet, see which subsidiary it belongs to, and add a new account when a new expense category appears.
-
Revenue operations
Set up a contract from the signed order
Once the order form is signed, create the Rillet contract with the right customer and products, then pull it back up by ID to confirm it looks right.
-
Sales
Add a new customer to Rillet quickly
Create the customer record in Rillet as soon as the deal closes, and fix the billing details when the customer sends a correction.
-
Pricing
Keep the product catalog current
List every product in Rillet, update names and prices when packaging changes, and retire products nobody sells anymore.
-
Controller
See who can do what in Rillet
List members, roles and role assignments in Rillet before an audit, and spot anyone whose role no longer matches their job.
Try asking
- “Show me contracts created this quarter and their invoice schedules.”
- “Preview the invoice schedule for the Acme annual contract.”
- “Which customers have no active contract in Rillet?”
What connecting Rillet gets you
6 screens from Elaichi, each doing one job for your Rillet account.
Ask Elaichi to work across your apps.
Show me contracts created this quarter and their invoice schedules.
Preview the invoice schedule for the Acme annual contract.
Which customers have no active contract in Rillet?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about contracts and customers in plain English.
Answers come from live Rillet contracts, customers and products, not a stale export.
Copy the endpoint
AI apps
One endpoint brings Rillet to every AI client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
121 Rillet tools, ready with no code.
Accounts, subsidiaries, products, customers and contracts are covered without writing a line of code.
Toolboxes
Every team gets its own Rillet toolbox.
Finance sees the chart of accounts, sales sees customers and products, nobody sees more than needed.
Shared connections
Share one Rillet connection without sharing the key.
Teammates work through the connection while the API key stays with whoever connected it.
Audit log
Every Rillet call is logged with a name.
See who created a customer or changed a product, when, and from which client.
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.
Rillet digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contracts
Rillet
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
Rillet
Queued
Automations
A schedule starts the work, a person approves.
New Rillet contracts are fetched, grouped by subsidiary, drafted into a digest, approved, then posted back.
Rillet health
Refreshed 4 minutes ago · every 15 minutes · from the contracts collection
Contracts
1,284 ↓ 12%
Customers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contracts created
Last 14 days
By team
Share of activity
Finance 34%
Revenue Ops 27%
Controller 21%
Sales 18%
Collections and dashboards
Rillet health numbers arrive before anyone asks.
Contracts created over 14 days, split by team, computed on a schedule with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Rillet
All three can connect Rillet 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 Rillet tools | Allow or restrict single Rillet 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 Rillet 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.
Rillet tools for your AI agents
121 tools are ready to call through Elaichi's MCP endpoint the moment you connect Rillet, 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 Rillet to Claude?
Connect Rillet in Elaichi first, which asks you to paste an API key from your Rillet workspace, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Rillet and no client ID or secret to generate. Once Claude finishes signing you in, Rillet is available in the conversation.
Does Rillet work with ChatGPT and Cursor as well as Claude?
Yes. Connect Rillet once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. There is nothing separate to set up for each one.
What can an AI agent actually do with my Rillet data?
It can look up customers, products, contracts, subsidiaries and the chart of accounts in Rillet, create and update customers and products, create contracts, and preview the invoice schedule a contract would produce. It can also list members, roles and who holds which role, and add payment settings. Because Rillet has a large set of tools, short concrete asks like show contracts for Acme work better than long sentences.
Does connecting Rillet give the AI access to every subsidiary?
No. Every call runs inside the access of the person who signed in, so the AI sees the Rillet subsidiaries, accounts and contracts that person can already see, and nothing more. Elaichi can narrow that further with roles and restrictions, but it can never widen it.
Can I stop an agent from deleting or changing things in Rillet?
Yes. Restrictions in Elaichi work per action, so you can allow reading Rillet contracts and customers while restricting deleting a customer or updating a product. 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 a Rillet connection when someone leaves?
Offboarding the person in Elaichi ends their Rillet access at once, in every client they used. If they had shared a Rillet connection with the team, it keeps working for everyone else. When you want Rillet gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Rillet MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Rillet 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 Rillet?
Yes. Both let Claude, ChatGPT or Cursor use Rillet. 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 Rillet call.
How is Elaichi different from Composio for Rillet?
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 Rillet: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Rillet 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