Homerun ATS MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Homerun ATS MCP Serverlist all published vacancies"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Homerun ATS MCP Server
MCP server that connects AI agents to Homerun — an applicant tracking system. Enables AI-assisted candidate review: browse vacancies, inspect applications, and leave review notes.
Standalone server. No runtime dependency on the platform. Users add it like any remote MCP server.
Tools
Tool | Description |
| List job openings with optional status filter and pagination |
| Get full vacancy details (description, stages, location, department) |
| Search/filter applications by vacancy, stage, hired status, disqualification |
| Get full application details (candidate profile, notes, files, question answers) |
| Add a review note to an application |
Related MCP server: Recruitment AI MCP
Setup
Get a Homerun API key
Homerun App → Integrations → API Keys. Assign scopes:
vacancies:readjob-applications:readjob-application-notes:read(for notes in get_application)job-application-notes:write(for add_note)
API access requires the Homerun Plus plan.
Run locally
pnpm -F @softcery/mcp-homerun devStarts on http://localhost:8080. The MCP endpoint is /mcp.
Environment variables
Variable | Default | Description |
|
| Server port |
|
| Bind address |
|
| Session expiry (30 min) |
| — | Comma-separated allowed Host header values (DNS rebinding protection) |
Connect
From the platform
Admin UI → Agent → Integrations → Add Server:
URL:
https://<deployed-host>/mcpAPI Key: your Homerun API key
From Claude Desktop
{
"mcpServers": {
"homerun": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer <HOMERUN_API_KEY>"
}
}
}
}From any MCP client
Send an initialize request to POST /mcp with your Homerun API key as a Bearer token in the Authorization header. The server creates a stateful session — subsequent requests use the mcp-session-id header.
Auth model
No server-level auth. The Bearer token from the client's Authorization header is used directly as the Homerun API key. Each user's key has its own rate limit (60 req/min).
Development
pnpm -F @softcery/mcp-homerun test # run tests
pnpm -F @softcery/mcp-homerun lint # tsc + oxlint + knip
pnpm -F @softcery/mcp-homerun build # production buildDocker
docker build -f mcp-servers/homerun/Dockerfile -t mcp-homerun .
docker run -p 8080:8080 mcp-homerunThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/softcery/homerun-ats-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server