Stax.ai MCP connector
The Stax.ai connector brings your stacks, documents, and TPA plans to Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so your team can find, file, and organize accounting paperwork in plain language while every action is logged.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
List the stacks with documents added this week.
Working in Stax.ai with Elaichi
-
List all Stax.ai stacks
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Stax.ai to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Stax.ai 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.
Stax.ai 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.
Stax.ai 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.
Stax.ai 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.
Stax.ai 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 Stax.ai 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 Stax.ai through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Stax.ai is logged.
-
Accounting
File the month's paperwork into stacks
Ask for the invoices and statements that came in this month and have them moved into the right client stack, with duplicates flagged before anything is filed twice.
-
Retirement plan administration
Set up a new TPA plan record
When a new plan client signs, create the TPA plan in Stax.ai and check the existing plan records so nothing is entered twice.
-
Operations
Check what processing is still running
See which document jobs are in progress and which finished, so you know when a batch is ready for review.
-
Compliance
Pull a document out of the archive
Search archived documents for a specific plan year or client, restore the one an auditor asked for, and download it for the response.
-
Client services
Find what a client sent this week
List recently added documents for a client, open the one they are asking about, and confirm which stack it landed in.
-
Office administration
Clean up stacks after a project closes
Archive the documents in a finished stack, copy anything that belongs elsewhere, and update the stack name so the workspace stays tidy.
Try asking
- “List the stacks with documents added this week.”
- “How many documents sit in the Payables stack?”
- “Move last month's invoices into the Archive stack.”
What connecting Stax.ai gets you
6 screens from Elaichi, each doing one job for your Stax.ai account.
Ask Elaichi to work across your apps.
List the stacks with documents added this week.
How many documents sit in the Payables stack?
Move last month's invoices into the Archive stack.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Stax.ai stacks, get answers.
Type a question in plain language and read answers from live Stax.ai records.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Stax.ai.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
32 Stax.ai tools ready to call.
Stack and document resources with their methods listed, no custom code to write.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Curate Stax.ai stack and document tools per team and scope each toolbox separately.
ElaichiConnectionsShared connections
Teammates use Stax.ai without a credential.
See who connected each Stax.ai account and how many teams and members share it.
ElaichiAudit logAudit log
Every Stax.ai call is on record.
When, who, what happened, type and resource for each stack and document call.
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.
Stax.ai digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch stacks
Stax.ai
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
Stax.ai
Queued
Automations
A schedule fires, a digest posts back.
Six steps fetch Stax.ai documents, group them, draft a digest, then a person approves.
Stax.ai health
Refreshed 4 minutes ago · every 15 minutes · from the stacks collection
Stacks
1,284 ↓ 12%
Documents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Stacks created
Last 14 days
By team
Share of activity
Accounts payable 34%
Accounts receivable 27%
Bookkeeping 21%
Audit EMEA 18%
Collections and dashboards
Stax.ai numbers arrive before you ask.
Four metrics, 14 days of documents created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Stax.ai
All three can connect Stax.ai 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 Stax.ai tools | Allow or restrict single Stax.ai 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 Stax.ai 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.
Stax.ai tools for your AI agents
32 tools are ready to call through Elaichi's MCP endpoint the moment you connect Stax.ai, 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 Stax.ai to Claude?
Connect Stax.ai in Elaichi by pasting your Stax.ai API key when asked, then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once both steps are done, Claude can work with your Stax.ai stacks, documents, and TPA plans.
Does Stax.ai work with ChatGPT and Cursor as well as Claude?
Yes. Once Stax.ai is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Stax.ai once and every client you use picks it up.
What can an AI agent actually do with my Stax.ai data?
An agent connected to Stax.ai can list and open your stacks and documents, upload new files, move or copy documents between stacks, archive and restore them, download a file you need, and find duplicates or recently added paperwork. It can also look up, create, and update TPA plans and check on document jobs still processing. Short, concrete asks such as "find last month's statements for Acme" work better than long paragraphs.
Does connecting Stax.ai give the AI access to every stack and document?
No. Access follows the person who signed in, so the AI only sees the Stax.ai stacks, documents, and TPA plans that person's own Stax.ai access allows. Elaichi can narrow that further with restrictions, but it can never widen it beyond what the person already has.
Can I stop an agent from deleting or changing things in Stax.ai?
Yes. In Elaichi you can restrict individual actions for Stax.ai, such as deleting documents, deleting stacks, or updating TPA plans, while leaving reading and filing allowed. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a Stax.ai connection when someone leaves?
Offboarding a person in Elaichi ends their access to Stax.ai through every client at once. A shared Stax.ai connection keeps working for everyone else on the team. If you want to remove Stax.ai entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.
Does the Stax.ai MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Stax.ai 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 Stax.ai?
Yes. Both let Claude, ChatGPT or Cursor use Stax.ai. 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 Stax.ai call.
How is Elaichi different from Composio for Stax.ai?
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 Stax.ai: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Stax.ai 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