Skip to content

ATS

JOIN MCP connector

Connect JOIN once in Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can read and update JOIN jobs, applications, candidates, notes, and offices as the signed-in recruiter, with every action logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

List open JOIN jobs with the number of applications on each.

Working in JOIN with Elaichi

  • List all JOIN jobs
  • Get single JOIN job by ID
  • List all JOIN applications
Ask anything…
Governance / Audit log Last 24 hours
J List all JOIN applications Emily Carter · ChatGPT · 9:41 AM Done
J Get single JOIN job by ID Emily Carter · ChatGPT · 9:41 AM Done
J List all JOIN jobs Emily Carter · ChatGPT · 9:41 AM Done
J Create a JOIN job Megan Brooks · Claude · 9:38 AM Done
J Update a JOIN job by ID Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

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

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

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

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

JOIN 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 JOIN 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 JOIN through Elaichi

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

  • Recruiting

    Catch a candidate up after a screening call

    Pull up the candidate in JOIN, add a note with what you heard, and move their application to the next stage without leaving the conversation.

  • Hiring managers

    See every open job and who applied

    Ask for the open jobs in JOIN, then the applications on one role, and get a plain summary of where each applicant stands.

  • HR

    Draft a new job in JOIN from a brief

    Turn a short brief into a JOIN job, review the wording, and activate it when the hiring manager signs off.

  • Talent acquisition

    Archive filled roles in one pass

    Change the status of every job that was filled this month and archive them together, so the live list in JOIN only shows what is still open.

  • Recruiting operations

    Move a batch of applications at once

    After an interview day, update a whole set of JOIN applications in one go and attach reference numbers from your HR system to each.

  • People Ops

    Keep office locations accurate

    Add a new office in JOIN when a site opens and correct an address or name when something changes, so every job posts against the right location.

Try asking

  • “List open JOIN jobs with the number of applications on each.”
  • “Add a note to Maria Lopez's candidate record about today's screening call.”
  • “Archive every job in the Berlin office that was filled last month.”

See all 30 JOIN tools →

What connecting JOIN gets you

6 screens from Elaichi, each doing one job for your JOIN account.

Elaichi Agent

Ask Elaichi to work across your apps.

List open JOIN jobs with the number of applications on each.

Add a note to Maria Lopez's candidate record about today's screening call.

Archive every job in the Berlin office that was filled last month.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about JOIN candidates in plain language.

Three starter prompts, answers pulled from live JOIN jobs, applications, and candidates.

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 JOIN endpoint for Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot.

Connect once over OAuth, no SDK and no shared API key handed around.

ElaichiTools
Tool Action Description
List all JOIN jobs List List jobs in Join. The connector sends status=ONLINE,OFFLINE,ARCHIVED and content=true by default (every job, with its full content); pass status or content to override (JOIN's own defaults are ONLINE and false). Returns each job's id, createdAt, lastUpdatedAt, title, status, externalId, and office.
Get single JOIN job by ID Get Get a single job in Join by id. Returns the job including id, createdAt, lastUpdatedAt, title, status, externalId, office, workplaceType, and screening questions. JOIN's reference says description, salary, contact, contactPerson, attachments, employmentTypeId, categoryId, seniorityId, language, and followers are returned only when content=true, yet documents no content parameter for this endpoint, so they may be absent. Required: id.
Create a JOIN job Create Create a job in Join; new jobs are automatically set active and multiposted to job boards. Returns: id. Required: title, description, categoryId, language, employmentTypeId, officeId.
Update a JOIN job by ID Update Update a job in Join by id; all body fields are optional. Returns: id. Required: id.
JOIN jobs bulk change status Action Change the status of a job in Join to ONLINE, OFFLINE, or ARCHIVED. Returns: id. Required: job_id, status.

Tool catalog

30 JOIN tools, no custom code to write.

Jobs, applications, candidates, notes, and offices, each with list, read, create, and update methods.

ElaichiToolboxes
Name Source template Tools Created

Recruiting toolbox

JOIN · jobs and applications

JOIN starter 18 Mar 4, 2026

Hiring managers toolbox

JOIN · applications on their open roles

— 9 Mar 2, 2026

HR toolbox

JOIN · candidates and notes

— 24 Feb 27, 2026

Talent acquisition toolbox

JOIN · candidate pipelines and sourcing

JOIN starter 6 Feb 19, 2026

Recruiting operations toolbox

JOIN · bulk status changes and external references

— 31 Jan 30, 2026

People Ops toolbox

JOIN · offices and job setup

— 12 Jan 22, 2026

Toolboxes

Every hiring team gets its own JOIN toolbox.

Recruiters, hiring managers, and HR each see only the JOIN tools scoped to them.

ElaichiConnections
Connection Scope Status Access
JO

JOIN (Recruiting DACH)

Connected by Emily Carter

Personal • Active 1 team · 6 members
JO

JOIN (Engineering hiring)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
JO

JOIN (Sales hiring)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
JO

JOIN (HR)

Connected by Tyler Reed

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

JOIN (Berlin office)

Connected by Ryan Hayes

Personal • Active Not shared
JO

JOIN (Talent acquisition)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one JOIN connection, never the API key.

See who connected each JOIN account and which teams and members work through it.

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]

JOIN Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

JOIN Jobs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

JOIN Jobs List Toolbox

Audit log

Know who changed which JOIN application, and when.

An append-only log of when, who, what happened, type, and resource for every JOIN call.

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.

JOIN digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch jobs

    JOIN

    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

    JOIN

    Queued

Workflows

A schedule starts the JOIN digest, you approve.

New JOIN applications are fetched, grouped by job, drafted into a digest, approved, then posted back.

JOIN health

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

Live

Jobs

1,284 ↓ 12%

Applications

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Jobs created

Last 14 days

By team

Share of activity

Recruiting DACH 34%

Engineering hiring 27%

Sales hiring 21%

HR 18%

Collections and dashboards

JOIN hiring numbers, computed, with no model involved.

Four metrics, 14 days of applications created, and a breakdown by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for JOIN

All three can connect JOIN 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 JOIN, 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 JOIN tools Allow or restrict single JOIN 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 JOIN 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.

JOIN tools for your AI agents

30 tools are ready to call through Elaichi's MCP endpoint the moment you connect JOIN, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect JOIN to Claude?

First connect JOIN in Elaichi by pasting the API key from your JOIN account; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and JOIN jobs, candidates, and applications are available in Claude.

Does JOIN work with ChatGPT and Cursor as well as Claude?

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

What can an AI agent actually do with my JOIN data?

With JOIN connected, an agent can list open jobs, look up a candidate, read the applications on a role, add or update notes, change application stages, create and activate jobs, archive filled ones, and keep office locations current. Short, concrete asks work best, such as "show me the applications on the Berlin sales job" rather than a long paragraph.

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

No. Every call to JOIN runs inside the access of the person who signed in, so the agent sees the jobs, candidates, and applications that person can already see in JOIN. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

Can my team share one JOIN connection?

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

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading JOIN jobs and candidates while restricting deleting applications or notes, or restricting any updates at all. 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 JOIN connection when someone leaves?

Offboarding a person in Elaichi ends their access to JOIN at once, in every client they used. A shared JOIN connection keeps working for everyone else on the team. If you want JOIN gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.

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

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

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

How is Elaichi different from Composio for JOIN?

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

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