Archer MCP connector
The Archer connector brings Archer risk, compliance, and audit records into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can find, update, and move records through workflows inside their own Archer access.
- Connects with an API key
- Free 14-day trial
- No credit card
List open high risk records in Archer with no owner.
Working in Archer with Elaichi
-
List all Archer records
-
Get single Archer record by ID
-
List all Archer content endpoints
How to connect Archer to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Archer 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.
Archer 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.
Archer 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.
Archer 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.
Archer 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 Archer 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 Archer through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Archer is logged.
-
Compliance
Catch a control record up after testing
Ask for the control, describe what the test showed, and have the record updated with the result and an attached evidence file. The change lands in the record history like any other edit.
-
Risk
Review the open risk register in plain language
Ask which risks in Archer are rated high and still unowned, or which assessments are overdue. Get an answer from live records rather than a report someone exported last week.
-
Audit
Pull the full history of a finding
Before a review meeting, ask for everything that happened to a finding since it was raised, including who changed what and when. The connector reads the record history and summarizes it.
-
Security
Log an incident record without opening Archer
Describe the incident in a sentence and have a new record created in the right Archer application, with the details filled in. Advance it through its workflow when triage is done.
-
Vendor management
Check where a third party assessment stands
Ask which vendor assessments are waiting on a workflow action and who needs to act. Move the ones that are ready to the next stage.
-
IT
Watch data feeds and chase failed runs
Ask which Archer data feeds ran overnight, which ones failed, and what the run messages say. Kick off a feed again once the source is fixed.
Try asking
- “List open high risk records in Archer with no owner.”
- “Summarize the history of finding FND-0412 since it was raised.”
- “Which Archer data feeds failed overnight and why?”
What connecting Archer gets you
6 screens from Elaichi, each doing one job for your Archer account.
Ask Elaichi to work across your apps.
List open high risk records in Archer with no owner.
Summarize the history of finding FND-0412 since it was raised.
Which Archer data feeds failed overnight and why?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Archer questions in plain language.
Get answers from live risk, control and finding records, not from last week's export.
Copy the endpoint
AI apps
One Archer endpoint for every client.
Claude, ChatGPT and Cursor use the same governed endpoint, with no SDK or shared API key.
Tool catalog
108 Archer tools ready without writing code.
Records, applications, levels, workflow actions, attachments and data feeds, all covered from day one.
Toolboxes
Each team gets its own Archer toolbox.
Compliance, Risk and Audit each work from a toolbox scoped to what they do.
Shared connections
Share an Archer connection, never a credential.
One person connects Archer, teams work through it, and nobody else sees the API key.
Audit log
Every Archer action, answered by name.
The log shows who touched which record, when, and what happened to it.
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.
Archer digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch records
Archer
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
Archer
Queued
Workflows
A schedule starts Archer work on its own.
New findings are fetched, grouped, drafted into a digest, approved by a person, and posted back.
Archer health
Refreshed 4 minutes ago · every 15 minutes · from the records collection
Records
1,284 ↓ 12%
Applications
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Records created
Last 14 days
By team
Share of activity
Compliance 34%
Risk 27%
Internal audit 21%
Security operations 18%
Collections and dashboards
Archer health numbers, computed without a model.
Four metrics, fourteen days of records created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Archer
All three can connect Archer 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 Archer tools | Allow or restrict single Archer 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 Archer 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.
Archer tools for your AI agents
108 tools are ready to call through Elaichi's MCP endpoint the moment you connect Archer, 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 Archer to Claude?
Connect Archer in Elaichi first by pasting an Archer API key, which is the only sign-in step. 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 with your Elaichi account and Archer is available in Claude.
Does Archer work with ChatGPT and Cursor as well as Claude?
Yes. Once Archer 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 Archer once and every client sees it.
What can an AI agent actually do with my Archer data?
An agent connected to Archer can find records in any Archer application, read a record's history, create and update records, attach files, and move a record through its workflow. It can also check which data feeds ran and whether they failed. Short, concrete asks work better than long paragraphs, for example asking for the open findings owned by one person.
Does connecting Archer give the AI everything in my Archer instance?
No. Every call runs as the person who signed in, so the agent only sees the Archer applications and records that person already has access to. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what Archer already allows.
Can I stop an agent from deleting or changing things in Archer?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Archer records or creating workflow actions for a role or for one person while leaving reading alone. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Archer connection when someone leaves?
Offboarding a person in Elaichi ends their Archer access through every client at once. If they connected a shared Archer connection, it keeps working for everyone else it was shared with. Disconnecting Archer once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Archer MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Archer 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 Archer?
Yes. Both let Claude, ChatGPT or Cursor use Archer. 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 Archer call.
How is Elaichi different from Composio for Archer?
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 Archer: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Archer 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