Diligent MCP connector
The Diligent connector brings robots, working files, tasks, jobs and agents into Elaichi, so once Diligent is connected, Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can list, create and run them inside each person's own access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Diligent robots ran overnight and did any jobs fail?
Working in Diligent with Elaichi
-
List all Diligent org agents
-
Get single Diligent org flow key by ID
-
List all Diligent org robots
How to connect Diligent to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Diligent 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.
Diligent 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.
Diligent 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.
Diligent 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.
Diligent 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 Diligent 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 Diligent through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Diligent is logged.
-
Internal audit
Check which robots ran overnight
Ask which Diligent robots ran, which jobs finished and which activations are still open before the morning stand-up. No need to open Diligent and click through each robot.
-
Compliance
Keep a current list of every robot
Pull every robot in the Diligent org, with its latest version, into one answer so the control inventory matches what is actually deployed.
-
Audit analytics
Stage a new robot version for review
Upload the revised script as a robot file, create a new version and hand it to a reviewer, all from the chat window where the change was discussed.
-
Risk
Kick off a robot task after a control change
When a control owner reports a change, create a Diligent robot task to rerun the relevant test and confirm it was picked up as a job.
-
IT
Tidy up agents and working files
List the agents registered to the org, retire robots nobody owns and bulk delete stale working files so the Diligent environment stays clean.
-
Finance controls
Pull a robot file for the workpaper
Fetch the output file from last night's reconciliation robot and drop it straight into the workpaper, without hunting through Diligent folders.
Try asking
- “Which Diligent robots ran overnight and did any jobs fail?”
- “List every robot in our Diligent org with its latest version.”
- “Create a task to run the vendor payments robot tonight.”
What connecting Diligent gets you
6 screens from Elaichi, each doing one job for your Diligent account.
Ask Elaichi to work across your apps.
Which Diligent robots ran overnight and did any jobs fail?
List every robot in our Diligent org with its latest version.
Create a task to run the vendor payments robot tonight.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Diligent robots in plain language.
Three starter prompts answered from live Diligent robots, jobs and working files.
Copy the endpoint
AI apps
One Diligent endpoint for every MCP client.
Claude, ChatGPT and Cursor reach Diligent through one governed endpoint, no SDK, no shared API key.
Tool catalog
394 Diligent tools, no connector code needed.
Robots, robot apps, working files, versions, tasks, jobs and agents, listed with resources and methods.
Toolboxes
Every team gets its own Diligent toolbox.
Internal audit, compliance and IT each see the Diligent tools their work calls for.
Shared connections
Teammates use Diligent without seeing the key.
One person connects Diligent, shares it with teams, and nobody else handles a credential.
Audit log
Know who ran which Diligent robot.
Every call records when, who, what happened, the type and the Diligent resource touched.
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.
Diligent digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch robots
Diligent
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
Diligent
Queued
Workflows
A schedule runs Diligent work end to end.
Overnight jobs are fetched, grouped, drafted into a digest, approved, then posted back to Diligent.
Diligent health
Refreshed 4 minutes ago · every 15 minutes · from the robots collection
Robots
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Robots created
Last 14 days
By team
Share of activity
Internal audit 34%
Compliance 27%
Risk 21%
IT 18%
Collections and dashboards
Diligent robot health, computed without a model.
Four metrics, fourteen days of robots created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Diligent
All three can connect Diligent 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 Diligent tools | Allow or restrict single Diligent 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 Diligent 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.
Diligent tools for your AI agents
394 tools are ready to call through Elaichi's MCP endpoint the moment you connect Diligent, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 255 of 394 Diligent tools here. Connect Diligent and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Diligent to Claude?
Two steps. In Elaichi, choose the Diligent connector and paste the API key from your Diligent account, 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 https://api.elaichi.ai/mcp. Sign in as yourself and Diligent robots, jobs and tasks are available in the chat.
Does Diligent work with ChatGPT and Cursor as well as Claude?
Yes. Once Diligent 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 Diligent once and every client picks it up.
What can an AI agent actually do with my Diligent data?
It can list the robots, agents and robot apps in your Diligent org, show which jobs and activations ran, create or update a robot, add a new robot version or working file, download a robot file and create a robot task to run a test. Short, concrete asks work best, such as which Diligent jobs failed last night, rather than long paragraphs.
Does connecting Diligent give the AI access to everything in my org?
No. Every call to Diligent runs inside the access of the person who signed in, so the agent sees the robots, files and jobs that person can already see in Diligent and nothing more. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Diligent?
Yes. Restrictions in Elaichi work per action, so you can allow listing Diligent robots and jobs while restricting deleting a robot or bulk deleting working files, for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Diligent connection when someone leaves?
Offboarding that person in Elaichi ends their access to Diligent at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Diligent connection keeps working for everyone else on the team. If you ever want Diligent gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Diligent MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Diligent 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 Diligent?
Yes. Both let Claude, ChatGPT or Cursor use Diligent. 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 Diligent call.
How is Elaichi different from Composio for Diligent?
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 Diligent: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Diligent 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