Vincere MCP Server

Listas de seleção, LiveLists, etapas do pipeline, notas e tarefas no Vincere.

Servidor MCP hospedado

npx add-mcp 'https://cotlet.dev/mcp/v1/vincere'

Instala no Claude Code, Codex, Cursor e outros

Documentação

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Vincere API and MCP server: Let your AI agent move your Vincere pipeline along.

Vincere has no MCP server (checked 27 Oct 2026). Its REST API is documented in public, but Vincere Support issues keys only to partners with a formal agreement, and the API has no call that emails a LiveList or a job list. Cotlet runs 13 Vincere tools hosted, over MCP for agents and REST for scripts, in the login your recruiters already have.

Shortlists, LiveLists, pipeline stages, notes and tasks in Vincere. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Vincere. Vincere is a trademark of its owner. If Vincere's own integrations cover what you need, use them first.

What can you automate in Vincere?

  • Shortlist a talent pool for a new job
  • Send the shortlist to the client as a LiveList
  • Log calls as comments with the right Action
  • Add follow-up tasks with due dates
  • Send new jobs to a talent pool
  • Count each job's pipeline on Monday

Does Vincere have an MCP server or an API?

  • With a partner key, the API reaches shortlists, stage moves, comments and tasks, at 10 requests a second and 50,000 a day. Its spec was last updated on 14 Sep 2026.
  • Zapier has 9 triggers and 6 actions, and Zapier MCP hands the same actions to an agent: a new contact, VinnyChat messages, GDPR details. None shortlists, moves a stage or logs a comment.
  • Copilot, the assistant in every Access Evo Smart Pack from £25 an agency a month, answers inside Vincere. An outside agent cannot call it.
What you needVincere API (partner key)ZapierCotlet
Read jobs, candidates and the pipelineYesNew records onlyYes
Shortlist and move stagesYesNoYes, after your OK
Comments and tasksYesNoYes, after your OK
Email a LiveList or a job listNo endpointNoYes, after your OK
What you need firstA partner agreementA key from Vincere SupportYour own Vincere login

Checked 27 Oct 2026. Sources: Vincere Help: Understanding and requesting API keys, Vincere Help: Set up and use the Zapier integration, Vincere on Zapier: triggers and actions, Vincere Help: Candidate Actions, Vincere API reference, Access Vincere Evo pricing

How does Cotlet connect to Vincere?

  1. Sign in to Vincere. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

Your Vincere password never reaches us, and nothing the agent writes in Vincere, from a comment to a LiveList, is saved before you approve it.

Connect Vincere 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.

  1. Sign in to Vincere in a Cloud Browser. Make a Cotlet account, open Vincere in its Cloud Browser and sign in on your agency's own vincere.io address. Then press Enable for agents.
  2. Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 where your agent lists its MCP servers or connectors.
  3. Let the agent in. Claude and ChatGPT open a Cotlet sign-in window. Cursor, Codex, n8n and scripts send an API key made in the console.

One address, https://cotlet.dev/mcp/v1, carries Vincere and every other app in your Cotlet account. Turned Vincere on after connecting? Reload the connector and the 13 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: vincere_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: vincere_write

How to use the Vincere REST API

Create your Cotlet API key

Create a Cotlet API key with access to Vincere and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Vincere in Cotlet and enable it for agents. Account access: Your own Vincere user account on your tenant URL (shortlisting needs a user with the permission for it).

Make your first Vincere API request

REST:

curl "https://cotlet.dev/api/v1/vincere/jobs?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read jobs 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": "vincere",
  "tool": "list_jobs",
  "result": {
    "jobs": [
      {
        "job_id": "1042",
        "title": "Senior Java Developer",
        "company": "Brightline Tech",
        "contact": "Alex Reed",
        "owner": "Dana Fox",
        "status": "open",
        "job_type": "Permanent",
        "sourcing_close_date": "2026-11-30"
      },
      {
        "job_id": "1047",
        "title": "Data Engineer",
        "company": "Northwind Systems",
        "contact": "Sam Okafor",
        "owner": "Dana Fox",
        "status": "open",
        "job_type": "Contract",
        "sourcing_close_date": "2026-12-15"
      }
    ],
    "next_cursor": null
  }
}

Lists jobs as Vincere shows them in the Jobs table, one page at a time; pass next_cursor back as cursor for the next page. status filters open or closed jobs. query matches the job title or company name. Use job_id from here in the other tools.

Only open jobs can take new shortlists.

limit: How many jobs to return on one page.

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.

Vincere workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestOne candidate with title, company, owner, Talent Pools and applications with their stage. Use get_candidate in your configured team report.
MakeHTTP > Make a requestCandidates on one job with their pipeline stage. Use list_job_applications in your configured team report.
Python or Node.jsREST APIComments, meetings and tasks logged on a candidate or a job, with who added them and when. Use list_activities 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 Vincere; 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.

Vincere API endpoints and MCP tools

Jobs and pipeline

Stages run from Applications to Placed. A candidate only moves forward, an offer can wait for approval in Vincere, and placing stays in the app.

  • List jobs (list_jobs, read): Jobs of your agency with company, contact, owner, status and sourcing dates.
  • Get job (get_job, read): One job with its details, public and internal description and brief notes.
  • List job applications (list_job_applications, read): Candidates on one job with their pipeline stage.
  • Move application stage (move_application_stage, write, asks first): Move a candidate to the next stage of a job without sending an email.

Candidates and shortlists

Up to 300 candidates per shortlist call, to open jobs only. A shortlist sends nothing to the candidate or the client.

  • List candidates (list_candidates, read): Candidates of your agency or of one Talent Pool, with title, company and owner.
  • Get candidate (get_candidate, read): One candidate with title, company, owner, Talent Pools and applications with their stage.
  • Shortlist candidates (shortlist_candidates, write, asks first): Shortlist candidates to an open job.

LiveLists and job lists

The only two tools that send email. Vincere caps one email action at 100 recipients, and a job list at 10 jobs.

  • Send candidates to a client (send_candidates_to_client, write, asks first): Email candidates to the client as a LiveList for a job and move them to Sent.
  • Send job list to candidates (send_job_list_to_candidates, write, asks first): Email a list of jobs to candidates, who can accept or decline each role.

Comments, tasks and activity

A comment takes its Action exactly as activated in Goal Console. A task synced to your calendar cannot be taken back out.

  • List activities (list_activities, read): Comments, meetings and tasks logged on a candidate or a job, with who added them and when.
  • Add comment (add_comment, write, asks first): Log a comment on a candidate with an Action, such as a connected call, and notes.
  • List tasks (list_tasks, read): Vincere tasks assigned to you, created by you or followed by you, with due date and status.
  • Add task (add_task, write, asks first): Create a Vincere task with subject, type, due date and assignee.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/vincere-api-mcp-server#tools

Who can see my Vincere session, and how do I revoke it?

  • What we store. Your signed-in Vincere profile for your tenant, AES-256-GCM, in Finland. No password.
  • What your agent gets. 13 Vincere tools. No cookie, no tenant login.
  • What the session sees. The candidates, jobs and Talent Pools your Vincere user may open under your agency's settings.
  • What no tool touches. Placements, timesheets, pay and bill, record deletes and Admin Settings.
  • If Vincere signs you out. We email you a link and you sign in again yourself.
  • How to cut access. Turn agents off for Vincere, reset the browser or revoke the key; calls fail from then on.

Candidate records are personal data under GDPR. A tool reads only the fields it returns, and our call log keeps the time, tool and status, not the records. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Reads the shortlist. Shortlisted candidates on the job, minus anyone already at Sent.
  2. Checks each profile. Flags a missing job title or CV before the client sees it.
  3. Waits for your OK. Names, recipient and shown or hidden names wait in your Cotlet console.
  4. Sends and confirms. One LiveList, then a fresh read of the Sent stage.
ActionUndo
Shortlist candidatesRemove Application in Vincere; no tool does it
Send a LiveListNo, the client already has the email
Send a job listNo, candidates answer on their own page
Move a stageNo, Vincere moves candidates forward only
Add a comment or a taskNo delete tool; a synced task stays in your calendar

All 6 write tools ask first, the two senders included, because a LiveList reaches a client and a job list can reach 100 candidates. The 7 reads run at once. You can switch the wait off per tool, for example for comments on a nightly run.

A candidate the client rejects stays on the LiveList with a rejected status. To take someone off it completely, delete the application from the job in Vincere.

MCP call:

{
  "name": "shortlist_candidates",
  "arguments": {
    "job_id": "1042",
    "candidate_ids": [
      "88214",
      "88230"
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/vincere/jobs/1042/candidates/shortlist \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"candidate_ids":["88214","88230"]}'

Response:

{
  "job_id": "1042",
  "shortlisted": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "stage": "shortlisted"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "stage": "shortlisted"
    }
  ],
  "skipped": []
}

Scripts and n8n flows reach the same tools over REST at /api/v1/vincere, with the same key and price; a pipeline count mailed to each consultant on Monday is a typical one. A call outside your Vincere permissions returns an error and costs nothing. Each tool row above shows its REST path.

How much does the Vincere MCP server cost?

About $60 a month for an agency of 6 recruiters with about 12 open jobs, 10,420 credits. Vincere itself starts at £69 a user a month on a 12-month contract.

JobCallsCredits
Log a call as a comment and a task4 × 1204,800
Shortlist a talent pool for a new job14 × 101,400
Friday LiveList for one job6 × 241,440
Monday pipeline count, 12 jobs13 × 4520
New jobs to a talent pool, weekly4 × 4160
Move a candidate to interview2 × 30600
Cloud Browser, 30 days1,500
Total10,420
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser

The month is our example: 6 recruiters log about 120 calls, shortlist for 10 new jobs, send 24 LiveLists and count 12 open jobs every Monday. Vincere publishes no activity figures; it counts 22,000+ recruiters, and most of its reviewers work at small agencies. Dollars at the $29 pack rate.

Vincere MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Zapier MCP for VincereThe 6 Zapier actions as agent tools: a new contact, VinnyChat messages, GDPR details, unsubscribe.No candidate, job, stage or comment writes; a Zapier plan and a key from Vincere Support.
automindz-solutions/hyreflow-pluginsHyreflow's hosted recruiting MCP; its Vincere playbook reads and writes candidates and searches jobs, companies and contacts. MIT, 1 star, last push 27 Oct 2026.Needs a Client ID and API key from Vincere; no shortlists, LiveLists or tasks.
formacv-mcpFormaCV's official MCP with 8 tools; push_to_ats saves a branded CV on a Vincere candidate. MIT, 36 stars, last push 6 May 2026.CVs only; FormaCV sets up the Vincere link and charges $0.99 a CV.
Tenzo AI, Skima AI and other partnersScreening and scoring that write results back to the candidate record.Their own product on a partner key, not your agent.

If your agency is a Vincere partner, or gets a key for its own developers, a server on the API is the cleaner route for reads, shortlists and comments. If new candidates or placements only need to reach another app, Zapier does that. If your agent should shortlist, send LiveLists and log calls without a key, Cotlet does it in your login.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and active since 2019, runs Cotlet. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Vincere tools go to contact@cotlet.dev.

Vincere API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Vincere under Integrations in the console and sign in to Vincere in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect Vincere to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Vincere 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 Vincere account through Cotlet, in their phone apps too.

What can ChatGPT do in Vincere?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Vincere: shortlist candidates for a job; send a candidate shortlist to a client; log call notes and follow-up tasks. You ask in plain words, and anything that reaches other people waits for your OK first.

Which Vincere role does my account need?

Cotlet works in your own Vincere login and sees what you see. Shortlisting needs a user account with the permission for it, and a company that is compliant, according to Vincere's Help Center, which names no role. Logging a call as a comment needs the call Action activated in Settings > Goal Console, and an admin with access to Settings and Goal Console does that.

Which tools send email?

Two do: send_candidates_to_client emails the client a LiveList, and send_job_list_to_candidates emails candidates a job list. Vincere limits an email action to 100 recipients, and a job-list send to 10 jobs and 100 candidates. shortlist_candidates and move_application_stage send nothing. Each write waits for your OK by default.

What does it not cover?

Placements stay in Vincere: Place opens the placement details page and Vincere runs compliance checks on it. A candidate cannot be moved back a stage, merged, archived or removed from a job through these tools, and Float to Contact for a role with no open job is not built. Comments and tasks cannot be deleted through Cotlet. Vincere also limits a candidate to 1,000 position associations.

Can my own developers get a Vincere API key?

Ask Vincere Support with your tenant URL, an integration name and an HTTPS callback URL. Vincere's help center says keys go only to partners with a formal agreement, so the answer depends on your contract. A key gives you the documented API at 10 requests a second, without the LiveList and job-list sends.

Does Vincere have webhooks?

Yes, in the API, for key holders. Without a key, Zapier's 9 triggers fire on new candidates, jobs, placements and contacts. To react to anything else, run your agent on a schedule and read the jobs and the pipeline.

Is the MCP server different from the REST API?

Only in the way you call it. Both carry the same 13 tools, inputs and answers, with one key and one price. Agents use MCP; scripts and cron jobs use REST.

Is Cotlet affiliated with Vincere?

No. Cotlet is independent and not affiliated with Vincere or The Access Group.

Can I use the Vincere 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.