Huntr MCP connector
Connect Huntr to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client through Elaichi, so career teams can ask about members, advisors, jobs, job posts, activities and goals, and send job posts to members, all inside each person's own Huntr access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which members in the spring cohort logged no activity this week?
Working in Huntr with Elaichi
-
List all Huntr organization invitations
-
List all Huntr advisors
-
List all Huntr members
How to connect Huntr to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Huntr 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.
Huntr 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.
Huntr 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.
Huntr 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.
Huntr 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 Huntr 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 Huntr through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Huntr is logged.
-
Career services
Find members who have gone quiet
Ask which members in a cohort have logged no applications, interviews or other activities this month, and get a list you can act on before the next check-in.
-
Advising
Prepare for a coaching session in minutes
Pull one member's goals, recent activities and the jobs on their board into a short brief, so the advisor walks in already knowing where the search stands.
-
Employer relations
Send a new job post to the right members
Turn a partner opening into a Huntr job post and send it to the member group it fits, without leaving the conversation you are already in.
-
Program operations
Invite a new cohort and set them up
Create organization invitations for an incoming cohort, add the member fields your program tracks, and tag members so they land in the right groups from day one.
-
Placement
Report placement progress by cohort
Ask how many members hit their weekly application goals, how many candidates reached interviews, and which cohorts are behind, summarized from live Huntr records.
-
Operations
Update member records in bulk
Correct a graduation date, program name or advisor assignment across dozens of members at once instead of opening each profile by hand.
Try asking
- “Which members in the spring cohort logged no activity this week?”
- “Send the new data analyst job post to the analytics group.”
- “Summarize Maria's goals and recent interviews before our session tomorrow.”
What connecting Huntr gets you
6 screens from Elaichi, each doing one job for your Huntr account.
Ask Elaichi to work across your apps.
Which members in the spring cohort logged no activity this week?
Send the new data analyst job post to the analytics group.
Summarize Maria's goals and recent interviews before our session tomorrow.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about members and get live Huntr answers.
Plain questions about members, activities and goals, answered from records as they stand right now.
Copy the endpoint
AI apps
One endpoint puts Huntr in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Huntr through one governed org endpoint, no SDK, no shared key.
Tool catalog
32 Huntr tools, ready without writing code.
Members, advisors, jobs, job posts, activities and goals, covered the day you connect.
Toolboxes
Every team gets its own Huntr toolbox.
Advisors, employer relations and program operations each work from a toolbox scoped to them.
Shared connections
Teammates use Huntr without touching the key.
One person connects Huntr, shares it with teams, and nobody else handles a credential.
Audit log
Every Huntr call is logged with a name.
When, who, what happened and which member or job post, kept in an append-only log.
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.
Huntr digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch members
Huntr
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
Huntr
Queued
Workflows
A schedule drafts the weekly cohort digest.
Activities are fetched, grouped by member, drafted, approved by an advisor, then posted back to Huntr.
Huntr health
Refreshed 4 minutes ago · every 15 minutes · from the members collection
Members
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Members created
Last 14 days
By team
Share of activity
Career center 34%
Advising team 27%
Employer relations 21%
Program ops 18%
Collections and dashboards
Huntr placement numbers, computed without a model.
Applications, interviews and goals met, charted over 14 days and split by team on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Huntr
All three can connect Huntr 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 Huntr tools | Allow or restrict single Huntr 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 Huntr 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.
Huntr tools for your AI agents
32 tools are ready to call through Elaichi's MCP endpoint the moment you connect Huntr, 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 Huntr to Claude?
In Elaichi, choose Huntr from the catalog and paste in your Huntr API key. 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 https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Huntr is ready to ask about.
Does Huntr work with ChatGPT and Cursor as well as Claude?
Yes. Once Huntr 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 Huntr once and every client you use sees it.
What can an AI agent actually do with my Huntr data?
It can look up members, advisors, member groups, candidates, jobs, job posts, activities, goals and tags in Huntr and answer questions about them, like which members have stalled or how a cohort is tracking against its goals. It can also create invitations, job posts, tags and member fields, send a job post to a group of members, and update member records in bulk. Short, concrete asks such as "list members with no activity this week" work better than long paragraphs.
Does connecting Huntr give the AI access to every member and advisor in my organization?
No. Every request runs as the person who signed in, so the AI sees only the members, groups and jobs that person can already see in Huntr. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Huntr itself allows.
Can I stop an agent from changing things in Huntr?
Yes. This connector can create invitations, job posts, tags and member fields and can update members in bulk, and each of those actions can be restricted separately in Elaichi. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Huntr connection when someone leaves?
Offboarding a person in Elaichi ends their access to Huntr through every client at once. A Huntr connection they shared keeps working for everyone else on the team. If you disconnect Huntr in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Huntr MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Huntr 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 Huntr?
Yes. Both let Claude, ChatGPT or Cursor use Huntr. 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 Huntr call.
How is Elaichi different from Composio for Huntr?
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 Huntr: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Huntr 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