Manatal MCP connector
The Manatal connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent add notes, resumes and attachments to Manatal candidates and read a candidate's note history, with every action tied to the recruiter who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the notes on this week's shortlisted candidates.
Working in Manatal with Elaichi
-
List all Manatal candidate notes
-
Create a Manatal candidate attachment
-
Create a Manatal candidate note
How to connect Manatal to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Manatal 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.
Manatal 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.
Manatal 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. The plugin directory lives at chatgpt.com/plugins.
Manatal 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.
Manatal MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 Manatal 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.
What teams do with Manatal through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Manatal is logged.
-
Recruiting
Write up a screening call in Manatal
After a phone screen, dictate what you learned and have it saved as a note on the candidate's Manatal record while the details are still fresh.
-
Recruiting
Read a candidate's history before an interview
Ask for every note left on a candidate in Manatal and get a short summary of what previous interviewers said, so you walk in prepared.
-
Talent acquisition
Attach an updated resume to a candidate
When a candidate sends a newer resume, have it added to their Manatal profile without leaving the conversation you are already in.
-
Hiring managers
Leave interview feedback where recruiters see it
Hiring managers can drop their feedback as a note on the Manatal candidate instead of emailing it, so the whole panel reads the same record.
-
HR
File reference checks and signed documents
Attach reference check summaries, signed offer letters or work samples to the candidate's Manatal record so everything about the hire sits in one place.
-
Agency recruiters
Tidy duplicate or outdated candidate notes
Spot notes that were added twice or no longer apply and remove them from Manatal, keeping the candidate's history clear for the next consultant.
Try asking
- “Summarize the notes on this week's shortlisted candidates.”
- “Add an interview note to the backend engineer candidate.”
- “List all notes on candidates for the sales role.”
What connecting Manatal gets you
6 screens from Elaichi, each doing one job for your Manatal account.
Ask Elaichi to work across your apps.
Summarize the notes on this week's shortlisted candidates.
Add an interview note to the backend engineer candidate.
List all notes on candidates for the sales role.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about candidates, get answers back.
Type a question in plain language and read it off live Manatal records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Connect any MCP client to Manatal over OAuth, no SDK, no shared key.
Tool catalog
5 Manatal tools ready with no code.
Browse candidate notes, attachments and resumes with every resource and method listed.
Toolboxes
Every team gets its own toolbox.
Scope a Manatal toolbox to recruiting, sourcing or hiring managers separately.
Shared connections
Teammates work without seeing a credential.
See who connected each Manatal account and how many teams and members use it.
Audit log
Every candidate note leaves a record.
When, who, what happened, type and resource for each Manatal 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. Automations, collections and live dashboards come with the Black plan.
Manatal digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch candidates
Manatal
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 Jake Morgan
Approve Deny -
Post the digest
Manatal
Queued
Automations
A schedule fires, a digest ships.
Fetch Manatal candidate notes, group them, draft a digest, approve, post back.
Manatal health
Refreshed 4 minutes ago · every 15 minutes · from the candidates collection
Candidates
1,284 ↓ 12%
Notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Candidates created
Last 14 days
By team
Share of activity
Recruiting EMEA 34%
Sourcing 27%
Hiring managers 21%
Talent ops 18%
Collections and dashboards
Candidate numbers computed, not asked for.
Four metrics, 14 days of candidates created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Manatal
All three can connect Manatal 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 Manatal tools | Allow or restrict single Manatal 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 Manatal 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.
Manatal tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Manatal, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Manatal to Claude?
First, connect Manatal in Elaichi by pasting your Manatal API key, which you copy from your Manatal account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Manatal is ready to use in Claude.
Does Manatal work with ChatGPT and Cursor as well as Claude?
Yes. Once Manatal is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Manatal once and every client you use picks it up.
What can an AI agent actually do with my Manatal data?
Through this connector an AI agent can add a note to a Manatal candidate, read back all the notes on a candidate and summarize them, remove a note, and attach a resume or another file such as a portfolio or signed offer letter to the candidate's record. It works at the level of individual candidates you already have in Manatal. It cannot search for candidates, edit jobs or change pipeline stages through this connector.
Does connecting Manatal give the AI access to every candidate?
No. Every call to Manatal runs inside the access of the person who signed in, so the AI can only reach candidates that person can already reach in Manatal. Elaichi can narrow that access further, for example by restricting note deletion for a role, but it can never widen it beyond what the person already has.
Can I stop an agent from deleting or changing things in Manatal?
Yes. Restrictions in Elaichi apply per action, so you can allow adding notes and resumes to Manatal candidates while restricting note deletion entirely. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Manatal connection when someone leaves?
When you offboard someone in Elaichi, their access to Manatal through the endpoint ends at once. A shared Manatal connection keeps working for everyone else on the team. If you ever want to remove Manatal completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Manatal MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Manatal 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 Manatal?
Yes. Both let Claude, ChatGPT or Cursor use Manatal. 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 Manatal call.
How is Elaichi different from Composio for Manatal?
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 Manatal: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Manatal 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