# Gem MCP connector

Connect Gem to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can look up candidates, jobs, projects, pipelines and outreach in Gem as the signed-in person, with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Gem |
| Category | ATS |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Gem builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@gem.com |
| 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 Gem is connected

- Which candidates in the Backend Engineer project haven't replied to outreach?
- Who has been at onsite stage longer than two weeks?
- Add a note to Priya Shah: strong debrief, moving to offer.

## Connect Gem in Elaichi

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

1. Open Connections, choose Add connection, and pick Gem.
2. Optionally set Share with, then press Connect.
3. Approve it in Gem. Gem's own window opens. Whoever approves it decides what this connection can reach.

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

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

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

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

Only Read is granted by default, which is not enough to call a Gem tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Gem through Elaichi

### Catch up on a candidate before the call

Recruiting. Ask where a candidate sits in the pipeline, which project they came from and what the last outreach said. After the conversation, have a note added to their record in Gem.

### See which sequences are getting replies

Sourcing. Ask which outreach sequences in Gem are getting replies this week and which projects are running dry, so you know where to spend the afternoon.

### Check the pipeline for your open role

Hiring managers. Ask how many candidates are at each stage for your job and who has been waiting longest, without opening Gem yourself.

### Spot stalled candidates across every project

Talent operations. Ask for candidates who have not moved stage in two weeks, grouped by recruiter, and send the list to the people who own them.

### Leave a note after the debrief

Coordinators. Once the interview panel has decided, ask the agent to add a note to the candidate in Gem with the decision and the next step.

### Get a weekly hiring summary in plain words

Leadership. Ask for open jobs, pipeline counts by stage and offers out across Gem, written up and ready to paste into the Monday update.

## Elaichi vs Zapier MCP vs Composio for Gem

All three can connect Gem 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 Gem tools | Allow or restrict single Gem 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 Gem 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 Gem to Claude?

Open Gem in the Elaichi catalog, choose Connect and sign in to Gem in the window that opens. Gem asks you to approve the access, and that is the whole step: there is 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 to Elaichi when Claude asks and Gem is available in your next conversation.

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

Yes. Gem is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor or any other MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up per client.

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

Once Gem is connected, you can ask about candidates, jobs, projects, pipeline stages, sourcing and outreach sequences in plain language and get answers from what is in Gem right now. Some changes are supported as well, such as adding a note to a candidate. Short, concrete asks work best: name the candidate, the job or the project rather than describing them in a long sentence.

### Does connecting Gem give the AI everything in my Gem account?

No. Every request to Gem runs as the person who signed in, so the agent sees only the candidates, projects and jobs that person can already see in Gem. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Gem itself allows that person.

### Can my recruiting team share one Gem connection?

Yes. One person connects Gem in Elaichi and shares the connection with a team, and nobody else ever handles a password or token. Each teammate still signs in to Elaichi as themselves, so the audit log names the individual who looked up a candidate or added a note in Gem.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading candidates and pipelines in Gem while blocking adding notes or any other change. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.

### What happens to a Gem connection when a recruiter leaves?

Offboarding that person in Elaichi ends their access to Gem through every client at once. A Gem connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Gem once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

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

Yes. Gem 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 Gem?

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

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

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