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

# Manatal API and MCP server

> Yes, but only on the top plan (checked 20 Oct 2026). Manatal's Open API and its official MCP server come with Enterprise Plus, $55 to $59 per user per month, and an admin sets them up. The MCP server reads and writes candidates, jobs, organizations, contacts, notes and matches. Professional and Enterprise plans get neither.

Applicant tracking system and recruitment CRM for agencies and in-house teams: candidate profiles, jobs with a stage pipeline, organizations (clients or departments), contacts and notes.

## What is the Manatal API?

Cotlet's Manatal API exposes 13 endpoints for your own Manatal account: search candidates, get candidate, list candidate notes, search jobs, get job, list job pipeline, list drop reasons, search organizations, create candidate, add candidate note, add candidate to job, move candidate to stage and drop candidate. The search_candidates endpoint returns candidates matching a name, email, position, company or tag. Each endpoint takes simple JSON inputs like cursor, candidate_id or query and works both as an operation of the manatal_read or manatal_write MCP tool for agents and as a REST call for scripts.

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

Yes, but only on the top plan (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Manatal with 13 endpoints (8 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Manatal have an official API?

Yes, but only on the top plan (checked 20 Oct 2026). Manatal's Open API and its official MCP server come with Enterprise Plus, $55 to $59 per user per month, and an admin sets them up. The MCP server reads and writes candidates, jobs, organizations, contacts, notes and matches. Professional and Enterprise plans get neither.

| Task | Manatal official | Cotlet |
|---|---|---|
| Search candidates and read profiles | Partly: Enterprise Plus only | Yes |
| Create candidates | Partly: Enterprise Plus only | Yes |
| Add notes to candidates | Partly: Enterprise Plus only | Yes |
| Search jobs and read a job pipeline | Partly: Enterprise Plus only | Yes |
| Add a candidate to a job | Partly: Enterprise Plus only | Yes |
| Move candidates between pipeline stages | Partly: Enterprise Plus only | Yes |
| Drop candidates with a drop reason | Partly: Enterprise Plus only | Yes |
| Any of the above on Professional or Enterprise | No | Yes |

Sources: [Manatal Help: MCP Server](https://support.manatal.com/docs/mcp-server), [Manatal Help: Manatal Open API](https://support.manatal.com/docs/manatal-api), [Manatal pricing](https://www.manatal.com/pricing), [Manatal Help: Zapier triggers and actions](https://support.manatal.com/docs/zapier-triggers-and-actions)

## For AI agents

```text
Yes, but only on the top plan (checked 20 Oct 2026). Manatal's Open API and its official MCP server come with Enterprise Plus, $55 to $59 per user per month, and an admin sets them up. The MCP server reads and writes candidates, jobs, organizations, contacts, notes and matches. Professional and Enterprise plans get neither.
Cotlet provides a hosted MCP server and REST API for Manatal: 13 tools (8 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=manatal, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    manatal_read, manatal_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/manatal, each operation at its own route, e.g. POST /api/v1/manatal/candidates/{candidate_id}/note
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   search_candidates, get_candidate, list_candidate_notes, search_jobs, get_job, list_job_pipeline, list_drop_reasons, search_organizations, create_candidate, add_candidate_note, add_candidate_to_job, move_candidate_stage, drop_candidate
Confirm      create_candidate, add_candidate_note, add_candidate_to_job, move_candidate_stage, drop_candidate (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/manatal-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=manatal, requests Manatal in the Cotlet console and creates an API key there.
2. The user signs in to Manatal once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Manatal 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 Manatal 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 Manatal 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 Manatal 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 Manatal 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 Manatal's terms; Cotlet is not affiliated with Manatal.
```

## What can an AI agent do in Manatal?

Cotlet is best for recruiters on Manatal Professional or Enterprise plans who want their AI agent to log notes, move and drop candidates and fill jobs without running or fixing a server.

- **[Log interview feedback as candidate notes](https://cotlet.dev/integrations/manatal-api-mcp-server/log-interview-feedback-notes.md)**: "Find Daniel Reyes in Manatal, turn my interview comments into a short note with strengths, concerns and a recommendation, and tag Lena Fischer." → `search_candidates`, `list_candidate_notes`, `add_candidate_note`
- **[Drop stale candidates with a reason](https://cotlet.dev/integrations/manatal-api-mcp-server/drop-candidates-with-reason.md)** (runs: weekly): "In the Product Designer job, drop everyone still in Applied for more than 30 days with the reason No response, and tell me who you skipped." → `search_jobs`, `list_job_pipeline`, `list_drop_reasons`, `drop_candidate`
- **[Add a shortlist of candidates to a job](https://cotlet.dev/integrations/manatal-api-mcp-server/shortlist-candidates-for-a-job.md)**: "Find candidates tagged design with Product Designer or UX Designer as current position, skip anyone already on the Product Designer job and add the rest to it." → `get_job`, `search_candidates`, `list_job_pipeline`, `add_candidate_to_job`, `move_candidate_stage`
- **Weekly pipeline report per job** (runs: weekly): "Every Monday, list my open jobs with how many candidates sit in each stage." → `search_jobs`, `list_job_pipeline`
- **Create a candidate from an email or message**: "Create a Manatal candidate from this email signature and add them to the Product Designer job." → `create_candidate`, `add_candidate_to_job`
- **Move interviewed candidates to the next stage** (runs: daily): "Move candidates in Interview on the Product Designer job to Offer if I named them in this list." → `list_job_pipeline`, `move_candidate_stage`

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

Yes. Cotlet does not replace your automation platform: it gives it a Manatal 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 drop stale candidates 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/manatal/jobs/search. | 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/manatal/jobs/search with your API key. | cron or GitHub Actions. |

## Tools

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

### search_candidates

Candidates matching a name, email, position, company or tag. Access: read. REST: `GET /api/v1/manatal/candidates/search`. MCP: `manatal_read → search_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, email, position or company to look for. |
| `tag` | string | no | Only candidates with this candidate tag, as written in Manatal. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the candidates that match the query, with current position, company, tags and the date the profile was created. Use candidate_id in get_candidate, list_candidate_notes, add_candidate_note and add_candidate_to_job. A query that matches nobody returns an empty list. What you see follows your Manatal role.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": 48213,
      "name": "Daniel Reyes",
      "current_position": "Senior Product Designer",
      "current_company": "Brightwell",
      "email": "daniel.reyes@example.com",
      "tags": [
        "design"
      ],
      "created_at": "2026-10-02T09:14:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_candidate

One candidate profile with contact details, education and work history. Access: read. REST: `GET /api/v1/manatal/candidates/{candidate_id}`. MCP: `manatal_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | integer | yes | Candidate ID from search_candidates. |

Returns the profile as the candidate overview shows it: contact details, current position, education, work experience, tags and the owner. Resume files are not returned. A candidate you cannot open with your role fails with APP_PERMISSION_DENIED.

Example response:

```json
{
  "candidate_id": 48213,
  "name": "Daniel Reyes",
  "email": "daniel.reyes@example.com",
  "phone": "+1 555 0100",
  "current_position": "Senior Product Designer",
  "current_company": "Brightwell",
  "education": [
    {
      "school": "Riverside University",
      "degree": "BA Design"
    }
  ],
  "experience": [
    {
      "position": "Product Designer",
      "employer": "Brightwell",
      "from": "2022-03",
      "to": null
    }
  ],
  "tags": [
    "design"
  ],
  "owner": "Lena Fischer"
}
```

### list_candidate_notes

Notes on a candidate profile, with author and date. Access: read. REST: `GET /api/v1/manatal/candidate-notes`. MCP: `manatal_read → list_candidate_notes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | integer | yes | Candidate ID from search_candidates. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the notes from the candidate's Notes tab as plain text, newest first, with the author and the time. Notes on jobs and organizations are not included.

Example response:

```json
{
  "notes": [
    {
      "note_id": 9120,
      "author": "Lena Fischer",
      "body": "Phone screen done. Wants a remote role.",
      "created_at": "2026-10-05T14:02:00Z"
    }
  ],
  "next_cursor": null
}
```

### search_jobs

Jobs by title, organization or location. Access: read. REST: `GET /api/v1/manatal/jobs/search`. MCP: `manatal_read → search_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the job title or location. |
| `organization_id` | integer | no | Only jobs of this organization, from search_organizations. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns jobs with title, organization, location and creation date. Use job_id in get_job and list_job_pipeline. A job in an organization you cannot see with your role is not returned.

Example response:

```json
{
  "jobs": [
    {
      "job_id": 3107,
      "title": "Product Designer",
      "organization": "Northwind Studio",
      "location": "Austin, US",
      "created_at": "2026-09-18T08:00:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_job

One job with description, organization and its pipeline stages. Access: read. REST: `GET /api/v1/manatal/jobs/{job_id}`. MCP: `manatal_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job ID from search_jobs. |

Returns the job description, the organization and the names of the pipeline stages in the order the pipeline shows them. Stage names are the job's own, so use these exact names in move_candidate_stage and list_job_pipeline.

Example response:

```json
{
  "job_id": 3107,
  "title": "Product Designer",
  "organization": "Northwind Studio",
  "description": "Own the design of our onboarding flow.",
  "stages": [
    "Applied",
    "Interview",
    "Offer"
  ]
}
```

### list_job_pipeline

Candidates on a job, by pipeline stage, with their match IDs. Access: read. REST: `GET /api/v1/manatal/job-pipelines`. MCP: `manatal_read → list_job_pipeline`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job ID from search_jobs. |
| `stage` | string | no | Only this stage, named as in get_job. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the matches of one job: match_id, candidate and stage. stage_counts shows how many candidates sit in each stage. added_to_job_on is the date Manatal shows as Added to Job on and is filled only when an admin has turned on Candidate Matches. Dropped candidates are not included.

Example response:

```json
{
  "stage_counts": {
    "Applied": 14,
    "Interview": 3,
    "Offer": 1
  },
  "matches": [
    {
      "match_id": 55120,
      "candidate_id": 48213,
      "name": "Daniel Reyes",
      "stage": "Applied",
      "added_to_job_on": "2026-08-28"
    },
    {
      "match_id": 55131,
      "candidate_id": 48377,
      "name": "Mei Tanaka",
      "stage": "Applied",
      "added_to_job_on": "2026-10-14"
    }
  ],
  "next_cursor": null
}
```

### list_drop_reasons

The drop reasons your Manatal account offers. Access: read. REST: `GET /api/v1/manatal/drop-reasons`. MCP: `manatal_read → list_drop_reasons`.

No parameters.

Returns the reasons your company account set up for dropping a candidate. Use drop_reason_id in drop_candidate. The list is the account's own and only an admin changes it.

Example response:

```json
{
  "reasons": [
    {
      "drop_reason_id": 1,
      "name": "Not a fit"
    },
    {
      "drop_reason_id": 2,
      "name": "Withdrew"
    },
    {
      "drop_reason_id": 3,
      "name": "No response"
    }
  ]
}
```

### search_organizations

Client companies or departments by name or location. Access: read. REST: `GET /api/v1/manatal/organizations/search`. MCP: `manatal_read → search_organizations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the organization name or location. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns organizations (clients or departments) with name and location. Use organization_id as a filter in search_jobs. Organizations you cannot see with your role are not returned.

Example response:

```json
{
  "organizations": [
    {
      "organization_id": 812,
      "name": "Northwind Studio",
      "location": "Austin, US"
    }
  ],
  "next_cursor": null
}
```

### create_candidate

A new candidate profile with name, contact details and current position. Access: write, asks the user first. REST: `POST /api/v1/manatal/candidates`. MCP: `manatal_write → create_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `full_name` | string | yes | Full name as it should appear on the profile. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |
| `current_position` | string | no | Current job title. |
| `current_company` | string | no | Current employer. |

Creates a profile in your candidate database and returns its candidate_id. It does not upload a resume and does not merge with an existing profile: check search_candidates first, and Manatal's Duplicates list under Candidates shows a repeat. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": 48402,
  "name": "Mei Tanaka",
  "created_at": "2026-10-20T08:30:00Z"
}
```

### add_candidate_note

A note on a candidate profile, optionally tagging team members. Access: write, asks the user first. REST: `POST /api/v1/manatal/candidates/{candidate_id}/note`. MCP: `manatal_write → add_candidate_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | integer | yes | Candidate ID from search_candidates. |
| `body` | string | yes | Text of the note. |
| `mentions` | array | no | Names of team members to tag, as Manatal shows them. |

Adds a note to the candidate's Notes tab as plain text and returns its note_id. Each name in mentions is tagged like @ in the Manatal editor and Manatal notifies that person. A name that matches no team member fails before anything is saved. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": 9187,
  "candidate_id": 48213,
  "tagged": [
    "Lena Fischer"
  ],
  "created_at": "2026-10-20T10:12:00Z"
}
```

### add_candidate_to_job

Links a candidate to a job so they show in its pipeline. Access: write, asks the user first. REST: `POST /api/v1/manatal/jobs/{job_id}/candidates/{candidate_id}/to-job`. MCP: `manatal_write → add_candidate_to_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | integer | yes | Candidate ID from search_candidates. |
| `job_id` | integer | yes | Job ID from search_jobs. |

Adds the candidate to the job, like Add Candidate on the job page, and returns the match_id. A candidate who is already on the job fails with a clear error, and one candidate can be on several jobs. Use move_candidate_stage to place the match in a stage. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "match_id": 55140,
  "candidate_id": 48213,
  "job_id": 3107,
  "added_to_job_on": "2026-10-20"
}
```

### move_candidate_stage

Moves a candidate on a job to another pipeline stage. Access: write, asks the user first. REST: `POST /api/v1/manatal/match/{match_id}/candidate-stage/move`. MCP: `manatal_write → move_candidate_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `match_id` | integer | yes | Match ID (a candidate on one job) from list_job_pipeline. |
| `stage` | string | yes | Target stage, named as in get_job. |

Moves the match to the named stage, like dragging the card in the pipeline view. The stage must be one of the job's stages from get_job: another name fails and the error lists the stages. Any automation your account runs on a stage change runs as usual. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "match_id": 55120,
  "job_id": 3107,
  "stage": "Interview",
  "moved_at": "2026-10-20T11:05:00Z"
}
```

### drop_candidate

Drops a candidate from a job with one of the account's drop reasons. Access: write, asks the user first. REST: `POST /api/v1/manatal/match/{match_id}/candidate/drop`. MCP: `manatal_write → drop_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `match_id` | integer | yes | Match ID (a candidate on one job) from list_job_pipeline. |
| `drop_reason_id` | integer | yes | Reason ID from list_drop_reasons. |

Marks the match as dropped, like Drop in the card's three-dots menu. The candidate is no longer considered for this job; the profile and the reason stay in your database. A reason that does not exist fails and lists the valid ones. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "match_id": 55120,
  "job_id": 3107,
  "status": "dropped",
  "reason": "No response",
  "profile_kept": true
}
```

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

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

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

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

```
Find Daniel Reyes in Manatal, turn my interview comments into a short note with strengths, concerns and a recommendation, and tag Lena Fischer.
```

### Call Manatal 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/manatal 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/manatal/candidates/48213/note \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Strengths: portfolio depth, clear case-study writing. Concern: no B2B experience. Recommendation: second round.","mentions":["Lena Fischer"]}'
```

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

```
{
  "note_id": 9187,
  "candidate_id": 48213,
  "tagged": [
    "Lena Fischer"
  ],
  "created_at": "2026-10-20T10:12:00Z"
}
```

## Why use Cotlet for Manatal?

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

## Is it safe to connect Manatal to Cotlet?

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

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

## Is there a Manatal MCP server on GitHub?

On Enterprise Plus the official MCP server is the first thing to try: it is first-party and included in the plan. Below that plan Manatal offers no API or MCP, and Zapier needs API access too. Cotlet works in your own Manatal login on the plan you already have.

|  | Official MCP server | Cotlet |
|---|---|---|
| Setup | An admin enables Manatal MCP under Administration > Integrations and copies the server URL into each AI client | Sign up, sign in to Manatal once, add one MCP server or API key |
| When Manatal changes | Manatal maintains the server | Our team tests it daily and fixes it for you; failed calls are free |
| Your Manatal access | The URL is a company-wide credential with the same access as an Admin user | Your own login session in your own Cloud Browser in the EU, profile encrypted, your role applies, disabled for agents in one click |
| When access ends | The URL works until an admin turns Manatal MCP off | Your Cloud Browser keeps you signed in; if Manatal logs you out, your agent gets a link to sign in again |
| Upkeep | Nothing for you to host | Nothing to host or update |
| Where it runs | Claude, ChatGPT, Gemini CLI and Copilot Studio, 100 requests per minute | Hosted: Claude Code, Codex, Cursor, n8n and scripts over REST, also on a schedule |
| Price | Included in Enterprise Plus, $55 to $59 per user per month | Free 7-day trial, then pay-as-you-go credit packs, no subscription, on your current plan |

### 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 Manatal 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 Manatal API cost?

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

**Do I need to be technical?**

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

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

Manatal 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 Manatal plan has the API and MCP server?**

Only Enterprise Plus, $55 to $59 per user per month, lists the Open API and the ChatGPT, Claude and LLM integration. An admin sets up the MCP server, and its URL gives the same access as an Admin user. Professional and Enterprise plans have neither. Sources: Manatal pricing and the MCP Server help page, checked 20 Oct 2026.

**Do I need Enterprise Plus to use Cotlet with Manatal?**

No. Cotlet works in your own Manatal login and does not use the Open API or Manatal MCP. Your role still counts, and features locked to a plan, such as Workflow Automation or the Advanced Report Builder on higher plans, stay locked. If you use 2FA, you enter the code yourself when you sign in to the Cloud Browser.

**What can it not do?**

It does not upload or read resume files, delete or merge candidates, email candidates, publish jobs to job boards or run Manatal's AI Interviewer. Notes are plain text. Drop reasons, tags and pipeline stages are only read: an admin edits them in Manatal.

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

No. Every call to create_candidate, add_candidate_note, add_candidate_to_job, move_candidate_stage or drop_candidate waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Manatal 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/manatal 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.