# 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.

Source: https://elaichi.ai/connectors/diligent/

## Facts

| | |
| --- | --- |
| Application | Diligent |
| Category | Compliance |
| AI tools | 394 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Diligent is connected

- 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.

## Connect Diligent in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Diligent.
2. Optionally set Share with, then press Connect.
3. Paste a Diligent API key. One person generates a token in Diligent and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Diligent tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Diligent MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Diligent MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Diligent tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Diligent through Elaichi

### Check which robots ran overnight

Internal audit. 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.

### Keep a current list of every robot

Compliance. Pull every robot in the Diligent org, with its latest version, into one answer so the control inventory matches what is actually deployed.

### Stage a new robot version for review

Audit analytics. 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.

### Kick off a robot task after a control change

Risk. 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.

### Tidy up agents and working files

IT. List the agents registered to the org, retire robots nobody owns and bulk delete stale working files so the Diligent environment stays clean.

### Pull a robot file for the workpaper

Finance controls. Fetch the output file from last night's reconciliation robot and drop it straight into the workpaper, without hunting through Diligent folders.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Diligent connection?

Yes. One person connects Diligent in Elaichi with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Diligent call.

### 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.

## All 394 Diligent tools

Every tool below is callable through https://api.elaichi.ai/mcp once Diligent is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Diligent org agents** (List). List all Robots Agents available to your Diligent organization. Returns: id, type, attributes. Required: org_id.
- **Get single Diligent org flow key by ID** (Get). Get the Flow Key for an organization in Diligent. Returns the flow key record with id, type, and attributes containing the public_key. Required: id.
- **List all Diligent org robots** (List). List all robots in your Diligent One Platform instance. Returns: id, type, attributes. Required: org_id.
- **Create a Diligent org robot** (Create). Create a robot in Diligent One to automate repetitive tasks using analytic scripts and configured scheduled tasks. Returns: id, type, attributes. Required: org_id, name.
- **Update a Diligent org robot by ID** (Update). Update a robot's attributes by id. Returns: id, type, attributes. Required: org_id, id, name.
- **Delete a Diligent org robot by ID** (Delete). Permanently delete a robot by id; its associated tasks are deleted as well. Returns: data. Required: org_id, id.
- **Get single Diligent robot robot app by ID** (Get). Get one analytic script from a robot in Diligent. Returns: id, type, attributes. Required: org_id, robot_id, id.
- **List all Diligent robot robot apps** (List). List a robot's analytic scripts in Diligent. Returns: id, type, attributes. Required: org_id, robot_id.
- **Create a Diligent robot robot app** (Create). Create a new analytic script for a robot in Diligent by uploading the script file. Returns: id, type, attributes. Required: org_id, robot_id, file.
- **Diligent robot robot apps activate** (Activate). Activate a robot app's script version in Diligent, making it the production version. Returns: id, type, attributes, relationships. Required: org_id, robot_id, robot_app_id. Only versions with a Python 3.11 runtime and HCL 3.0.* requirements can be activated.
- **List all Diligent robot robot activations** (List). List a robot's script activation history in Diligent. Returns: id, type, attributes, relationships. Required: org_id, robot_id.
- **List all Diligent robot robot files** (List). List related files for an ACL robot in Diligent. Returns robot file records with id, type, and attributes including filename and created_at. Required: org_id, robot_id.
- **Create a Diligent robot robot file** (Create). Upload a related file to an ACL robot in Diligent. Returns the uploaded file record with id, type, and attributes including filename and created_at. Required: org_id, robot_id, file.
- **List all Diligent robot working files** (List). Download a Diligent One Platform or Workflow robot working file by fetching its download url. Returns: id, type, attributes. Required: org_id, robot_id, filename.
- **Create a Diligent robot working file** (Create). Upload a working file to a Diligent One Platform or Workflow robot for use as script input. Returns: id, type, attributes. Required: org_id, robot_id, data.
- **Diligent robot working files bulk delete** (Delete). Delete a working file from a Diligent One Platform or Workflow robot. Returns data with the name of the deleted file. Required: org_id, robot_id, filename.
- **Get single Diligent robot version by ID** (Get). Get a specific script version of a robot in Diligent One Platform. Returns: id, type, attributes, relationships. Required: id, org_id, robot_id.
- **Create a Diligent robot version** (Create). Create a new script version for a Diligent One Platform robot or workflow robot. Returns: id, type, attributes, relationships, relationship. Requires org_id, robot_id and a body with comment, name, and raw flow json (python script, variables, system token user uid). Required: org_id, robot_id.
- **Get single Diligent org robot file by ID** (Get). Get the metadata for a related file in a Diligent ACL robot by id. Returns: id, type, attributes. Required: org_id, id.
- **Delete a Diligent org robot file by ID** (Delete). Delete a related file from a Diligent ACL robot by id. Returns the deleted file record: id, type, and attributes including filename and created_at. Required: org_id, id.
- **Get single Diligent robot file download by ID** (Get). Download an ACL robot related file in Diligent One by id. Returns the raw file content of the related file (non-Analytics files such as Excel or delimited data used as robot script input) rather than a JSON record. Required: id, org_id.
- **List all Diligent robot robot tasks** (List). List tasks for a robot in Diligent. Returns each task's id, type, and attributes including name, analytic_names, enabled, and created_at. Required: org_id, robot_id.
- **Create a Diligent robot robot task** (Create). Create a new task for a robot in Diligent; the robot runs it according to the configured settings, scheduled or ad hoc. Returns the created task's id, type, and attributes including name, analytic_names, enabled, and created_at. Required: org_id, robot_id, data.
- **List all Diligent robot jobs** (List). List robot task runs (individual executions of a robot task) in Diligent. Returns: id, type, attributes, relationships. Required: org_id, robot_id.
- **Delete a Diligent robots job by ID** (Delete). Delete a single robot task run (robot job) in Diligent. Returns an empty 204 response on success. Required: org_id, id.
- **Update a Diligent org robot task by ID** (Update). Update a robot task in Diligent by editing its existing settings; the new settings apply the next time a robot runs the task. Returns: id, type, attributes. Required: data, org_id, and id.
- **Delete a Diligent org robot task by ID** (Delete). Permanently delete a robot task from a robot in Diligent. Returns: id, type, attributes. Required: org_id, id. Previous task runs and output files are retained, and the task cannot be deleted while a run is queued or in progress.
- **Create a Diligent robot task run now** (Create). Run a robot task immediately in Diligent, creating a robot job. Returns the job's id, type, and attributes (status, queued_at, completed_at, result_analytics) with relationships to robot, task, and triggered_by. Required: org_id, robot_task_id.
- **List all Diligent robot task values** (List). List the values of a Diligent robot task, such as each value's analytic name and data type. Returns: id, type, attributes. Required: org_id, robot_task_id.
- **Diligent robot task values bulk update** (Update). Update the values of a Diligent robot task, such as changing a value's analytic name. Returns the updated values with id, type, and attributes (analytic_name, data, encrypted, parameter_id). Required: org_id, robot_task_id, data.
- **Get single Diligent robot task schedule by ID** (Get). Get a Diligent robot task's schedule to see when it runs, its time zone, and last run date. Returns: id, type, attributes. Required: id, org_id.
- **Create a Diligent robot task schedule** (Create). Create a schedule for a Diligent robot task so it runs on an automated basis. Returns: id, type, attributes. Required: data, org_id, robot_task_id
- **Diligent robot task schedules bulk update** (Update). Update a Diligent robot task's schedule to change when the task runs. Returns: id, type, attributes. Required: data, org_id, robot_task_id
- **Diligent robot task schedules bulk delete** (Delete). Delete a Diligent robot task's schedule; the task can still be run ad hoc afterwards. Returns the schedule in data (id, type, attributes). Required: robot_task_id, org_id
- **List all Diligent robots folder collaborators** (List). List the collaborators of a robots folder in Diligent. Returns each collaborator's id, type, and attributes (email, username, role, admin). Required: org_id, folder_id.
- **Update a Diligent robots folder collaborator by ID** (Update). Update a folder collaborator in Diligent, such as changing their role. Returns: id, type, attributes. Required: id, org_id, folder_id, data
- **Delete a Diligent robots folder collaborator by ID** (Delete). Delete a collaborator from a robots folder in Diligent, revoking their access to the folder's robots. Returns the deleted collaborator: id, type, attributes (email, username, role, admin). Required: id, org_id, folder_id.
- **Create a Diligent robots folder collaborator** (Create). Add a collaborator to a robots folder in Diligent, granting access to all robots in that folder. Returns: id, type, attributes. Required: org_id, folder_id, data
- **List all Diligent org robots folders** (List). List Robots Folders in Diligent used to organize Robots. Returns: id, type, attributes. Required: org_id.
- **Create a Diligent org robots folder** (Create). Create a Robots Folder in Diligent to organize Robots. Returns the created folder with id, type, and attributes. Required: org_id, data.
- **Get single Diligent org robots folder by ID** (Get). Get a single Robots Folder by id in Diligent. Returns: id, type, attributes. Required: org_id, id.
- **Update a Diligent org robots folder by ID** (Update). Update a Robots Folder by id in Diligent. Returns the updated folder with id, type, and attributes. Required: id, org_id, data.
- **Delete a Diligent org robots folder by ID** (Delete). Delete a Robots Folder by id in Diligent. Returns the deleted folder with id, type, and attributes. Required: org_id, id.
- **List all Diligent robots users** (List). List users of the Robots module in a Diligent organization. Returns a users array where each user includes id, uid, name, email, robots_role, and agent_manager, plus a next url for fetching the next page. Required: org_id.
- **Update a Diligent robots user by ID** (Update). Update a robot user in a Diligent organization by id. Returns: id, type, attributes. Required: id, org_id.
- **List all Diligent robots folder robots** (List). List the Robots in a Diligent Robots folder. Returns each robot's id, type, attributes, and relationships. Required: org_id and folder_id.
- **Create a Diligent org storyboard** (Create). Create a storyboard in Diligent One. Returns the created storyboard's id, type, and attributes (name, config, created_at, updated_at). At least one visualization or metric must already exist to include in the storyboard. Required: org_id, data.
- **Get single Diligent org storyboard by ID** (Get). Get a Diligent One storyboard by id. Returns the storyboard's id, type, and attributes. Required: org_id, id.
- **Update a Diligent org storyboard by ID** (Update). Update a Diligent One storyboard, such as renaming it or applying filters. Returns the updated storyboard's id, type, and attributes (name, config, created_at, updated_at). Required: id, org_id, data.
- **Delete a Diligent org storyboard by ID** (Delete). Permanently delete a storyboard in Diligent One Platform by id within an org. Returns an empty 204 response on success. Required: org_id, id. Once deleted, the storyboard cannot be recovered.
- ...and 344 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
