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

# Loxo API and MCP server

> Yes, Loxo has an Open API, but it is a paid feature: Loxo Support turns on the Settings > API Keys page for your account, and only account admins can use it (checked 22 Oct 2026). Loxo has no official MCP server, and its API reference has no endpoints for reports or for sending email.

Recruiting platform for agencies and in-house teams: jobs with candidate pipelines, a People and Companies database, outreach, deals and reporting in one account.

## What is the Loxo API?

Cotlet's Loxo API exposes 12 endpoints for your own Loxo account: list jobs, read a job pipeline, list workflow stages and triggers, search people, get a person, read the activity report, create a person, add a person to a job, move a candidate to a stage, log candidate activity, add people to a list and email candidates from a job. The list_jobs endpoint returns list jobs from the Jobs page, optionally by keyword. Each endpoint takes simple JSON inputs like job_id, stage or person_id and works both as an operation of the loxo_read or loxo_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-20

Yes, Loxo has an Open API, but it is a paid feature: Loxo Support turns on the Settings > API Keys page for your account, and only account admins can use it (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Loxo with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Loxo have an official API?

Yes, Loxo has an Open API, but it is a paid feature: Loxo Support turns on the Settings > API Keys page for your account, and only account admins can use it (checked 22 Oct 2026). Loxo has no official MCP server, and its API reference has no endpoints for reports or for sending email.

| Task | Loxo official | Cotlet |
|---|---|---|
| List jobs | Yes: Paid API only | Yes |
| Read a job pipeline | Yes: Paid API only | Yes |
| Search and read people | Yes: Paid API only; Loxo Source profiles return only person_name, person_id and custom fields | Yes |
| Create a person | Yes: Paid API only | Yes |
| Add a candidate to a job | Partly: The apply endpoint needs name, email, phone and a resume file | Yes |
| Log activity and move a candidate | Partly: The reference has person_events and candidates endpoints; the help center does not say they move a stage like the app does | Yes |
| Add people to a list | Yes: Paid API only | Yes |
| Read the Activity Report | No | Yes |
| Email candidates from a job pipeline | No: The reference has an SMS endpoint and email tracking, no email send | Yes |

Sources: [Loxo Help: Loxo's Open API](https://help.loxo.co/en/articles/446640-loxo-s-open-api), [Loxo API reference](https://loxo.readme.io/reference/loxo-api), [Loxo Help: Reporting Questions](https://help.loxo.co/en/articles/9027502-reporting-questions)

## For AI agents

```text
Yes, Loxo has an Open API, but it is a paid feature: Loxo Support turns on the Settings > API Keys page for your account, and only account admins can use it (checked 22 Oct 2026). Loxo has no official MCP server, and its API reference has no endpoints for reports or for sending email.
Cotlet provides a hosted MCP server and REST API for Loxo: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=loxo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    loxo_read, loxo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/loxo, each operation at its own route, e.g. POST /api/v1/loxo/jobs/{job_id}/activities
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_jobs, get_job_pipeline, list_workflow_stages, search_people, get_person, list_activity, create_person, add_person_to_job, move_candidate, log_activity, add_to_list, send_email
Confirm      add_person_to_job, move_candidate, log_activity, send_email (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/loxo-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=loxo, requests Loxo in the Cotlet console and creates an API key there.
2. The user signs in to Loxo once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Loxo 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 Loxo server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Loxo MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Loxo 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 Loxo 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 Loxo 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 Loxo's terms; Cotlet is not affiliated with Loxo.
```

## What can an AI agent do in Loxo?

Cotlet is best for recruiters and agency owners who run Loxo without the paid API and want their AI agent to log activity, move candidates, email a stage and report on activity without running or fixing a server.

- **[Log interview outcomes and move candidates](https://cotlet.dev/integrations/loxo-api-mcp-server/log-interview-outcomes.md)** (runs: daily): "On the Senior Data Engineer job, log "1st Interview" for Priya Nair and Tom Becker with my notes, then show me where each one landed." → `list_workflow_stages`, `get_job_pipeline`, `log_activity`
- **[Weekly recruiting activity report](https://cotlet.dev/integrations/loxo-api-mcp-server/weekly-recruiting-activity-report.md)** (runs: weekly): "Every Monday, summarize last week's Loxo activity by type and by recruiter, and compare it with the week before." → `list_activity`, `list_jobs`
- **[Email every candidate in a pipeline stage](https://cotlet.dev/integrations/loxo-api-mcp-server/email-candidates-in-a-pipeline-stage.md)**: "Email everyone in the Shortlist stage of the Senior Data Engineer job: the client call moved to Thursday at 3 pm. Show me the draft first." → `get_job_pipeline`, `get_person`, `send_email`
- **Copy a shortlist to another job**: "Copy everyone in the Shortlist stage of the Senior Data Engineer job into the Longlist of the Data Platform Lead job." → `get_job_pipeline`, `list_jobs`, `add_person_to_job`
- **Add new leads to Loxo** (runs: weekly): "Add the people from this list to Loxo, skip anyone already there, and put them on the Data leads list." → `search_people`, `create_person`, `add_to_list`
- **Move stalled candidates forward**: "Find candidates in Interviewing with no activity for 14 days and move the ones I name to the stage I pick." → `get_job_pipeline`, `get_person`, `move_candidate`

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

Yes. Cotlet does not replace your automation platform: it gives it a Loxo 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 log interview outcomes and move candidates, 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/loxo/workflow-stages. | 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/loxo/workflow-stages 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 Loxo.

### list_jobs

List jobs from the Jobs page, optionally by keyword. Access: read. REST: `GET /api/v1/loxo/jobs`. MCP: `loxo_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Keyword to search jobs by, for example a title or hiring company. |
| `cursor` | string | no | next_cursor from the previous page. |

Returns job_id, title, hiring company and location for each job the signed-in account can see, in the order the Jobs page shows them. Results come in pages; follow next_cursor until it is null. A confidential job shows only to the Group it is visible to.

Example response:

```json
{
  "jobs": [
    {
      "job_id": 2481530,
      "title": "Senior Data Engineer",
      "company": "Northwind Analytics",
      "location": "Austin, TX"
    },
    {
      "job_id": 2481544,
      "title": "VP of Sales",
      "company": "Brightpath Health",
      "location": "Remote"
    },
    {
      "job_id": 2481562,
      "title": "Product Designer",
      "company": "Kestrel Labs",
      "location": "London, UK"
    }
  ],
  "next_cursor": null
}
```

### get_job_pipeline

Read the stages of one job and the candidates in each. Access: read. REST: `GET /api/v1/loxo/jobs/{job_id}/pipeline`. MCP: `loxo_read → get_job_pipeline`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id from list_jobs. |
| `stage` | string | no | Stage name from list_workflow_stages. Without it, every stage is returned. |

Returns the job title, the total number of candidates in the pipeline and, per stage, its count and its candidates with person_id and name. Stages come in the order of your workflow. total_candidates covers the whole pipeline even when stage limits the stages returned.

Example response:

```json
{
  "job_id": 2481530,
  "title": "Senior Data Engineer",
  "total_candidates": 14,
  "stages": [
    {
      "stage": "Shortlist",
      "count": 3,
      "candidates": [
        {
          "person_id": 48211077,
          "name": "Priya Nair"
        },
        {
          "person_id": 48211102,
          "name": "Tom Becker"
        },
        {
          "person_id": 48211130,
          "name": "Lena Ortiz"
        }
      ]
    }
  ]
}
```

### list_workflow_stages

List the stages of your Loxo workflow and the names of its progression triggers. Access: read. REST: `GET /api/v1/loxo/workflow-stages`. MCP: `loxo_read → list_workflow_stages`.

No parameters.

Returns the stages in pipeline order, with a flag for stages set as an interview stage, and the progression trigger names an admin defined under Settings > Workflow. Call it first so that stage and trigger names in other calls match your account exactly.

Example response:

```json
{
  "stages": [
    {
      "name": "Longlist",
      "interview": false
    },
    {
      "name": "Shortlist",
      "interview": false
    },
    {
      "name": "Interviewing",
      "interview": true
    },
    {
      "name": "Hired",
      "interview": false
    }
  ],
  "progression_triggers": [
    "Phone Screen",
    "1st Interview",
    "Onsite 1"
  ]
}
```

### search_people

Search the People page by keyword. Access: read. REST: `GET /api/v1/loxo/peoples/search`. MCP: `loxo_read → search_people`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Keyword, for example a name or an email address. |
| `cursor` | string | no | next_cursor from the previous page. |

Returns person_id, name and primary email for each match, in the order of the People page, in pages. Use it before create_person to avoid a duplicate. It searches your own database only, not Loxo Source.

Example response:

```json
{
  "people": [
    {
      "person_id": 48211077,
      "name": "Priya Nair",
      "primary_email": "priya.nair@example.com"
    },
    {
      "person_id": 48211102,
      "name": "Tom Becker",
      "primary_email": "tom.becker@example.com"
    }
  ],
  "next_cursor": null
}
```

### get_person

Read one profile: emails, jobs and the Activity Feed. Access: read. REST: `GET /api/v1/loxo/persons/{person_id}`. MCP: `loxo_read → get_person`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `person_id` | integer | yes | Person id from search_people or get_job_pipeline. |

Returns the name, every email with its type and which one is primary, the jobs the person is in with their stage, the lists they are on and the Activity Feed, newest first. A trigger logged from the activity drop-down shows as two events. Documents and resume files are not returned.

Example response:

```json
{
  "person_id": 48211077,
  "name": "Priya Nair",
  "emails": [
    {
      "type": "Personal",
      "address": "priya.nair@example.com",
      "primary": true
    }
  ],
  "jobs": [
    {
      "job_id": 2481530,
      "title": "Senior Data Engineer",
      "stage": "Shortlist"
    }
  ],
  "lists": [
    "Data leads"
  ],
  "activity": [
    {
      "event": "Outgoing Call",
      "logged_at": "2026-10-19T14:05:00Z",
      "by": "Dana Reyes"
    },
    {
      "event": "Moved to Shortlist",
      "logged_at": "2026-10-17T09:30:00Z",
      "by": "Dana Reyes"
    }
  ]
}
```

### list_activity

Read logged activity for a date range, with totals per type and per user. Access: read. REST: `GET /api/v1/loxo/activities`. MCP: `loxo_read → list_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | yes | First day, YYYY-MM-DD, matched against Date Logged. |
| `date_to` | string | yes | Last day, YYYY-MM-DD. |
| `activity_type` | string | no | Activity type, for example Outgoing Call or Submission. Without it, all types. |
| `user` | string | no | Name of the user who logged the activity. |
| `job_id` | integer | no | Only activity on this job. |
| `stage` | string | no | Only activity in this stage. |
| `cursor` | string | no | next_cursor from the previous page. |

Returns the total, the count per activity type and the count per user over the whole range and filters, then the activity rows newest first in pages. A drag between stages counts as "Moved to ..." and a trigger as its own event. The account needs access to Reports; without it the call fails with APP_PERMISSION_DENIED.

Example response:

```json
{
  "date_from": "2026-10-12",
  "date_to": "2026-10-18",
  "total": 48,
  "by_type": [
    {
      "activity_type": "Outgoing Call",
      "count": 21
    },
    {
      "activity_type": "Moved to Interviewing",
      "count": 12
    },
    {
      "activity_type": "Scheduled Interview",
      "count": 9
    },
    {
      "activity_type": "Submission",
      "count": 6
    }
  ],
  "by_user": [
    {
      "user": "Dana Reyes",
      "count": 30
    },
    {
      "user": "Sam Okafor",
      "count": 18
    }
  ],
  "activities": [
    {
      "logged_at": "2026-10-18T16:40:00Z",
      "activity_type": "Submission",
      "user": "Dana Reyes",
      "person": "Tom Becker",
      "job_id": 2481530
    },
    {
      "logged_at": "2026-10-18T11:02:00Z",
      "activity_type": "Outgoing Call",
      "user": "Sam Okafor",
      "person": "Lena Ortiz",
      "job_id": 2481544
    }
  ],
  "next_cursor": "c2"
}
```

### create_person

Add one person to your Loxo database. Access: write. REST: `POST /api/v1/loxo/persons`. MCP: `loxo_write → create_person`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Full name. |
| `email` | string | no | Email address. |
| `email_type` | string | no | Email type, for example Personal or Work. |
| `phone` | string | no | Phone number. |

Creates the profile as the Add People form does and returns its person_id. Required fields that an admin set for new people apply, and a missing one fails the call with its name. Loxo can flag a duplicate after creation, so run search_people first. It creates no profile from a resume file. It reaches no one, so it does not wait for your OK by default.

Example response:

```json
{
  "person_id": 48211190,
  "name": "Marcus Webb",
  "created": true
}
```

### add_person_to_job

Put a person into a job pipeline at a stage. Access: write, asks the user first. REST: `POST /api/v1/loxo/jobs/{job_id}/persons/{person_id}/to-job`. MCP: `loxo_write → add_person_to_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `person_id` | integer | yes | Person id. |
| `job_id` | integer | yes | Job id from list_jobs. |
| `stage` | string | yes | Stage name from list_workflow_stages. |

Adds the person to the job in that stage, as "Add to Another Job" does. The person stays in the pipelines they are already in. A stage with an Email Automation can start sending its emails to the new candidate. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "person_id": 48211190,
  "job_id": 2481562,
  "stage": "Longlist",
  "added": true
}
```

### move_candidate

Move a candidate to another stage of a job. Access: write, asks the user first. REST: `POST /api/v1/loxo/jobs/{job_id}/candidate/move`. MCP: `loxo_write → move_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id. |
| `person_id` | integer | yes | Person id. |
| `stage` | string | yes | Target stage name from list_workflow_stages. |

Moves the candidate as a drag and drop does, so the profile and reports show "Moved to {stage}" and no progression trigger. Use log_activity when the trigger should count. A stage with an Email Automation can start sending its emails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": 2481530,
  "person_id": 48211102,
  "stage": "Interviewing",
  "events": [
    "Moved to Interviewing"
  ]
}
```

### log_activity

Log a progression trigger on a candidate in a job, with an optional note. Access: write, asks the user first. REST: `POST /api/v1/loxo/jobs/{job_id}/activities`. MCP: `loxo_write → log_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id. |
| `person_id` | integer | yes | Person id. |
| `activity` | string | yes | Progression trigger name from list_workflow_stages, for example 1st Interview. |
| `note` | string | no | Text saved with the activity. |

Logs the trigger as the activity drop-down on the profile does. Loxo adds two events, "Moved to {stage}" and the trigger, so the candidate also changes stage. A trigger name your workflow does not have fails the call. A stage with an Email Automation can start sending its emails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": 2481530,
  "person_id": 48211077,
  "stage": "Interviewing",
  "events": [
    "Moved to Interviewing",
    "1st Interview"
  ],
  "note": "Strong on Spark, wants a remote role."
}
```

### add_to_list

Add people to a list on the People page. Access: write. REST: `POST /api/v1/loxo/lists`. MCP: `loxo_write → add_to_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list` | string | yes | Title of an existing list. A name that does not exist fails and the error lists your lists. |
| `person_ids` | array | yes | Person ids to add. |

Adds the people to the list. Lists are static groups, and anyone with access to a list can add or remove records. It reaches no one and a person can be removed from the list in Loxo, so it does not wait for your OK by default.

Example response:

```json
{
  "list": "Data leads",
  "added": 1
}
```

### send_email

Send one email to several candidates of a job, each as an individual message. Access: write, asks the user first. REST: `POST /api/v1/loxo/jobs/{job_id}/emails`. MCP: `loxo_write → send_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id, so Loxo links the email to the job. |
| `person_ids` | array | yes | Person ids of the recipients. |
| `subject` | string | yes | Subject line. |
| `body` | string | yes | Plain-text message, sent as written to every recipient. |
| `email_type` | string | no | Email type to send to, for example Personal or Work. Default: the primary email, the first listed on the record. |

Sends from the job pipeline, as the Email button does, so each email is linked to the job. Loxo sends every recipient an individual message, so they do not see each other. A person with no address of that type is skipped and listed in the response. It sends text only: no merge tags, attachments or SMS. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": 2481530,
  "sent": 3,
  "email_type": "Primary",
  "recipients": [
    {
      "person_id": 48211077,
      "name": "Priya Nair",
      "status": "sent"
    },
    {
      "person_id": 48211102,
      "name": "Tom Becker",
      "status": "sent"
    },
    {
      "person_id": 48211130,
      "name": "Lena Ortiz",
      "status": "sent"
    }
  ],
  "skipped": []
}
```

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

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

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

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

```
On the Senior Data Engineer job, log "1st Interview" for Priya Nair and Tom Becker with my notes, then show me where each one landed.
```

### Call Loxo 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/loxo 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/loxo/jobs/2481530/activities \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id":48211102,"activity":"1st Interview","note":"Good system design answers."}'
```

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

```
{
  "job_id": 2481530,
  "person_id": 48211102,
  "stage": "Interviewing",
  "events": [
    "Moved to Interviewing",
    "1st Interview"
  ],
  "note": "Good system design answers."
}
```

## Why use Cotlet for Loxo?

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

## Is it safe to connect Loxo to Cotlet?

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

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

## Is there a Loxo MCP server on GitHub?

Yes. Community Loxo MCP servers exist on GitHub, usually maintained by one person. They call the Open API, so you need the paid API enabled first, then install and run the server yourself and fix it when it breaks. Cotlet hosts the same kind of server for you and our team keeps it working. It also covers what the API does not: reports and emailing a stage.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask Loxo Support to enable API keys, create a key, install the server, add it to each MCP client | Sign up, sign in to Loxo once, add one MCP server or API key; no Loxo API add-on |
| When Loxo changes | You or the maintainer update the server | Our team tests it daily and fixes it for you; failed calls are free |
| Your Loxo access | An API key in a file on your computer, readable by any program you run | Your signed-in session in your own Cloud Browser in the EU, encrypted, only for the apps you enable, disabled for agents in one click |
| When access ends | Calls fail until you create a new key | Your Cloud Browser keeps you signed in; if Loxo logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, plus the paid Loxo API and 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 Loxo 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 Loxo API cost?

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

**Do I need to be technical?**

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

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

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

**Do I need Loxo's paid API to use Cotlet?**

No. Cotlet works in your own signed-in Loxo session, so you do not need Loxo Support to enable API keys. Your role still counts: Loxo lets only account admins create and edit reports, and other users need a Group permission and a shared dashboard, so list_activity fails with APP_PERMISSION_DENIED without Reports access.

**Can Cotlet set up Email Automations or Outreach Campaigns?**

No. send_email sends a one-off email from a job pipeline. Email Automations and Outreach Campaigns are set up in Loxo under Settings > Email Automation and in the Outreach section. Moving a candidate into a stage that has an automation can start it, which is why moves and logs wait for your OK by default.

**Can Cotlet notify me when a candidate or job changes?**

No, Cotlet answers calls and does not push events. Loxo's own webhooks cover item types such as candidate, job, person and placement with create, update and destroy actions, but they are part of the paid API.

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

No. Every call to add_person_to_job, move_candidate, log_activity or send_email waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_person, add_to_list runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Loxo 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/loxo 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.