Comeet MCP Server
Candidates, positions and hiring decisions in Comeet, from your agent.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/comeet'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Comeet API and MCP server: Let your AI agent clear the Comeet hiring queue.
Spark Hire Recruit, the new name of Comeet, opened a beta MCP connection on 12 Oct 2026 that searches candidates, positions and the pipeline in plain words. Its Recruiting API comes with Enterprise or as a paid add-on, and no call in it changes a status, decides a step, invites to an interview or tags (checked 27 Oct 2026). Cotlet runs 12 Comeet tools hosted, over MCP for agents and REST for scripts.
Candidates, positions and hiring decisions in Comeet, from your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Comeet or Spark Hire
- Page: https://cotlet.dev/integrations/comeet-api-mcp-server
What can you automate in Comeet?
- Reject stale candidates with a reason
- Invite candidates to pick an interview time
- Chase Go/No-go decisions that wait too long
- Decide Go or No-go on your own steps
- Tag silver medalists for the next opening
- Report candidates per step for each position
Does Comeet have an MCP server or an API?
- Recruit's changelog lists one MCP feature: "Search live candidate, position, and pipeline data using natural language". The terms updated on 27 Oct 2026 already describe an MCP that may "create, update, delete", so that may change.
- The API needs a request form and a secret from Recruit support, and "Permissions for the integration are defined by the Recruit representative". The only webhook reports position updates.
- Zapier, n8n and Pipedream have no Comeet or Recruit app (checked 27 Oct 2026).
| What you need | Recruit MCP (beta) | Recruiting API | Cotlet |
|---|---|---|---|
| Search candidates and positions | Yes, in plain words | Yes | Yes |
| Add a candidate to a position | Not listed | Yes | Yes, after your OK |
| Reject with a disposition reason | Not listed | No | Yes, after your OK |
| Go or No-go on a step | Not listed | No | Yes, after your OK |
| Invite to self-schedule | Not listed | No | Yes, after your OK |
| Comment with @mention, tag | Not listed | A note, no @ or tags | Yes |
| What you need first | An admin turns it on per role | Enterprise or add-on, plus approval | Your Comeet login |
Checked 27 Oct 2026. Sources: Spark Hire Recruit for Developers, Terms of Use for Comeet API, Spark Hire changelog: Recruit MCP (beta), Recruit Help: Manage multiple candidates, Recruiting API: Getting Started for Recruit customers, Recruiting API: Permissions, Spark Hire pricing, Recruit Additional Service Terms
How does Cotlet connect to Comeet?
- Sign in to Comeet. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Comeet password, and no rejection, invitation or decision a candidate or teammate would notice happens before you approve it.
Connect Comeet to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to Comeet in a Cloud Browser. Create a Cotlet account, open Comeet in its Cloud Browser, sign in to app.comeet.co with your own Recruit user and press Enable for agents. No Recruiting API secret needed.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the Cotlet console.
Comeet and every other app on your Cotlet account answer at one address, https://cotlet.dev/mcp/v1. If you enable Comeet after the agent is connected, refresh the connector so the new tools show up.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: comeet_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: comeet_write
How to use the Comeet REST API
Create your Cotlet API key
Create a Cotlet API key with access to Comeet and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Comeet in Cotlet and enable it for agents. Account access: Your own Comeet (Spark Hire Recruit) account; changing status needs a position role of recruiter, recruiting coordinator, hiring manager, manager or recruiting assistant.
Make your first Comeet API request
REST:
curl https://cotlet.dev/api/v1/comeet/positions \
-H "Authorization: Bearer $COTLET_API_KEY"
Read positions and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "comeet",
"tool": "list_positions",
"result": {
"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
}
}
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.
limit: 1 to 30. Default: 30.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Comeet workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Candidates of a position with status, current step, assignee and source. Use list_candidates in your configured team report. |
| Make | HTTP > Make a request | Candidates with a task assigned to the signed-in account, as in My tasks. Use list_my_tasks in your configured team report. |
| Python or Node.js | REST API | Comments, emails, meetings and status changes from a candidate's activity log. Use list_candidate_activity in your configured team report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Comeet; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Comeet API endpoints and MCP tools
Positions and candidates
Filters follow the Recruit position view. A position marked discreet stays hidden unless your role sees it.
- List positions (
list_positions, read): Positions you can see, with department, location, status and hiring team. - Get position (
get_position, read): One position with its workflow steps, hiring team and openings. - List candidates (
list_candidates, read): Candidates of a position with status, current step, assignee and source. - Get candidate (
get_candidate, read): One candidate with profile details, status, workflow steps and tags. - Add candidate (
add_candidate, write, asks first): Create a candidate on a position.
Status and steps
Rejected and Withdrawn need the last completed step. Leaving In progress cancels future interviews, and the candidate hears nothing unless you set notify.
- Set candidate status (
set_candidate_status, write, asks first): Change a candidate to in progress, on hold, rejected, withdrawn or hired. - Decide Go/No-go step (
decide_go_no_go, write, asks first): Click Go or No-go on a candidate's Go/No-go step. - Invite to self-schedule (
invite_to_self_schedule, write, asks first): Email a candidate a link to pick their interview time.
Tasks, comments and tags
Each @mention emails the teammate. New tags come only from an Owner or Admin in Library > Tags.
- List my tasks (
list_my_tasks, read): Candidates with a task assigned to the signed-in account, as in My tasks. - List candidate activity (
list_candidate_activity, read): Comments, emails, meetings and status changes from a candidate's activity log. - Comment on candidate (
add_comment, write, asks first): Post a comment on a candidate profile and tag teammates with @. - Tag candidate (
tag_candidate, write): Add a tag to a candidate, or remove one.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/comeet-api-mcp-server#tools
Who can see my Comeet session, and how do I revoke it?
- What we store. Your signed-in Recruit profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 12 Comeet tools. No cookie, password or API secret.
- What the session sees. The positions your role is on. An Interviewer or Viewer sees less and cannot change a status.
- What no tool touches. Offers, resumes as files, settings, teammates and integrations.
- If Recruit signs you out. We email you a sign-in link. You sign in yourself, with your SSO if you use one.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
Candidate profiles are personal data your company answers for, so keep comments and notes to hiring facts. The Cotlet site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.
Is it against Comeet's terms? Account safety
use any robot, spider, scraper, or any other automated means to access, copy, collect and/or extract from the Solution (including, information); provided that the foregoing shall not apply to acts of collecting content through the API's official, documented API
Comeet Terms of Service, section 3.1 (j) (updated 29 Aug 2025, read 27 Oct 2026)
An agent in a browser is not the documented API, so the clause covers it. Section 16.4 lets Comeet suspend an account for a suspected breach of section 3 without notice. On 27 Oct 2026 the same company added terms for outside AI agents on its own MCP that put their actions on the customer and ask for human review of hiring decisions. We found no public case of a Comeet account suspended over automation (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own Recruit login, typed in by you
- One Cloud Browser with a steady IP and cookies, like your office laptop
- Rejections, Go/No-go, invitations and comments wait for your OK
- No tool exports the candidate database or downloads resumes
- If Comeet objects, we pause the Comeet tools for everyone within 24 h
Spread a big clean-up, like 200 rejections on an old position, over a few days. A burst of status changes from one user is easy to spot in the audit log.
What happens when Comeet changes?
- 12 h between tests of the Comeet position, candidate and task reads
- 24 h between tests of rejections and invitations a candidate would notice
- $0 for a call to a Comeet tool paused for a fix
Recruit changes often: on 26 Oct 2026 it began rolling out refreshed candidate profiles, select-all bulk actions and a new Settings tab, after AI follow-up emails for self-scheduling (14 Sep) and Notetaker updates (25 Sep). When a screen moves, we repair the tool and keep its name. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads the step. Candidates at Application review, with how long each has waited.
- Checks your rule. Against the profile, with the field it used, and skips anyone with an interview booked.
- Waits for your OK. Each rejection, with step and reason, waits in your Cotlet console.
- Reports back. Rejected, kept for you and skipped, by name.
| Action | Undo |
|---|---|
| Reject or withdraw | Set In progress again; cancelled interviews stay cancelled |
| No-go on a step | Same as a rejection |
| Invite to self-schedule | No; the email is out, the link lasts 5 days |
| Comment with @mention | No tool deletes it; the tagged teammate has the email |
| Add a candidate | No tool deletes it; a step email may fire |
| Tag a candidate | Yes, remove it with the same tool |
5 of the 6 write tools ask first. tag_candidate runs at once because a tag reaches nobody and one call removes it. Reads run at once. For a scheduled run you can switch the wait off per tool.
A rejection with notify left at none sends the candidate nothing. Ask for a notification step if you want to read the email before it goes.
MCP call:
{
"name": "set_candidate_status",
"arguments": {
"candidate_id": "cand_7d21a9",
"status": "rejected",
"last_step": "Application review",
"reason": "Incomplete application",
"note": "No portfolio link in the application."
}
}
REST:
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."}'
Response:
{
"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
}
A cron job or your HRIS sync can call the same tools over REST at /api/v1/comeet, with one key and one price. A call your position role cannot make returns APP_PERMISSION_DENIED and costs nothing. Every tool row above lists its REST path.
How much does the Comeet MCP server cost?
About $37 a month for one recruiter with 6 open positions, 6,440 credits. Works on Recruit Pro, Growth or Enterprise; Pro starts at $335 a month, billed yearly.
| Job | Calls | Credits |
|---|---|---|
| Interview invitations, each workday | 4 × 22 | 880 |
| Chase Go/No-go decisions, each workday | 11 × 22 | 2,420 |
| Reject stale candidates with a reason, weekly | 31 × 4 | 1,240 |
| Tag silver medalists on a closed position | 6 × 2 | 120 |
| Pipeline summary for 6 positions, weekly | 7 × 4 | 280 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 6,440 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No API add-on or Enterprise plan needed
The month is our example: 6 open positions, one invitation round and one Go/No-go check each workday, a weekly clean-up of 10 rejections and a weekly summary. Comeet publishes no typical size; Bloomberry puts 52% of its customers at 51 to 200 employees. Dollars at the $29 pack rate.
Comeet MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| StackOne Comeet connector | 26 hosted actions, MCP or API, on the Recruiting API: positions, candidates, leads, notes, logged conversations, openings. In beta. | Needs your Recruiting API key and secret; no status, step, invitation or tag. |
| Unified.to Comeet | A unified ATS API and MCP: list and get jobs, applications and candidates, create a candidate. | Built for software vendors, on the same API key and limits. |
| ComeetCo/comeet-wp-plugin | Comeet's own WordPress plugin for careers pages. 7 stars, last push 20 May 2026. | Public job postings only, no candidates. |
If your agent only needs to answer questions about the pipeline and your admin enables it, try Recruit's beta MCP first. If your own product syncs Comeet data, the Recruiting API with StackOne or Unified.to fits. If your agent should reject, invite, decide and comment in Recruit, Cotlet does that hosted.
Who runs Cotlet
Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), has run Cotlet and its other products since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Comeet tools go to contact@cotlet.dev.
Comeet API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Comeet under Integrations in the console and sign in to Recruit in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect Comeet to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Comeet once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Comeet account through Cotlet, in their phone apps too.
What can ChatGPT do in Comeet?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Comeet: reject candidates in bulk with a reason; invite candidates to pick an interview time; chase pending Go/No-go decisions. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Can I use Recruit's own MCP and Cotlet together?
Yes. Recruit's beta MCP answers questions about candidates and the pipeline; Cotlet adds the steps that change something. Both use your own permissions, so an agent with both sees nothing your role does not.
Is Comeet the same as Spark Hire Recruit?
Yes. Comeet merged with Spark Hire in June 2023 and the product is now sold as Spark Hire Recruit. The app still runs at app.comeet.co, and the terms still name Comeet. Spark Hire's video interview product is a separate app.
Does Comeet have webhooks?
One, for position updates, through the Recruiting API. Nothing fires on a new candidate or a step change. To react to new applicants, run your agent on a schedule and read the position.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HR systems use REST.
Is Cotlet affiliated with Comeet?
No. Cotlet is independent and not affiliated with Comeet or Spark Hire.
Can I use the Comeet API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
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.