# 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. Source: https://elaichi.ai/connectors/flatchr/ ## Facts | | | | --- | --- | | Application | Flatchr | | Category | ATS | | AI tools | 28 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | 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 Flatchr is connected - 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. ## Connect Flatchr in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Flatchr. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Flatchr tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Flatchr 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. ## Flatchr MCP connector for Claude Code Endpoint: https://api.elaichi.ai/mcp 1. In a terminal, run `claude mcp add` with the endpoint. 2. Start Claude Code and run `/mcp`. 3. Pick elaichi, then sign in and approve in the browser. ```bash 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 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. ## Flatchr 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 Flatchr 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 Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a Flatchr tool needs "Run your connected tools". 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. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Flatchr through Elaichi ### See who is waiting in each stage Recruiting. Ask which applicants sit in each column of a Flatchr vacancy and who has been there longest, then decide where to spend the afternoon. ### Move a candidate after the interview Recruiting. Right after the debrief, move the applicant to the next column in Flatchr and create a task for the follow-up call. ### Catch up on a vacancy before the sync Hiring managers. List the active vacancies you own, see which channels they run on and read the latest comments and messages without opening Flatchr. ### Add a referral in a few words HR. Create the applicant against the right vacancy, tag them as a referral and leave a comment so the recruiter knows where they came from. ### Open a new vacancy from a brief Talent acquisition. Turn a hiring brief into a Flatchr vacancy with the right contract type and column setup, ready for the team to review. ### Keep the pipeline and task list clean People operations. List overdue tasks and update them, archive applicants who withdrew, and check recent activity so nothing sits forgotten in Flatchr. ## 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. Endpoint: 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](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 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 my team share one Flatchr connection? Yes. One person connects Flatchr with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the person who moved an applicant or created a task in Flatchr. ### 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. ## All 28 Flatchr tools Every tool below is callable through https://api.elaichi.ai/mcp once Flatchr is connected, subject to the toolbox it is in and the restrictions on the caller. - **Flatchr auth login** (Action). Login auth using the flatchr API. - **Create a Flatchr vacancy** (Create). Create vacancies using the flatchr API. - **List all Flatchr vacancies** (List). List vacancies using the flatchr API. - **Flatchr vacancies list active** (List). List active vacancies using the flatchr API. - **Get single Flatchr vacancy by ID** (Get). Get vacancies using the flatchr API. - **Flatchr applicants search** (Search). Search applicants using the flatchr API. - **Create a Flatchr applicant** (Create). Create applicants using the flatchr API. - **Flatchr applicants test** (Test). Test applicants using the flatchr API. - **Flatchr applicants archive** (Archive). Archive applicants using the flatchr API. - **Flatchr applicants move** (Move). Move applicants using the flatchr API. - **Flatchr applicants create custom** (Create). Create a candidate through the public careers-site multipart form. Supports vacancy, name, comment, and question answers. - **List all Flatchr comments** (List). List comments using the flatchr API. - **Delete a Flatchr comment by ID** (Delete). Delete comments using the flatchr API. - **List all Flatchr messages** (List). List messages using the flatchr API. - **Create a Flatchr task** (Create). Create tasks using the flatchr API. - **Update a Flatchr task by ID** (Update). Update tasks using the flatchr API. - **List all Flatchr tasks** (List). List tasks using the flatchr API. - **List all Flatchr tags** (List). List tags using the flatchr API. - **List all Flatchr candidate tags** (List). List candidate tags using the flatchr API. - **Create a Flatchr candidate tag** (Create). Create candidate tags using the flatchr API. - **List all Flatchr activities** (List). List activities using the flatchr API. - **List all Flatchr channels** (List). List channels using the flatchr API. - **List all Flatchr columns** (List). List columns using the flatchr API. - **List all Flatchr contract types** (List). List contract types using the flatchr API. - **List all Flatchr education levels** (List). List education levels using the flatchr API. - **List all Flatchr members** (List). List members using the flatchr API. - **List all Flatchr metiers** (List). List metiers using the flatchr API. - **Flatchr candidates add meta** (Add). Add metadata to a candidate profile. Requires the Premium CV Library option; candidate reference is an email address.