JOIN MCP connector
Connect JOIN once in Elaichi and Claude, ChatGPT, Cursor, or any MCP client can read and update JOIN jobs, applications, candidates, notes, and offices as the signed-in recruiter, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect JOIN to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect JOIN once
-
Open Connections, choose Add connection, and pick JOIN.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a JOIN API key. One person generates a token in JOIN and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
JOIN MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
JOIN MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect JOIN to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with JOIN through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting JOIN gets you
6 screens from the product, each doing one job for your JOIN account.
The agent
Ask about JOIN candidates in plain language.
Three starter prompts, answers pulled from live JOIN jobs, applications, and candidates.
- jobs
- applications
- candidates
- notes
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 or Cursor
MCP clients
One JOIN endpoint for Claude, ChatGPT, and Cursor.
Connect once over OAuth, no SDK and no shared API key handed around.
Copy the endpoint
Tool catalog
30 JOIN tools, no custom code to write.
Jobs, applications, candidates, notes, and offices, each with list, read, create, and update methods.
- List all JOIN jobs
- Get single JOIN job by ID
- Create a JOIN job
- Update a JOIN job by ID
Toolboxes
Every hiring team gets its own JOIN toolbox.
Recruiters, hiring managers, and HR each see only the JOIN tools scoped to them.
- Recruiting
- Hiring managers
- HR
- Talent acquisition
Shared connections
Share one JOIN connection, never the API key.
See who connected each JOIN account and which teams and members work through it.
- Recruiting DACH
- Engineering hiring
- Sales hiring
- HR
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.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
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 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
JOIN
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
JOIN
Queued
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.
JOIN health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 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 blocking deleting applications or notes, or blocking any updates at all. A restricted action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it.
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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.