[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 API and MCP server

> Homerun has a documented Public API, version 2, but no official MCP server (checked 22 Oct 2026). It is for paid plans, trials get no key, and an admin creates the key. It reads jobs and manages candidates, but it cannot create, edit, publish or close a job.

Applicant tracking system for small teams: job posts and a career page, an application form, candidates moving through hiring stages, reviews, emails and interview events in one place.

## What is the Homerun API?

Cotlet's Homerun API exposes 14 endpoints for your own Homerun account: list jobs, get a job, list candidates, get a candidate, list tags, list disqualification reasons, add a note to a candidate, tag a candidate, remove a tag from a candidate, move a candidate to a stage, move a candidate to another job, disqualify a candidate, email a candidate and set job visibility. The list_jobs endpoint returns list your jobs with their state and visibility. Each endpoint takes simple JSON inputs like job_id, candidate_id or tag and works both as an operation of the homerun_read or homerun_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 14 (6 read, 8 write)
- **Updated:** 2026-10-20

Homerun has a documented Public API, version 2, but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Homerun with 14 endpoints (6 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Homerun have an official API?

Homerun has a documented Public API, version 2, but no official MCP server (checked 22 Oct 2026). It is for paid plans, trials get no key, and an admin creates the key. It reads jobs and manages candidates, but it cannot create, edit, publish or close a job.

| Task | Homerun official | Cotlet |
|---|---|---|
| List jobs and read a job with its application questions | Yes: Public API, read scope; 60 requests a minute | Yes |
| List candidates with their answers and source | Yes: Public API; a candidate exists only as an application to a job | Yes |
| Move a candidate to another stage or job | Yes: Public API, update the application | Yes |
| Add notes and tags to a candidate | Yes: Public API, separate scopes for notes and tags | Yes |
| Disqualify a candidate with a reason | Partly: The API returns the reason; the docs list no action to set it | Yes |
| Email a candidate | Partly: Only the application confirmation email, once per application | Yes |
| Close a job or change its visibility | No | Yes |

Sources: [Homerun Public API documentation](https://developers.homerun.co/), [Homerun Help: What can you do with the Homerun Public API?](https://help.homerun.co/en/articles/16761415-what-can-you-do-with-the-homerun-public-api), [Homerun Help: How to generate our public API key](https://help.homerun.co/en/articles/2240793-how-to-generate-our-public-api-key), [Homerun pricing](https://www.homerun.co/pricing)

## For AI agents

```text
Homerun has a documented Public API, version 2, but no official MCP server (checked 22 Oct 2026). It is for paid plans, trials get no key, and an admin creates the key. It reads jobs and manages candidates, but it cannot create, edit, publish or close a job.
Cotlet provides a hosted MCP server and REST API for Homerun: 14 tools (6 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=homerun, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    homerun_read, homerun_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/homerun, each operation at its own route, e.g. POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/to-stage/move
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_jobs, get_job, list_candidates, get_candidate, list_tags, list_disqualification_reasons, add_candidate_note, add_candidate_tag, remove_candidate_tag, move_candidate_to_stage, move_candidate_to_job, disqualify_candidate, send_candidate_email, set_job_visibility
Confirm      move_candidate_to_stage, move_candidate_to_job, disqualify_candidate, send_candidate_email, set_job_visibility (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/homerun-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=homerun, requests Homerun in the Cotlet console and creates an API key there.
2. The user signs in to Homerun once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Homerun for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Homerun server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Homerun MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Homerun in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Homerun only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Homerun login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Homerun's terms; Cotlet is not affiliated with Homerun.
```

## What can an AI agent do in Homerun?

Cotlet is best for recruiters and small hiring teams on Homerun who want their AI agent to screen, reply to and sort candidates and close jobs without running or fixing a server.

- **[Disqualify unqualified candidates in bulk](https://cotlet.dev/integrations/homerun-api-mcp-server/disqualify-candidates-in-bulk.md)** (runs: daily): "Go through the candidates in the Application stage of Customer Success Manager. Disqualify the ones whose answers show no relevant experience, without emailing them, and leave every unclear one for me with a one-line reason." → `list_candidates`, `get_candidate`, `list_disqualification_reasons`, `disqualify_candidate`
- **[Reply to new applicants on time](https://cotlet.dev/integrations/homerun-api-mcp-server/reply-to-new-applicants.md)** (runs: daily): "Find candidates in Customer Success Manager whose first reply is overdue. Send each a short personal reply that mentions one thing from their application and says when we decide. Skip anyone I already wrote to." → `list_candidates`, `get_candidate`, `send_candidate_email`, `add_candidate_note`
- **[Close jobs that have enough applicants](https://cotlet.dev/integrations/homerun-api-mcp-server/close-jobs-with-enough-applicants.md)** (runs: daily): "Check my active public jobs in Homerun. Close every job that has at least 50 candidates in its stages so we stop taking applications, and list what you closed. Leave private jobs alone." → `list_jobs`, `list_candidates`, `set_job_visibility`
- **Log interview notes and tag candidates** (runs: daily): "Here are my notes from today's interviews. Add each as a note on the candidate it belongs to, and tag the ones I liked with "shortlist"." → `list_candidates`, `add_candidate_note`, `add_candidate_tag`
- **Weekly hiring pipeline report** (runs: weekly): "Every Monday, list my active jobs with the number of candidates in each stage and who has waited longest for a reply." → `list_jobs`, `get_job`, `list_candidates`
- **Move candidates to a better-fitting job**: "Candidates in Office Manager who match the Customer Success Manager role: move them there and tell me who you moved." → `list_candidates`, `list_jobs`, `move_candidate_to_job`

## Can Homerun automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Homerun connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to disqualify unqualified candidates in bulk, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/homerun/jobs/{job_id}/candidates. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/homerun/jobs/{job_id}/candidates with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Homerun.

### list_jobs

List your jobs with their state and visibility. Access: read. REST: `GET /api/v1/homerun/jobs`. MCP: `homerun_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | string | no | draft, active or archived. Default active. |
| `visibility` | string | no | public, private or closed. Only for active jobs. |

Returns each job with its ID, title, state and visibility, in the order of the Jobs page. Draft jobs are visible only to the hiring team, which includes the account the agent uses. Use the ID in every other call.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "job_3b7e91",
      "title": "Customer Success Manager",
      "state": "active",
      "visibility": "public"
    },
    {
      "job_id": "job_9d4a27",
      "title": "Product Designer",
      "state": "active",
      "visibility": "public"
    },
    {
      "job_id": "job_c51f08",
      "title": "Office Manager",
      "state": "active",
      "visibility": "private"
    }
  ]
}
```

### get_job

Read one job: its hiring stages, closing date and application form questions. Access: read. REST: `GET /api/v1/homerun/jobs/{job_id}`. MCP: `homerun_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |

Returns the job state and visibility, the hiring stages in order, the closing date if one is set and the questions of the application form. Stage names are specific to each job, so read them here before moving anyone.

Example response:

```json
{
  "job_id": "job_3b7e91",
  "title": "Customer Success Manager",
  "state": "active",
  "visibility": "public",
  "closing_date": null,
  "stages": [
    "Application",
    "Phone call",
    "Interview",
    "Offer"
  ],
  "application_questions": [
    "Why do you want this role?",
    "How many years of customer-facing experience do you have?"
  ]
}
```

### list_candidates

List the candidates of one job, filtered by stage, tag or status. Access: read. REST: `GET /api/v1/homerun/jobs/{job_id}/candidates`. MCP: `homerun_read → list_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `stage` | string | no | Stage name as shown in get_job, for example Application. |
| `tag` | string | no | Tag name from list_tags. |
| `status` | string | no | active or disqualified. Default active. |

Returns each candidate with their ID, name, stage, origin (applied or sourced), tags, application date and whether the first reply is overdue. Disqualified candidates are returned only with status disqualified, as Homerun shows them in Table view only.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": "ap_N4pQ8sT2vX6zB1cD3eF5",
      "name": "Dana Whitfield",
      "stage": "Application",
      "origin": "applied",
      "tags": [],
      "applied_at": "2026-10-20",
      "first_reply_overdue": true
    },
    {
      "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
      "name": "Priya Raman",
      "stage": "Application",
      "origin": "applied",
      "tags": [
        "shortlist"
      ],
      "applied_at": "2026-10-18",
      "first_reply_overdue": true
    }
  ]
}
```

### get_candidate

Read a candidate profile with answers, ratings, notes and messages. Access: read. REST: `GET /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}`. MCP: `homerun_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |

Returns the contact details, the current stage and the stages passed, the answers to the application form, ratings, notes, tags and the latest messages. A candidate belongs to one job, so the same person applying twice has two IDs.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "name": "Priya Raman",
  "email": "priya.raman@example.com",
  "stage": "Application",
  "answers": [
    {
      "question": "How many years of customer-facing experience do you have?",
      "answer": "4"
    }
  ],
  "rating": 4,
  "notes": [],
  "tags": [
    "shortlist"
  ],
  "messages": []
}
```

### list_tags

List the tags your company uses on candidates. Access: read. REST: `GET /api/v1/homerun/tags`. MCP: `homerun_read → list_tags`.

No parameters.

Returns every tag name in Settings under Candidates, Tags. Use a name from here in add_candidate_tag to reuse a tag instead of creating a near-duplicate.

Example response:

```json
{
  "tags": [
    "shortlist",
    "referral",
    "talent pool"
  ]
}
```

### list_disqualification_reasons

List the reasons you can give when disqualifying a candidate. Access: read. REST: `GET /api/v1/homerun/disqualification-reasons`. MCP: `homerun_read → list_disqualification_reasons`.

No parameters.

Returns Homerun's own reasons and the ones your company added. The reason you give to disqualify_candidate must match one of these names exactly.

Example response:

```json
{
  "reasons": [
    "Too junior",
    "Too senior",
    "No relevant experience",
    "Position was filled",
    "Position was put on hold",
    "Perhaps in the future",
    "Salary expectation too high",
    "Accepted another offer",
    "Stopped responding or didn't show",
    "Not willing to relocate"
  ]
}
```

### add_candidate_note

Add an internal note to a candidate profile. Access: write. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/note`. MCP: `homerun_write → add_candidate_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `text` | string | yes | The note text. Leave out @mentions: they notify colleagues. |

Adds a note that the hiring team sees on the profile and the candidate never sees. It reaches nobody unless it mentions a colleague, which the agent avoids, so it does not wait for your OK. Returns the note with its time.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "added",
  "text": "First reply sent 22 Oct. Promised an answer on interviews by Friday.",
  "created_at": "2026-10-22T09:14:00Z"
}
```

### add_candidate_tag

Add a tag to a candidate, creating the tag if it does not exist. Access: write. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/tag`. MCP: `homerun_write → add_candidate_tag`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `tag` | string | yes | Tag name, preferably one from list_tags. |

Adds the tag to the profile below the contact information. A new name creates a new tag for the whole company, so check list_tags first. Tags are internal and removed with one call of remove_candidate_tag, so it does not wait for your OK.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "tagged",
  "tags": [
    "shortlist"
  ]
}
```

### remove_candidate_tag

Remove a tag from a candidate. Access: write. REST: `DELETE /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/tag`. MCP: `homerun_write → remove_candidate_tag`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `tag` | string | yes | Tag name on the candidate. |

Removes the tag from this profile only; the tag stays in the company list. It reaches nobody and add_candidate_tag undoes it, so it does not wait for your OK.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "untagged",
  "tags": []
}
```

### move_candidate_to_stage

Move a candidate to another hiring stage of the same job. Access: write, asks the user first. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/to-stage/move`. MCP: `homerun_write → move_candidate_to_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `stage` | string | yes | Stage name as shown in get_job. |

Moves the candidate and returns the old and new stage. Homerun can send an email automatically when a candidate enters a stage, if your account set one up, so a move can reach the candidate. A name that is not a stage of this job fails and lists the stages. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "moved",
  "from_stage": "Application",
  "to_stage": "Phone call"
}
```

### move_candidate_to_job

Move a candidate to another job. Access: write, asks the user first. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/to-job/move`. MCP: `homerun_write → move_candidate_to_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `target_job_id` | string | yes | Job ID of the new job from list_jobs. |

Moves the whole profile: CV, contact details, answers and application review stay, but stage reviews, scorecards and stage history of the old job are deleted. The candidate lands in the same stage in the new job, or in the first stage if it has no such stage. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "ap_N4pQ8sT2vX6zB1cD3eF5",
  "status": "moved",
  "from_job": "Office Manager",
  "to_job": "Customer Success Manager",
  "stage": "Application"
}
```

### disqualify_candidate

Disqualify a candidate with a reason and choose whether to tell them. Access: write, asks the user first. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/disqualify`. MCP: `homerun_write → disqualify_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `reason` | string | yes | A name from list_disqualification_reasons. |
| `notify` | string | no | none, email or todo. Default none. |
| `email_body` | string | no | Message to send when notify is email. |

Removes the candidate from the job's list of all candidates and records the reason, which the candidate does not see. With notify email the message goes out at once; with todo Homerun creates a to-do for you instead. A disqualified candidate can be re-qualified in Homerun. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "ap_N4pQ8sT2vX6zB1cD3eF5",
  "status": "disqualified",
  "reason": "No relevant experience",
  "notified": "none",
  "stage_before": "Application"
}
```

### send_candidate_email

Send an email to one candidate through Homerun. Access: write, asks the user first. REST: `POST /api/v1/homerun/jobs/{job_id}/candidates/{candidate_id}/email`. MCP: `homerun_write → send_candidate_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `candidate_id` | string | yes | Candidate ID from list_candidates. |
| `body` | string | yes | The email text. |

Sends the email at once. It shows in the candidate's Activity and message modal, and a reply from the candidate lands there too. A sent email cannot be unsent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "sent",
  "sent_at": "2026-10-22T09:12:00Z"
}
```

### set_job_visibility

Make an active job public, private or closed. Access: write, asks the user first. REST: `PUT /api/v1/homerun/jobs/{job_id}/visibility`. MCP: `homerun_write → set_job_visibility`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `visibility` | string | yes | public, private or closed. |

Works on active jobs; a draft or archived job returns an error. Closed stops new applications and keeps the hiring process going; anyone with the link sees "Applications closed". Public shows the job to everyone, private only to people with the share link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "job_9d4a27",
  "title": "Product Designer",
  "state": "active",
  "visibility": "closed"
}
```

## How do I connect Homerun to Claude Code, Codex or Cursor?

Connecting Homerun takes three steps: sign up, sign in to Homerun once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Homerun to your agent.

1. **Create an account** Sign up and add Homerun in the console. Your API key is there too.

2. **Sign in to Homerun in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Homerun there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Homerun tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through the candidates in the Application stage of Customer Success Manager. Disqualify the ones whose answers show no relevant experience, without emailing them, and leave every unclear one for me with a one-line reason.
```

### Call Homerun from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/homerun with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/homerun/jobs/job_3b7e91/candidates/ap_K2mP7rS1uW5yA9bC3dE6/to-stage/move \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stage":"Phone call"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
  "status": "moved",
  "from_stage": "Application",
  "to_stage": "Phone call"
}
```

## Why use Cotlet for Homerun?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Homerun yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Homerun changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Homerun to Cotlet?

Yes. You sign in to Homerun yourself, in your own Cloud Browser, and we never save your password. Your agents only get Homerun once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Homerun integration?**

No, Cotlet is independent of Homerun. Homerun's own API is too limited for this work. Cotlet works through your own Homerun account, the way you use Homerun in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Homerun in your console: your agents lose access at once and you stay signed in. Signing out of Homerun in the browser works too, and Reset browser deletes the whole profile.

## Is there a Homerun MCP server on GitHub?

Yes. Community Homerun MCP servers exist on GitHub, usually maintained by one person. They call the Public API, so you need a paid plan and an admin key, and they cannot change a job. You install one yourself and fix it when Homerun changes. Cotlet hosts the same kind of server for you, works in your own account, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask an admin for an API key, clone the repo, install it, add it to each MCP client | Sign up, sign in to Homerun once, add one MCP server or API key |
| When Homerun changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Homerun access | An API key in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until an admin issues a new key or you replace an expired one | Your Cloud Browser keeps you signed in; if Homerun logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Homerun changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Homerun API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Homerun API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Homerun account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Homerun yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Homerun only after you enable it. When Homerun signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Homerun, sign out of Homerun in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Homerun's terms:** You use your own Homerun account and stay responsible for following Homerun's terms. Cotlet is independent and not affiliated with Homerun. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Homerun in the console and press Request access. Then you create your API key and connect Homerun there.

**Do I need to be technical?**

No. You sign in to Homerun once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Homerun to Cotlet?**

Yes. You sign in to Homerun yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Homerun once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Homerun sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Homerun cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Homerun's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Homerun sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Homerun login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Homerun offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a paid Homerun plan or an API key?**

No key. Homerun's own Public API is for paid plans only, trials are excluded, and only an admin can generate a key. Cotlet works in your own Homerun account instead, so what your agent can do follows your permissions in Homerun.

**Can it create or edit a job post?**

No. The tools read jobs and change their visibility between public, private and closed. Writing and publishing a job post stays in Homerun, as it does in the Public API, where jobs are read-only.

**Does a candidate see why they were disqualified?**

No. Homerun does not share the disqualification reason with the candidate. They hear only from an email, and disqualify_candidate sends one only when you set notify to email.

**Can my agent post or send messages in Homerun without asking me?**

No. Every call to move_candidate_to_stage, move_candidate_to_job, disqualify_candidate, send_candidate_email or set_job_visibility waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_candidate_note, add_candidate_tag, remove_candidate_tag runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Homerun API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/homerun from the HTTP Request node.

---

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.