Flatchr MCP connector
The Flatchr connector brings vacancies, applicants, tasks and comments into Claude, ChatGPT, Cursor and the Elaichi Agent, so recruiters can ask about the pipeline, move candidates and create tasks while signed in as themselves.
-
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.
28 tools
How to connect
How to connect Flatchr to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Flatchr once
-
Open Connections, choose Add connection, and pick Flatchr.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Flatchr API key. One person generates a token in Flatchr 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.
Flatchr 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.
Flatchr MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
Flatchr 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.
Flatchr 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 Flatchr 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 Flatchr through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Recruiting
See who is waiting in each stage
Ask which applicants sit in each column of a Flatchr vacancy and who has been there longest, then decide where to spend the afternoon.
-
Recruiting
Move a candidate after the interview
Right after the debrief, move the applicant to the next column in Flatchr and create a task for the follow-up call.
-
Hiring managers
Catch up on a vacancy before the sync
List the active vacancies you own, see which channels they run on and read the latest comments and messages without opening Flatchr.
-
HR
Add a referral in a few words
Create the applicant against the right vacancy, tag them as a referral and leave a comment so the recruiter knows where they came from.
-
Talent acquisition
Open a new vacancy from a brief
Turn a hiring brief into a Flatchr vacancy with the right contract type and column setup, ready for the team to review.
-
People operations
Keep the pipeline and task list clean
List overdue tasks and update them, archive applicants who withdrew, and check recent activity so nothing sits forgotten in Flatchr.
Try asking
- “Which applicants for the Account Executive vacancy are still in screening?”
- “Move Marie Dupont to the interview column and add a follow-up task.”
- “List my open Flatchr tasks due this week.”
Compare
Elaichi vs Zapier MCP vs Composio for Flatchr
All three can connect Flatchr 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 Flatchr tools | Allow or restrict single Flatchr 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 Flatchr 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
Flatchr tools for your AI agents
28 tools are ready to call through Elaichi's MCP endpoint the moment you connect Flatchr, 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 Flatchr gets you
6 screens from the product, each doing one job for your Flatchr account.
The agent
Ask Flatchr who is waiting for feedback.
Three starter prompts, answered from live vacancies, applicants and tasks in Flatchr.
- vacancies
- applicants
- tasks
- comments
Ask Elaichi to work across your apps.
Which applicants for the Account Executive vacancy are still in screening?
Move Marie Dupont to the interview column and add a follow-up task.
List my open Flatchr tasks due this week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Flatchr in every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
28 Flatchr tools, no code to write.
Vacancies, applicants, tasks, comments, tags and channels, covered without a line of custom code.
- Flatchr auth login
- Create a Flatchr vacancy
- List all Flatchr vacancies
- Flatchr vacancies list active
ElaichiToolsToolboxes
Each team gets its own Flatchr toolbox.
Recruiting, hiring managers and HR each see the Flatchr tools their work needs.
- Recruiting
- Hiring managers
- HR
- Talent sourcing
ElaichiToolboxesShared connections
Share one Flatchr connection, keep the key private.
Teammates move applicants and create tasks without ever seeing the Flatchr API key.
- Recruiting
- HR France
- Engineering hiring
- Sales hiring
ElaichiConnectionsAudit log
Every Flatchr change names who made it.
When, who, what happened and which applicant or vacancy, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 drafts the weekly Flatchr digest.
New applicants are fetched, grouped by vacancy, drafted, approved by a person, then posted back.
Flatchr digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch vacancies
Flatchr
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
Flatchr
Queued
Collections and dashboards
Flatchr pipeline numbers, computed without a model.
Four metrics, 14 days of applicants created and a breakdown by team, refreshed on schedule.
Flatchr health
Refreshed 4 minutes ago · every 15 minutes · from the vacancies collection
Vacancies
1,284 ↓ 12%
Applicants
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Vacancies created
Last 14 days
By team
Share of activity
Recruiting 34%
HR France 27%
Engineering hiring 21%
Sales hiring 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Flatchr to Claude?
Connect Flatchr in Elaichi first, which means pasting your Flatchr API key, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Flatchr vacancies, applicants and tasks are available in your next conversation.
Does Flatchr work with ChatGPT and Cursor as well as Claude?
Yes. Once Flatchr is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Flatchr once and every client picks it up.
What can an AI agent actually do with my Flatchr data?
It can list your active Flatchr vacancies, search applicants, create a new applicant or vacancy, move a candidate to another column and archive those who dropped out. It can also read comments, messages and recent activity, create and update tasks, and add candidate tags. Short, concrete asks such as "move this applicant to interview" work better than long paragraphs.
Does connecting Flatchr give the AI access to every vacancy and applicant?
No. Every call runs inside the access of the person who signed in, so the AI sees the Flatchr vacancies and applicants that person can already see and nothing more. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Flatchr already allows.
Can I stop an agent from deleting or changing things in Flatchr?
Yes. Restrictions in Elaichi work per action, so you can allow reading Flatchr vacancies and applicants while blocking archiving, moving candidates or deleting comments. A restricted action is left out of the AI client's tool list entirely and cannot be called, whatever the prompt says.
What happens to a Flatchr connection when someone leaves?
Offboarding that person in Elaichi ends their access to Flatchr through every client at once. A shared Flatchr connection keeps working for everyone else on the team. If you want to remove Flatchr completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Flatchr MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Flatchr 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 Flatchr?
Yes. Both let Claude, ChatGPT or Cursor use Flatchr. 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 Flatchr call.
How is Elaichi different from Composio for Flatchr?
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 Flatchr: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Flatchr 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.