[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)

# Comeet API and MCP server

> Comeet, now Spark Hire Recruit, has a Recruiting API, but Comeet grants access at its sole discretion under partner terms (checked 22 Oct 2026). Its beta MCP connection for ChatGPT and Claude searches live candidate, position and pipeline data and lists nothing that changes a record.

Applicant tracking system, now called Spark Hire Recruit: positions with hiring workflows, candidates moving through steps, interviews, comments and offers in one place.

## What is the Comeet API?

Cotlet's Comeet API exposes 12 endpoints for your own Comeet account: list positions, get position, list candidates, get candidate, list my tasks, list candidate activity, tag candidate, add candidate, comment on candidate, set candidate status, decide Go/No-go step and invite to self-schedule. The list_positions endpoint returns positions you can see, with department, location, status and hiring team. Each endpoint takes simple JSON inputs like candidate_id, cursor or position_id and works both as an operation of the comeet_read or comeet_write MCP tool for agents and as a REST call for scripts.

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

Comeet, now Spark Hire Recruit, has a Recruiting API, but Comeet grants access at its sole discretion under partner terms (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Comeet with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Comeet have an official API?

Comeet, now Spark Hire Recruit, has a Recruiting API, but Comeet grants access at its sole discretion under partner terms (checked 22 Oct 2026). Its beta MCP connection for ChatGPT and Claude searches live candidate, position and pipeline data and lists nothing that changes a record.

| Task | Comeet official | Cotlet |
|---|---|---|
| Search candidates, positions and pipeline | Partly: Beta MCP searches live data; the Recruiting API lists candidates and positions for approved access only | Yes |
| Read one candidate with steps and tags | Partly: Recruiting API for approved access | Yes |
| Add a candidate to a position | Partly: Recruiting API for approved access | Yes |
| Change candidate status, reject with a reason | No | Yes |
| Decide a Go/No-go step | No | Yes |
| Invite a candidate to pick an interview time | No | Yes |
| Comment on a candidate and mention teammates | No | Yes |
| Tag candidates | No | Yes |

Sources: [Spark Hire Recruit for Developers](https://developers.comeet.com/), [Terms of Use for Comeet API](https://recruit-support.sparkhire.com/hc/en-us/articles/40045047401371-Terms-of-Use-for-Comeet-API), [Spark Hire changelog: Recruit MCP (beta)](https://sparkhire.canny.io/changelog), [Recruit Help: Manage multiple candidates](https://recruit-support.sparkhire.com/hc/en-us/articles/40045064475419-Manage-multiple-candidates)

## For AI agents

```text
Comeet, now Spark Hire Recruit, has a Recruiting API, but Comeet grants access at its sole discretion under partner terms (checked 22 Oct 2026). Its beta MCP connection for ChatGPT and Claude searches live candidate, position and pipeline data and lists nothing that changes a record.
Cotlet provides a hosted MCP server and REST API for Comeet: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=comeet, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    comeet_read, comeet_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/comeet, each operation at its own route, e.g. PUT /api/v1/comeet/candidates/{candidate_id}/status
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_positions, get_position, list_candidates, get_candidate, list_my_tasks, list_candidate_activity, tag_candidate, add_candidate, add_comment, set_candidate_status, decide_go_no_go, invite_to_self_schedule
Confirm      add_candidate, add_comment, set_candidate_status, decide_go_no_go, invite_to_self_schedule (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/comeet-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=comeet, requests Comeet in the Cotlet console and creates an API key there.
2. The user signs in to Comeet once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Comeet 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 Comeet server that someone else maintains, including non-developers.

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 Comeet 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 Comeet 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 Comeet 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 Comeet's terms; Cotlet is not affiliated with Comeet.
```

## What can an AI agent do in Comeet?

Cotlet is best for recruiters and hiring leads who use Comeet and want their AI agent to reject, schedule and chase decisions without running or fixing a server.

- **[Reject candidates in bulk with a reason](https://cotlet.dev/integrations/comeet-api-mcp-server/reject-candidates-with-reason.md)** (runs: weekly): "In the Senior Product Designer position, find candidates still at Application review for more than 14 days. Reject the ones with no portfolio link, with the reason "Incomplete application", and list the rest for me." → `list_candidates`, `get_candidate`, `set_candidate_status`
- **[Invite candidates to pick an interview time](https://cotlet.dev/integrations/comeet-api-mcp-server/invite-candidates-to-self-schedule.md)** (runs: daily): "List candidates in the Senior Product Designer position who reached the Interview with hiring manager step and have no invitation yet. Invite each one to select a time with my own video link." → `list_candidates`, `get_candidate`, `invite_to_self_schedule`
- **[Chase pending Go/No-go decisions](https://cotlet.dev/integrations/comeet-api-mcp-server/chase-go-no-go-decisions.md)** (runs: daily): "Find candidates in my open positions waiting at a Go/No-go step for more than 3 days. For each, comment on the candidate and @mention the person who has to decide, visible to the position recruiters only." → `list_candidates`, `list_candidate_activity`, `add_comment`
- **Tag candidates for a talent pool**: "Tag every rejected candidate in the Senior Product Designer position who reached the final interview with "silver medalist", so I can search for them next time." → `list_candidates`, `tag_candidate`
- **Weekly hiring pipeline summary** (runs: weekly): "Every Monday, list my open positions with the number of candidates at each step and the ones that did not move for 14 days." → `list_positions`, `list_candidates`

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

Yes. Cotlet does not replace your automation platform: it gives it a Comeet 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 reject candidates in bulk with a reason, 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/comeet/positions/{position_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/comeet/positions/{position_id}/candidates with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 Comeet.

### list_positions

Positions you can see, with department, location, status and hiring team. Access: read. REST: `GET /api/v1/comeet/positions`. MCP: `comeet_read → list_positions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | open (default), on_hold, closed or all. |
| `department` | string | no | Only positions of this department. |
| `limit` | integer | no | 1 to 30. Default: 30. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the positions your account can see, 30 to a page; pass next_cursor back as cursor for the next page. status picks open, on_hold or closed positions. Each position carries its department, location, hiring manager and lead recruiter. Use position_id in the other tools.

Example response:

```json
{
  "positions": [
    {
      "position_id": "pos_21c4",
      "name": "Senior Product Designer",
      "department": "Design",
      "location": "Remote, EU",
      "status": "open",
      "hiring_manager": "Dana Cho",
      "lead_recruiter": "Ravi Shah"
    },
    {
      "position_id": "pos_21d9",
      "name": "Backend Engineer",
      "department": "Engineering",
      "location": "Berlin",
      "status": "open",
      "hiring_manager": "Leo Park",
      "lead_recruiter": "Ravi Shah"
    }
  ],
  "next_cursor": null
}
```

### get_position

One position with its workflow steps, hiring team and openings. Access: read. REST: `GET /api/v1/comeet/positions/{position_id}`. MCP: `comeet_read → get_position`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `position_id` | string | yes | Position from list_positions. |

Returns the position details, its workflow in order with each step type (go_no_go, interview, administrative, offer, send_notification), the hiring team with position roles, and the openings with their status. A candidate cannot be marked hired unless an opening is open. Positions you cannot see return APP_PERMISSION_DENIED.

Example response:

```json
{
  "position_id": "pos_21c4",
  "name": "Senior Product Designer",
  "status": "open",
  "workflow": [
    {
      "step": "Application review",
      "type": "administrative"
    },
    {
      "step": "Hiring manager screen",
      "type": "go_no_go"
    },
    {
      "step": "Interview with hiring manager",
      "type": "interview"
    }
  ],
  "hiring_team": [
    {
      "name": "Dana Cho",
      "role": "hiring_manager"
    },
    {
      "name": "Ravi Shah",
      "role": "recruiter"
    }
  ],
  "openings": [
    {
      "status": "open"
    }
  ]
}
```

### list_candidates

Candidates of a position with status, current step, assignee and source. Access: read. REST: `GET /api/v1/comeet/positions/{position_id}/candidates`. MCP: `comeet_read → list_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `position_id` | string | yes | Position from list_positions. |
| `status` | enum | no | in_progress (default), on_hold, rejected, withdrawn, hired. |
| `step` | string | no | Current workflow step name. |
| `step_type` | enum | no | go_no_go, interview, administrative, offer or send_notification. |
| `assignee` | string | no | Teammate who holds the current step. |
| `tag` | string | no | Only candidates with this tag. |
| `limit` | integer | no | 1 to 30. Default: 30. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the candidates of one position, 30 to a page; pass next_cursor back as cursor. Filters match what the Recruit position view offers: status, step, step type, assignee, tag and source. waiting_since is when the candidate reached the current step. Only candidates you may see are returned; evaluations of hired candidates stay hidden for other roles.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": "cand_5a11c8",
      "name": "Mia Jensen",
      "status": "in_progress",
      "current_step": "Hiring manager screen",
      "step_type": "go_no_go",
      "assignee": "Dana Cho",
      "source": "Careers website",
      "waiting_since": "2026-10-16"
    },
    {
      "candidate_id": "cand_7d21a9",
      "name": "Noah Kim",
      "status": "in_progress",
      "current_step": "Application review",
      "step_type": "administrative",
      "assignee": "Ravi Shah",
      "source": "Referral",
      "waiting_since": "2026-10-02"
    }
  ],
  "next_cursor": null
}
```

### get_candidate

One candidate with profile details, status, workflow steps and tags. Access: read. REST: `GET /api/v1/comeet/candidates/{candidate_id}`. MCP: `comeet_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |

Returns the profile fields Recruit shows (contact details, source, position, application answers when present), the status, the workflow with each step done or pending, scheduled interviews and tags. Resume files are not returned, only their names. Roles that may not see a hired candidate's evaluations get none.

Example response:

```json
{
  "candidate_id": "cand_3b90e4",
  "name": "Priya Nair",
  "position": "Senior Product Designer",
  "status": "in_progress",
  "source": "Careers website",
  "workflow": [
    {
      "step": "Application review",
      "state": "done"
    },
    {
      "step": "Interview with hiring manager",
      "state": "pending",
      "invitation": null
    }
  ],
  "scheduled_interviews": [],
  "tags": [
    "portfolio strong"
  ],
  "resume_files": [
    "priya-nair-cv.pdf"
  ]
}
```

### list_my_tasks

Candidates with a task assigned to the signed-in account, as in My tasks. Access: read. REST: `GET /api/v1/comeet/my-tasks`. MCP: `comeet_read → list_my_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `step_type` | enum | no | go_no_go, interview, administrative, offer or send_notification. |
| `position_id` | string | no | Only tasks of this position. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the candidates with tasks assigned to your account, newest assignment last, 30 to a page. step_type narrows the list to one kind of task, as the Filters in My tasks do. Tasks of other teammates are not included; use list_candidates with assignee for those.

Example response:

```json
{
  "tasks": [
    {
      "candidate_id": "cand_5a11c8",
      "name": "Mia Jensen",
      "position": "Senior Product Designer",
      "step": "Hiring manager screen",
      "step_type": "go_no_go",
      "assigned_at": "2026-10-16"
    }
  ],
  "next_cursor": null
}
```

### list_candidate_activity

Comments, emails, meetings and status changes from a candidate's activity log. Access: read. REST: `GET /api/v1/comeet/candidate-activities`. MCP: `comeet_read → list_candidate_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |
| `filter` | enum | no | recent (default), internal, candidate or screening_and_interviews. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the entries of the activity log, newest first, 30 to a page. filter picks what Recruit's log filters show: recent, internal, candidate, screening_and_interviews. Comments hidden from your role are not returned.

Example response:

```json
{
  "entries": [
    {
      "type": "comment",
      "author": "Ravi Shah",
      "body": "@Dana Cho please decide on this one",
      "visibility": "position_recruiters",
      "at": "2026-10-19T09:12:00Z"
    },
    {
      "type": "status_change",
      "author": "Ravi Shah",
      "body": "Moved to Hiring manager screen",
      "at": "2026-10-16T08:40:00Z"
    }
  ],
  "next_cursor": null
}
```

### tag_candidate

Add a tag to a candidate, or remove one. Access: write. REST: `POST /api/v1/comeet/candidates/{candidate_id}/tag`. MCP: `comeet_write → tag_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |
| `tag` | string | yes | Name of an existing tag. |
| `action` | enum | no | add (default) or remove. |

Adds or removes one tag from Library > Tags on a candidate. A tag that does not exist is not created here, because only Owners and Admins add new tags. Tags are shared across all the candidate's hiring processes, so a change shows in every position. It reaches nobody and is undone with one call (action remove), so it does not wait for your OK.

Example response:

```json
{
  "candidate_id": "cand_7d21a9",
  "tags": [
    "silver medalist"
  ],
  "changed": "added"
}
```

### add_candidate

Create a candidate on a position. Access: write, asks the user first. REST: `POST /api/v1/comeet/positions/{position_id}/candidates`. MCP: `comeet_write → add_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `full_name` | string | yes | Candidate's full name. |
| `position_id` | string | yes | Position from list_positions. |
| `source` | string | yes | Source name as Recruit lists it. |
| `posting_location` | string | yes | One of the position's posting locations. |
| `email` | string | no | Candidate email. |
| `phone` | string | no | Candidate phone. |

Creates a candidate with the fields Recruit requires: full name, source, position and posting location. Email, phone, salary expectations and availability are optional. It does not check for duplicates, so search with list_candidates first. Email templates that fire on workflow steps still apply, so the candidate may hear from Recruit. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "cand_8e44b0",
  "name": "Ana Lopez",
  "position": "Backend Engineer",
  "source": "Referral",
  "status": "in_progress",
  "current_step": "Application review"
}
```

### add_comment

Post a comment on a candidate profile and tag teammates with @. Access: write, asks the user first. REST: `POST /api/v1/comeet/candidates/{candidate_id}/comments`. MCP: `comeet_write → add_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |
| `body` | string | yes | Comment text, with @ and a name to tag. |
| `visibility` | enum | no | position_access (default), hiring_leadership, position_recruiters or only_me. |

Posts one comment on the activity log. Type @ and a teammate's name in the body to tag them; every tagged teammate gets an email with the thread. visibility is one of position_access, hiring_leadership, position_recruiters or only_me, and the teammates you can tag are limited to those who may see the discussion. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "cmt_90f2",
  "candidate_id": "cand_5a11c8",
  "visibility": "position_recruiters",
  "mentioned": [
    "Dana Cho"
  ],
  "posted_at": "2026-10-22T08:05:00Z"
}
```

### set_candidate_status

Change a candidate to in progress, on hold, rejected, withdrawn or hired. Access: write, asks the user first. REST: `PUT /api/v1/comeet/candidates/{candidate_id}/status`. MCP: `comeet_write → set_candidate_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |
| `status` | enum | yes | in_progress, on_hold, rejected, withdrawn or hired. |
| `last_step` | string | no | Last completed step; required for rejected and withdrawn. |
| `completed_by` | array | no | Participants who completed a Go/No Go or Interview last step. |
| `reason` | string | no | Disposition reason text, e.g. Incomplete application. |
| `note` | string | no | Optional note stored with the reason. |
| `notify` | enum | no | none (default), create_send_notification_step or send_message. |
| `opening` | string | no | Opening the hire fills; required for hired. |
| `application_date` | date | no | When the hiring process began; required for hired. |
| `first_day` | date | no | First day of work; required for hired. |

Sets the status as the status list on the profile does. rejected and withdrawn need last_step, the last completed workflow step; for a Go/No Go or Interview step pass completed_by, the participants of that step. reason is one of your disposition reasons, and is required when your company made them required. hired needs opening, application_date and first_day. A change from in progress cancels future scheduled interviews. notify decides whether the candidate hears about a rejection: none (default), create_send_notification_step or send_message. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "cand_7d21a9",
  "name": "Noah Kim",
  "position": "Senior Product Designer",
  "status": "rejected",
  "last_step": "Application review",
  "reason": "Incomplete application",
  "note": "No portfolio link in the application.",
  "notified": "none",
  "cancelled_interviews": 0
}
```

### decide_go_no_go

Click Go or No-go on a candidate's Go/No-go step. Access: write, asks the user first. REST: `POST /api/v1/comeet/candidates/{candidate_id}/go-no-go/decide`. MCP: `comeet_write → decide_go_no_go`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate at a Go/No-go step. |
| `decision` | enum | yes | go or no_go. |
| `reason` | string | no | Rejection reason; required for no_go. |
| `notify` | enum | no | none (default), create_send_notification_step or send_message. |

Completes the candidate's current Go/No-go step. go moves the candidate on to the next step. no_go needs reason and ends the process as a rejection, and notify works as in set_candidate_status. Your account must be allowed to decide that step. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "cand_5a11c8",
  "step": "Hiring manager screen",
  "decision": "go",
  "next_step": "Interview with hiring manager"
}
```

### invite_to_self_schedule

Email a candidate a link to pick their interview time. Access: write, asks the user first. REST: `POST /api/v1/comeet/candidates/{candidate_id}/self-schedule/invite`. MCP: `comeet_write → invite_to_self_schedule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate at an interview step. |
| `step` | string | yes | Interview step name. |
| `online_meeting` | enum | no | none (default), zoom or custom_link. |
| `custom_link` | string | no | Video interview URL for custom_link. |

Does what Schedule > Invite a candidate to select a time does on an interview step. online_meeting is none, zoom or custom_link; custom_link needs the URL, and zoom needs a plan that includes it. The candidate sees your availability at the moment they open the link, and the link expires after 5 days by default. It fails if Auto-scheduling is not configured by an Admin. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "cand_3b90e4",
  "name": "Priya Nair",
  "step": "Interview with hiring manager",
  "invitation": "sent",
  "online_meeting": "custom_link",
  "expires_in_days": 5
}
```

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

Connecting Comeet takes three steps: sign up, sign in to Comeet 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 Comeet to your agent.

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

2. **Sign in to Comeet in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Comeet 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 Comeet 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.

```
In the Senior Product Designer position, find candidates still at Application review for more than 14 days. Reject the ones with no portfolio link, with the reason "Incomplete application", and list the rest for me.
```

### Call Comeet 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/comeet 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 PUT https://cotlet.dev/api/v1/comeet/candidates/cand_7d21a9/status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"rejected","last_step":"Application review","reason":"Incomplete application","note":"No portfolio link in the application."}'
```

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

```
{
  "candidate_id": "cand_7d21a9",
  "name": "Noah Kim",
  "position": "Senior Product Designer",
  "status": "rejected",
  "last_step": "Application review",
  "reason": "Incomplete application",
  "note": "No portfolio link in the application.",
  "notified": "none",
  "cancelled_interviews": 0
}
```

## Why use Cotlet for Comeet?

**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 Comeet 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 Comeet changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Comeet to Cotlet?

Yes. You sign in to Comeet yourself, in your own Cloud Browser, and we never save your password. Your agents only get Comeet 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 Comeet integration?**

No, Cotlet is independent of Comeet. Comeet's own API is open only to approved partners. Cotlet works through your own Comeet account, the way you use Comeet 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 Comeet in your console: your agents lose access at once and you stay signed in. Signing out of Comeet in the browser works too, and Reset browser deletes the whole profile.

## Is there a Comeet MCP server on GitHub?

No hosted server or Zapier app does this today. The vendor's beta MCP searches only, the Recruiting API needs access from Comeet, and everything else is clicked by hand in Recruit. Cotlet works in your own Recruit account and hosts the tools for you.

|  | By hand in Recruit | Cotlet |
|---|---|---|
| Setup | Nothing to set up, but every step is a click | Sign up, sign in to Comeet once, add one MCP server or API key |
| Rejecting many candidates | Select candidates, open the three-dot menu, Set status, Rejected, pick a reason | Your agent applies your rule and sets status with a reason for each candidate |
| Your Comeet session | Your browser | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You sign in again | If Comeet logs you out, your agent gets a link to sign in again |
| Upkeep | None | Nothing to host or update; our team tests it daily and fixes it when Comeet changes |
| Where it runs | Your browser, while you are in it | 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 Comeet 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 Comeet API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Comeet 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 Comeet 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 Comeet 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 Comeet only after you enable it. When Comeet 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 Comeet, sign out of Comeet 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.
- **Comeet's terms:** You use your own Comeet account and stay responsible for following Comeet's terms. Cotlet is independent and not affiliated with Comeet. [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 Comeet in the console and press Request access. Then you create your API key and connect Comeet there.

**Do I need to be technical?**

No. You sign in to Comeet 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 Comeet to Cotlet?**

Yes. You sign in to Comeet yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Comeet 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 Comeet 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 Comeet 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 Comeet's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Comeet 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 Comeet 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?**

Comeet 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).

**Which Comeet role does my account need?**

The tools use your own permissions. At position level, recruiters, recruiting coordinators, hiring managers, managers and recruiting assistants can change candidate status; interviewers and viewers cannot. Tags need the permission to edit candidate tags, and a call without the right role fails with APP_PERMISSION_DENIED.

**How is this different from the official MCP connection?**

Spark Hire's MCP connection for ChatGPT and Claude is in beta and lists searching live candidate, position and pipeline data. Cotlet adds the actions you take in the app: status changes, Go/No-go decisions, scheduling invitations, comments and tags, signed in as you.

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

No. Every call to add_candidate, add_comment, set_candidate_status, decide_go_no_go or invite_to_self_schedule waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. tag_candidate runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Comeet 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/comeet 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.