Alloy MCP connector
The Alloy connector brings customer accounts, bank accounts, review cases, evidence, alerts, batches, and custom lists into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so your compliance team can ask questions and work cases in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
List open Alloy cases created this week by reviewer.
Working in Alloy with Elaichi
-
List all Alloy bank accounts
-
Get single Alloy bank account by ID
-
List all Alloy batches
How to connect Alloy to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Alloy 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.
Alloy 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.
Alloy 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.
Alloy 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.
Alloy 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 Alloy 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 Alloy through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Alloy is logged.
-
Compliance
Work through the open case queue
Ask for the cases waiting on review, pull up a single case with its evidence and alerts, and get a plain summary of what triggered it before you decide.
-
Fraud
Attach evidence and notes to a case
After looking into a suspicious application, add the evidence you found and record the work you did on the case, in the same conversation where you reviewed it.
-
Compliance
Keep custom lists current
Add a new entry to a blocklist or allowlist, publish a new version, and check which version is live, without opening the Alloy console.
-
Operations
Check on batch runs
Ask which batches are still in progress, which finished, and what came back for a specific batch by its ID.
-
Onboarding
Look up an applicant's account and bank details
Find an account, see the bank accounts tied to it, and correct account details when a customer sends updated information.
-
Risk
Review alerts across recent cases
List the evidence alerts raised this week, group them by type, and spot the patterns that need a closer look.
Try asking
- “List open Alloy cases created this week by reviewer.”
- “Summarize evidence attached to Alloy case 4821.”
- “Which Alloy accounts have bank accounts pending review?”
What connecting Alloy gets you
6 screens from Elaichi, each doing one job for your Alloy account.
Ask Elaichi to work across your apps.
List open Alloy cases created this week by reviewer.
Summarize evidence attached to Alloy case 4821.
Which Alloy accounts have bank accounts pending review?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Alloy cases in plain language.
The agent reads live Alloy cases, accounts and evidence to answer.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Alloy here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
138 Alloy tools ready without custom code.
Browse Alloy accounts, cases, batches, evidence and case works with their methods.
Toolboxes
Every team gets its own Alloy toolbox.
Compliance, fraud ops and onboarding each see the Alloy tools they need.
Shared connections
Teammates use Alloy accounts without the credential.
See who connected each Alloy account and which teams and members share it.
Audit log
Answer who touched which Alloy case.
Every call lands append only with time, person, action, type and resource.
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.
Alloy digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch cases
Alloy
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
Alloy
Queued
Automations
A schedule fires, an Alloy digest ships.
Six steps fetch Alloy cases, group them, draft, wait for approval, post back.
Alloy health
Refreshed 4 minutes ago · every 15 minutes · from the cases collection
Cases
1,284 ↓ 12%
Accounts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Cases created
Last 14 days
By team
Share of activity
Compliance US 34%
Fraud operations 27%
Onboarding 21%
Risk review 18%
Collections and dashboards
Alloy case volume computed, not asked for.
Four metrics, 14 days of new Alloy cases, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Alloy
All three can connect Alloy 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 Alloy tools | Allow or restrict single Alloy 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 Alloy 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.
Alloy tools for your AI agents
138 tools are ready to call through Elaichi's MCP endpoint the moment you connect Alloy, 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 Alloy to Claude?
Connect Alloy in Elaichi first: paste your Alloy API key when asked, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi with your own account and Alloy appears in Claude.
Does Alloy work with ChatGPT and Cursor as well as Claude?
Yes. Once Alloy 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 Alloy once and every client you use picks it up.
What can an AI agent actually do with my Alloy data?
With Alloy connected, an agent can look up accounts and their bank accounts, list and open review cases, read the evidence and alerts on a case, add new evidence and case notes, check batch results, create documents, and create or update custom lists and their versions. Because Alloy has a large set of actions, short concrete asks like "show me open cases from today" work better than long paragraphs.
Does connecting Alloy give the AI access to every case and list?
No. Every request to Alloy runs under the access of the person who signed in to Elaichi, so the agent sees only the cases, accounts, and lists that person could already reach. Elaichi can narrow that further, for example to read-only access, but it can never widen it beyond what the person already has.
Can I stop an agent from changing things in Alloy?
Yes. In Elaichi you can restrict the Alloy connection action by action, for example allowing case lookups while restricting updates to accounts or changes to custom lists. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to an Alloy connection when someone leaves?
When you offboard a person in Elaichi, their access to Alloy through every client ends at once, and the audit log keeps the record of what they did. A shared Alloy connection keeps working for everyone else on the team. If you disconnect Alloy in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the Alloy MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Alloy 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 Alloy?
Yes. Both let Claude, ChatGPT or Cursor use Alloy. 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 Alloy call.
How is Elaichi different from Composio for Alloy?
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 Alloy: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Alloy 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