[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Homerun MCP tools

> The Homerun MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/homerun

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Homerun has 14 operations on the Cotlet MCP server, in homerun_read and homerun_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `homerun_read`, `homerun_write`
- Connects with: Your own Homerun account. What your agent can do follows your permissions in Homerun, and a key from an admin is not needed.
- Integration page: https://cotlet.dev/integrations/homerun-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_jobs`](https://cotlet.dev/docs/mcp/homerun/list_jobs.md) | List your jobs with their state and visibility. |
| [`get_job`](https://cotlet.dev/docs/mcp/homerun/get_job.md) | Read one job: its hiring stages, closing date and application form questions. |
| [`list_candidates`](https://cotlet.dev/docs/mcp/homerun/list_candidates.md) | List the candidates of one job, filtered by stage, tag or status. |
| [`get_candidate`](https://cotlet.dev/docs/mcp/homerun/get_candidate.md) | Read a candidate profile with answers, ratings, notes and messages. |
| [`list_tags`](https://cotlet.dev/docs/mcp/homerun/list_tags.md) | List the tags your company uses on candidates. |
| [`list_disqualification_reasons`](https://cotlet.dev/docs/mcp/homerun/list_disqualification_reasons.md) | List the reasons you can give when disqualifying a candidate. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`add_candidate_note`](https://cotlet.dev/docs/mcp/homerun/add_candidate_note.md) | Add an internal note to a candidate profile. |
| [`add_candidate_tag`](https://cotlet.dev/docs/mcp/homerun/add_candidate_tag.md) | Add a tag to a candidate, creating the tag if it does not exist. |
| [`remove_candidate_tag`](https://cotlet.dev/docs/mcp/homerun/remove_candidate_tag.md) | Remove a tag from a candidate. |
| [`move_candidate_to_stage`](https://cotlet.dev/docs/mcp/homerun/move_candidate_to_stage.md) (Confirm) | Move a candidate to another hiring stage of the same job. |
| [`move_candidate_to_job`](https://cotlet.dev/docs/mcp/homerun/move_candidate_to_job.md) (Confirm) | Move a candidate to another job. |
| [`disqualify_candidate`](https://cotlet.dev/docs/mcp/homerun/disqualify_candidate.md) (Confirm) | Disqualify a candidate with a reason and choose whether to tell them. |
| [`send_candidate_email`](https://cotlet.dev/docs/mcp/homerun/send_candidate_email.md) (Confirm) | Send an email to one candidate through Homerun. |
| [`set_job_visibility`](https://cotlet.dev/docs/mcp/homerun/set_job_visibility.md) (Confirm) | Make an active job public, private or closed. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.