Skip to content

ATS

Gem MCP connector

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

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which candidates in the Backend Engineer project haven't replied to outreach?

Working in Gem with Elaichi

  • Looked in Gem
Ask anything…
Governance / Audit log Last 24 hours
Gem Looked in Gem Emily Carter · Claude · 9:41 AM Done
Gem Looked in Gem Megan Brooks · ChatGPT · 9:38 AM Done
Gem Looked in Gem Ryan Hayes · Cursor · 9:35 AM Done

How to connect Gem to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Gem MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Gem MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Gem MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Gem MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Gem to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Gem through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Gem is logged.

  • Recruiting

    Catch up on a candidate before the call

    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.

  • Sourcing

    See which sequences are getting replies

    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.

  • Hiring managers

    Check the pipeline for your open role

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

  • Talent operations

    Spot stalled candidates across every project

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

  • Coordinators

    Leave a note after the debrief

    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.

  • Leadership

    Get a weekly hiring summary in plain words

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

Try asking

  • “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.”

What connecting Gem gets you

5 screens from Elaichi, each doing one job for your Gem account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Gem questions in plain language.

Get answers from live candidates, projects and pipelines in Gem, no report to build.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One governed endpoint for Claude, ChatGPT, Cursor and Microsoft Copilot.

Every client reaches Gem through one org endpoint, no SDK and no shared API key.

ElaichiToolboxes
Name Source template Tools Created

Recruiting toolbox

Gem · candidates and pipelines

Gem starter 18 Mar 4, 2026

Sourcing toolbox

Gem · projects and outreach sequences

— 9 Mar 2, 2026

Hiring managers toolbox

Gem · open jobs and pipeline stages

— 24 Feb 27, 2026

Talent operations toolbox

Gem · stage hygiene and reporting

Gem starter 6 Feb 19, 2026

Coordinators toolbox

Gem · candidate notes and next steps

— 31 Jan 30, 2026

Leadership toolbox

Gem · open jobs and offers out

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Gem toolbox.

Sourcing, recruiting and hiring managers each work from a toolbox scoped to their role.

ElaichiConnections
Connection Scope Status Access
GE

Gem (Engineering recruiting)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GE

Gem (GTM recruiting)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GE

Gem (Sourcing EMEA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GE

Gem (Sourcing US)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GE

Gem (Executive search)

Connected by Ryan Hayes

Personal • Active Not shared
GE

Gem (University hiring)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Gem connection, never a credential.

Teammates work through the account you connected and never see a password or token.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Gem Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Gem Candidates Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Gem Candidates List Toolbox

Audit log

Every Gem call is logged with a name.

See who looked up which candidate, when, and what changed, in one append-only log.

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.

Gem digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch candidates

    Gem

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Gem

    Queued

Workflows

A schedule starts the work, a person approves.

Candidates from Gem are fetched, grouped, drafted into a digest, approved, then posted back.

Gem health

Refreshed 4 minutes ago · every 15 minutes · from the candidates collection

Live

Candidates

1,284 ↓ 12%

Jobs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Candidates created

Last 14 days

By team

Share of activity

Engineering recruiting 34%

GTM recruiting 27%

Sourcing EMEA 21%

Sourcing US 18%

Collections and dashboards

Gem pipeline health, computed without a model.

Four metrics, fourteen days of candidates created and a split by team, refreshed on schedule.

Why connect Gem's MCP server through Elaichi

Gem builds and runs this MCP server. Elaichi sits in front of it, so Gem's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Gem's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Gem's tools at the same Elaichi address as every other connected app. Nobody adds Gem's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Gem sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Gem's server. By default, a tool Gem does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Gem

    Gem builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Gem team.

    [email protected]

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Gem, by what to check
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 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 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.

Questions, answered

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, Microsoft Copilot 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 restricting adding notes or any other change. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, 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 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.

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