Homerun MCP server
Homerun in any MCP client, through Memtro: Homerun does not publish this server. Memtro's Homerun connector reads Homerun through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Homerun applicant tracking: vacancies with status, department, location, stages, salary range and candidate counts, each vacancy's application-form questions, candidates by vacancy, stage, hire date or disqualification (by id, stage and dates only, never their personal details or ratings), a candidate's non-sensitive notes and tags, and company tags; can add, move between stages or vacancies, and delete candidates, add, edit and delete notes, create, rename and delete tags, tag and untag candidates, submit application-form answers, and send a candidate the confirmation email.
Reads
homerun_list_vacanciesHomerun vacancies (jobs): id, title, status (public, private, draft, closed), employment type, department, location, hiring stages with their ids…homerun_get_vacancyOne Homerun vacancy with its stages, and optionally its application-form questions (id, type, whether mandatory or sensitive, and the question text)…homerun_list_candidatesHomerun candidates (job applications), by vacancy, stage, hired-after date or disqualification: id, vacancy, stage, when they applied…homerun_get_candidateOne Homerun candidate by id: vacancy, stage, dates, sources, Homerun link, tags, and notes that are not marked sensitive…homerun_list_notesA Homerun candidate's notes: author name, text (truncated) and dates.homerun_list_tagsThe company's Homerun tags: id and name.
Acts, when you ask
These change something in Homerun. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
homerun_create_candidateAdds a candidate to Homerun, on a vacancy (in its first stage) or, without a vacancy, to the talent pool.homerun_move_candidateMoves a Homerun candidate to another stage (by stage id or name, from the vacancy's stages) and/or onto another vacancy.homerun_delete_candidatePermanently deletes a Homerun candidate's application with its notes, files and answers.homerun_add_noteAdds a note to a Homerun candidate, visible to the hiring team (only to those allowed sensitive notes, when marked sensitive).homerun_update_noteReplaces the text of a note on a Homerun candidate, or changes whether it is sensitive.homerun_delete_notePermanently deletes a note from a Homerun candidate (recorded in the company's audit log).homerun_send_confirmation_emailEmails a Homerun candidate the "thanks for applying" confirmation, using the vacancy's template in its default language.homerun_create_tagCreates a company tag in Homerun, for labelling candidates.homerun_rename_tagRenames a Homerun tag; every candidate carrying it shows the new name.homerun_delete_tagPermanently deletes a Homerun tag from the company; it is also removed from every candidate who had it.homerun_tag_candidateAttaches an existing tag to a Homerun candidate (find or create the tag first); tags already on the candidate stay.homerun_untag_candidateRemoves a tag from a Homerun candidate; the tag itself stays.homerun_submit_answersSubmits a candidate's answers to the vacancy's application-form questions (ids from homerun_get_vacancy with include_questions)…
Connect it
First connect Homerun on Dashboard → Connections, then add Memtro to your client once. The Homerun tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Homerun connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › How many candidates are in interview for the designer role?
- › Which vacancies are public, and how many candidates does each have?
- › Who was hired for engineering roles since September?
- › What notes are on this candidate so far?
- › Move candidate 58213 to the Offer stage.
Questions
- Is this an official Homerun MCP server?
- No. It is Memtro's MCP server with Memtro's Homerun connector behind it: the connector reads Homerun through its API with the credentials you connect on Dashboard → Connections, and Homerun publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Homerun?
- Only when you ask, and only what it has been granted: add a candidate to a vacancy or the talent pool; move a candidate to another stage or vacancy; delete a candidate (permanent); add a note to a candidate; edit a candidate's note; delete a candidate's note (permanent); send a candidate the application confirmation email (once only); create a tag; rename a tag; delete a tag (removed from every candidate); tag a candidate; remove a tag from a candidate; submit answers to a vacancy's application-form questions for a candidate. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.