Aleph MCP connector
The Aleph connector brings your tables, blocks, dashboards and data source refreshes to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask planning questions and update models inside their own Aleph access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Show me the variance to budget in the opex table this month
Working in Aleph with Elaichi
-
List tables
-
Get table
-
Search values in tables
How to connect Aleph to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Aleph 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.
Aleph 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.
Aleph 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.
Aleph 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.
Aleph 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 Aleph 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 Aleph through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Aleph is logged.
-
FP&A
Explain a variance before the review
Ask which lines in the opex table moved against budget this month and get the answer from the live table, not a screenshot from last week.
-
Accounting
Refresh actuals after the close
Trigger a refresh of the ERP source once the books are closed, then confirm the actuals tables picked up the new period.
-
Revenue operations
Check bookings against the forecast
Search the bookings table for a region or rep and compare it with the forecast block without opening the model.
-
People
Keep the headcount plan current
Find the open roles in the headcount table and update the pass-through columns for start dates once offers are signed.
-
Leadership
Read the board dashboard in plain words
Ask what changed on the board dashboard since last quarter and get a short summary of each block that moved.
-
Data
Tidy blocks and dashboards across models
List every dashboard, find the blocks that point at a retired table, and update them in one pass.
Try asking
- “Show me the variance to budget in the opex table this month”
- “Which blocks on the board dashboard changed since last close?”
- “Refresh the ERP data source and tell me when it finishes”
What connecting Aleph gets you
6 screens from Elaichi, each doing one job for your Aleph account.
Ask Elaichi to work across your apps.
Show me the variance to budget in the opex table this month
Which blocks on the board dashboard changed since last close?
Refresh the ERP data source and tell me when it finishes
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Aleph a question, get live numbers.
Ask about tables, blocks and dashboards in plain language and get answers from live records.
Copy the endpoint
AI apps
One endpoint brings Aleph to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Aleph through one governed endpoint, no SDK, no shared key.
Tool catalog
14 Aleph tools, ready without writing code.
Tables, blocks, dashboards, data sources and pass-through columns, covered with no custom code.
Toolboxes
Every team gets its own Aleph toolbox.
Finance, revenue and people teams each work from a toolbox scoped to their planning.
Shared connections
Share Aleph access, never share a credential.
One person connects Aleph, teammates work through it, and nobody else sees a login.
Audit log
Every Aleph call is logged with a name.
See who refreshed a source, changed a block or edited a dashboard, and when.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Aleph digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tables
Aleph
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
Aleph
Queued
Workflows
A schedule runs the Aleph close digest.
Tables are fetched, grouped and drafted into a digest, approved, then posted back to Aleph.
Aleph health
Refreshed 4 minutes ago · every 15 minutes · from the tables collection
Tables
1,284 ↓ 12%
Blocks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tables created
Last 14 days
By team
Share of activity
FP&A 34%
Accounting 27%
Revenue ops 21%
People 18%
Collections and dashboards
Aleph health numbers arrive without being asked.
Four metrics, a 14 day chart and a team breakdown, computed on schedule, no model.
Why connect Aleph's MCP server through Elaichi
Aleph builds and runs this MCP server. Elaichi sits in front of it, so Aleph's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Aleph's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Aleph's tools at the same Elaichi address as every other connected app. Nobody adds Aleph's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Aleph sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Aleph's server. By default, a tool Aleph does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Aleph
Aleph builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Aleph team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Aleph
All three can connect Aleph 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 Aleph tools | Allow or restrict single Aleph 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 Aleph 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.
Aleph tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Aleph, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Aleph builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Aleph to Claude?
Connect Aleph in Elaichi first, where you sign in to Aleph over OAuth and approve access as yourself. 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. Claude asks you to sign in to Elaichi, and Aleph is available in your next conversation.
Does Aleph work with ChatGPT and Cursor as well as Claude?
Yes. The Aleph connection you set up in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Aleph once and every client uses it.
What can an AI agent actually do with my Aleph data?
An agent can list and open your Aleph tables, search for values inside them, read and update blocks, read and update dashboards, kick off a refresh of a connected data source, and change pass-through columns on a table. In practice that means asking why a line moved, checking a forecast against bookings, or refreshing actuals after close. Short, concrete asks such as find the Q3 opex table work better than long paragraphs.
Does connecting Aleph give the AI access to every model and dashboard?
No. Every call through Elaichi runs as the person who signed in to Aleph, so the agent sees only the tables, blocks and dashboards that person already has. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Aleph grants.
Can I stop an agent from changing blocks or triggering refreshes in Aleph?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Aleph tables and dashboards while restricting changes to blocks, dashboards or pass-through columns, or restricting refreshes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to an Aleph connection when someone leaves?
Offboarding a person in Elaichi ends their access to Aleph through every client at once. If they had shared their Aleph connection with a team, the connection keeps working for everyone else. Disconnecting Aleph once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Aleph MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Aleph 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 Aleph?
Yes. Both let Claude, ChatGPT or Cursor use Aleph. 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 Aleph call.
How is Elaichi different from Composio for Aleph?
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 Aleph: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Aleph 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