# Dvinci MCP connector

The Dvinci connector brings applications, attachments, hiring requests and application history into Claude, ChatGPT, Cursor and the Elaichi Agent, so recruiters can ask about candidates and move them forward inside their own Dvinci access.

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

## Facts

| | |
| --- | --- |
| Application | Dvinci |
| Category | ATS |
| AI tools | 75 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, 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 Dvinci is connected

- Which applications for the backend engineer opening are still waiting on feedback?
- Move Anna Keller's application to interview and note the call summary.
- Create a hiring request for a support agent in Hamburg starting May.

## Connect Dvinci in Elaichi

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

1. Open Connections, choose Add connection, and pick Dvinci.
2. Optionally set Share with, then press Connect.
3. Paste a Dvinci API key. One person generates a token in Dvinci 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 Dvinci tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

## Dvinci 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 today. The plugin directory lives at chatgpt.com/plugins.

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

## Connect Dvinci 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 data and remove access", which you tick yourself. Calling a Dvinci tool needs "Run your connected tools". 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 Delete, which reaches into connected apps and cannot be undone.

## What teams do with Dvinci through Elaichi

### Catch an application up after a screening call

Recruiting. Tell the agent what came out of the call and it updates the application in Dvinci and adds a history entry, so the next person to open it sees the full story.

### Move candidates to the next stage in bulk

Recruiting. Ask for everyone in a job opening still at phone screen, then change their status or move them to another job opening without clicking through each one.

### See where every applicant for my role stands

Hiring managers. Ask which applications are open for your job opening, how long each has been waiting, and what the last history entry says.

### Raise a hiring request without the form

HR. Describe the role, team and start date, and the agent creates the hiring request in Dvinci. Later, ask for its history to see where approval sits.

### Pull the CV before the interview

Talent acquisition. Ask for the attachments on an application and get the PDF, so the interviewer walks in prepared.

### Reconcile applications with the HR system

Operations. Look up applications and hiring requests by their external ID to match them against records in payroll or the HRIS, and fix mismatches in place.

## Elaichi vs Zapier MCP vs Composio for Dvinci

All three can connect Dvinci 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 Dvinci tools | Allow or restrict single Dvinci 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 Dvinci 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 | $15 per user per month. | 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 Dvinci to Claude?

Two steps. In Elaichi, add Dvinci and paste in your Dvinci API key; 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 Dvinci is ready to use.

### Does Dvinci work with ChatGPT and Cursor as well as Claude?

Yes. Dvinci is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You do not set Dvinci up again for each client.

### What can an AI agent actually do with my Dvinci data?

It can find, create and update applications in Dvinci, change their status, move them between job openings and add a history entry after a call. It can fetch attachments, including the PDF of a CV, and create and update hiring requests. Short, concrete asks such as 'move Anna to interview' work better than long paragraphs.

### Does connecting Dvinci give the AI access to everything in my account?

No. The AI works through the Dvinci account whose API key was connected, so it can only see and change what that account can, and each person still signs in to Elaichi as themselves. Elaichi can narrow that access further, by team and by action, but it never widens it beyond what Dvinci itself allows.

### Can my team share one Dvinci connection?

Yes. One person connects Dvinci with the API key and shares the connection with a team in Elaichi. Teammates use Dvinci from their own AI client without ever seeing the key, and because each of them signs in to Elaichi as themselves, the audit log names who did what.

### Can I stop an agent from deleting or changing things in Dvinci?

Yes. Restrictions on the Dvinci connection in Elaichi apply per action, so you can switch off deleting applications or attachments while leaving reading and updating on. A restricted action is left out of the tool list the AI client sees, so it cannot be called no matter how the prompt is worded.

### What happens to a Dvinci connection when someone leaves?

Offboarding someone in Elaichi ends their access to Dvinci at once, and a shared Dvinci connection keeps working for everyone else on the team. If you later want to remove Dvinci entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Dvinci MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Dvinci 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, 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 Dvinci?

Yes. Both let Claude, ChatGPT or Cursor use Dvinci. 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 Dvinci call.

### How is Elaichi different from Composio for Dvinci?

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 Dvinci: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 75 Dvinci tools

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

- **List all Dvinci applications** (List). List applications using the dvinci API.
- **Create a Dvinci application** (Create). Create applications using the dvinci API.
- **Get single Dvinci application by ID** (Get). Get applications using the dvinci API.
- **Update a Dvinci application by ID** (Update). Update applications using the dvinci API.
- **Delete a Dvinci application by ID** (Delete). Delete applications using the dvinci API.
- **Dvinci applications change status** (Action). Change status applications using the dvinci API.
- **Dvinci applications move job opening** (Move). Move job opening applications using the dvinci API.
- **Dvinci applications get by external ID** (Get). Get applications by external ID.
- **List all Dvinci application attachments** (List). List application attachments using the dvinci API.
- **Create a Dvinci application attachment** (Create). Create application attachments using the dvinci API.
- **Get single Dvinci application attachment by ID** (Get). Get application attachments using the dvinci API.
- **Dvinci application attachments get PDF** (Get). Get pdf application attachments using the dvinci API.
- **Delete a Dvinci application attachment by ID** (Delete). Delete application attachments using the dvinci API.
- **List all Dvinci application history** (List). List application history using the dvinci API.
- **Dvinci application history upsert** (Upsert). Upsert application history using the dvinci API.
- **Dvinci application history upsert entry** (Upsert). Upsert entry application history using the dvinci API.
- **List all Dvinci configuration external links** (List). List configuration external links using the dvinci API.
- **Dvinci configuration external links upsert** (Upsert). Upsert configuration external links using the dvinci API.
- **List all Dvinci hiring requests** (List). List hiring requests using the dvinci API.
- **Create a Dvinci hiring request** (Create). Create hiring requests using the dvinci API.
- **Get single Dvinci hiring request by ID** (Get). Get hiring requests using the dvinci API.
- **Update a Dvinci hiring request by ID** (Update). Update hiring requests using the dvinci API.
- **Dvinci hiring requests get by external ID** (Get). Get hiring requests by external ID.
- **List all Dvinci hiring request history** (List). List hiring request history using the dvinci API.
- **List all Dvinci hiring request approvers** (List). List hiring request approvers using the dvinci API.
- **List all Dvinci job openings** (List). List job openings using the dvinci API.
- **Create a Dvinci job opening** (Create). Create job openings using the dvinci API.
- **Get single Dvinci job opening by ID** (Get). Get job openings using the dvinci API.
- **Update a Dvinci job opening by ID** (Update). Update job openings using the dvinci API.
- **Delete a Dvinci job opening by ID** (Delete). Delete job openings using the dvinci API.
- **Dvinci job openings get by external ID** (Get). Get job openings by external ID.
- **List all Dvinci job opening history** (List). List job opening history using the dvinci API.
- **Dvinci job opening history upsert** (Upsert). Upsert job opening history using the dvinci API.
- **Dvinci job opening history upsert entry** (Upsert). Upsert entry job opening history using the dvinci API.
- **List all Dvinci job publications** (List). List job publications using the dvinci API.
- **Create a Dvinci job publication** (Create). Create job publications using the dvinci API.
- **Get single Dvinci job publication by ID** (Get). Get job publications using the dvinci API.
- **Update a Dvinci job publication by ID** (Update). Update job publications using the dvinci API.
- **Delete a Dvinci job publication by ID** (Delete). Delete job publications using the dvinci API.
- **Dvinci job publications delete deprecated** (Delete). Delete job publications through the vendor's deprecated POST route.
- **Dvinci job publications get by external ID** (Get). Get job publications by external ID.
- **List all Dvinci locations** (List). List locations using the dvinci API.
- **Create a Dvinci location** (Create). Create locations using the dvinci API.
- **Get single Dvinci location by ID** (Get). Get locations using the dvinci API.
- **Update a Dvinci location by ID** (Update). Update locations using the dvinci API.
- **Delete a Dvinci location by ID** (Delete). Delete locations using the dvinci API.
- **List all Dvinci onboardings** (List). List onboardings using the dvinci API.
- **Get single Dvinci onboarding by ID** (Get). Get onboardings using the dvinci API.
- **Delete a Dvinci onboarding by ID** (Delete). Delete onboardings using the dvinci API.
- **List all Dvinci onboarding attachments** (List). List onboarding attachments using the dvinci API.
- ...and 25 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.