Huntr MCP connector
Connect Huntr to Claude, ChatGPT, Cursor 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.
-
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 Huntr to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Huntr once
-
Open Connections, choose Add connection, and pick Huntr.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Huntr API key. One person generates a token in Huntr 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.
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 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.
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.
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.
Use cases
What teams do with Huntr through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Huntr gets you
6 screens from the product, each doing one job for your Huntr account.
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.
- members
- jobs
- job posts
- activities
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 or Cursor
MCP clients
One endpoint puts Huntr in every client.
Claude, ChatGPT and Cursor reach Huntr through one governed org endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
32 Huntr tools, ready without writing code.
Members, advisors, jobs, job posts, activities and goals, covered the day you connect.
- List all Huntr organization invitations
- Create a Huntr organization invitation
- List all Huntr advisors
- List all Huntr members
Toolboxes
Every team gets its own Huntr toolbox.
Advisors, employer relations and program operations each work from a toolbox scoped to them.
- Career services
- Advisors
- Employer relations
- Program operations
Shared connections
Teammates use Huntr without touching the key.
One person connects Huntr, shares it with teams, and nobody else handles a credential.
- Career center
- Advising team
- Employer relations
- Program ops
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.
- 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 drafts the weekly cohort digest.
Activities are fetched, grouped by member, drafted, approved by an advisor, then posted back to Huntr.
Huntr digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Huntr
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 is never advertised to the AI client at all, so no prompt can reach it, and reading Huntr records still works as normal.
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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Huntr 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.