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

# Agile CRM API and MCP server

> Yes, Agile CRM has a REST API on all plans, with a daily call cap by plan and no official MCP server (checked 22 Oct 2026). It covers contacts, companies, deals, tasks, notes, events, tracks and enrolling a contact in a campaign, but not campaign reports or bulk actions.

Small-business CRM with contacts and companies, deals in tracks and milestones, tasks, a calendar, email campaigns and a help desk.

## What is the Agile CRM API?

Cotlet's Agile CRM API exposes 11 endpoints for your own Agile CRM account: list contacts, get contact, list deals, list tasks, list campaigns, get campaign report, add contact tags, add note, create task, move deal to milestone and add contacts to campaign. The list_contacts endpoint returns lists contacts or companies, filtered by search text, tag or owner. Each endpoint takes simple JSON inputs like owner_email, cursor or type and works both as an operation of the agile_crm_read or agile_crm_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-21

Yes, Agile CRM has a REST API on all plans, with a daily call cap by plan and no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Agile CRM with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Agile CRM have an official API?

Yes, Agile CRM has a REST API on all plans, with a daily call cap by plan and no official MCP server (checked 22 Oct 2026). It covers contacts, companies, deals, tasks, notes, events, tracks and enrolling a contact in a campaign, but not campaign reports or bulk actions.

| Task | Agile CRM official | Cotlet |
|---|---|---|
| List and search contacts | Yes: GET dev/api/contacts and search endpoints | Yes |
| Add tags to contacts | Yes | Yes |
| Add notes and create tasks | Yes | Yes |
| Move a deal between milestones | Yes: Partial deal update | Yes |
| Add contacts to a campaign | Partly: One contact per call by email | Yes |
| Read campaign reports (opens, clicks, bounces, unsubscribes) | No: The REST reference lists campaigns but returns no metrics | Yes |
| Run a bulk action on a selection of contacts | No: Bulk delete of deals is the only bulk endpoint | Yes |
| Work past the daily API call cap | No: Free 500, Starter 5,000, Regular 10,000, Enterprise 25,000 per day, per Agile's product update of 22 Jun 2016 | Yes |

Sources: [Agile CRM REST API reference (GitHub)](https://github.com/agilecrm/rest-api), [Agile CRM Product Updates](https://www.agilecrm.com/product-updates), [Agile CRM Help: Bulk Actions](https://www.agilecrm.com/sales-enablement/bulk-actions), [Agile CRM on Zapier](https://zapier.com/apps/agile-crm/integrations)

## For AI agents

```text
Yes, Agile CRM has a REST API on all plans, with a daily call cap by plan and no official MCP server (checked 22 Oct 2026). It covers contacts, companies, deals, tasks, notes, events, tracks and enrolling a contact in a campaign, but not campaign reports or bulk actions.
Cotlet provides a hosted MCP server and REST API for Agile CRM: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=agile-crm, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    agile_crm_read, agile_crm_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/agile-crm, each operation at its own route, e.g. POST /api/v1/agile-crm/contacts/{contact_id}/notes
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_contacts, get_contact, list_deals, list_tasks, list_campaigns, get_campaign_report, add_contact_tags, add_note, create_task, move_deal, add_contacts_to_campaign
Confirm      add_contacts_to_campaign (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/agile-crm-api-mcp-server.md

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

## What can an AI agent do in Agile CRM?

Cotlet is best for Agile CRM teams who want campaign reports read, tagged contacts added to campaigns and deals kept current by an AI agent without running or fixing a server.

- **[Weekly campaign performance report](https://cotlet.dev/integrations/agile-crm-api-mcp-server/weekly-campaign-report.md)** (runs: weekly): "Every Monday, read the report of each Agile CRM campaign and send me opens, clicks, bounces, unsubscribes and spam complaints, flagging any campaign with more than 10 unsubscribes or a spam complaint." → `list_campaigns`, `get_campaign_report`
- **[Add tagged contacts to a campaign](https://cotlet.dev/integrations/agile-crm-api-mcp-server/enroll-tagged-contacts-in-campaign.md)** (runs: daily): "Find Agile CRM contacts tagged webinar_oct, add the tag nurture, and add them to the Onboarding series campaign. Skip anyone already tagged nurture." → `list_contacts`, `add_contact_tags`, `add_contacts_to_campaign`
- **Chase stale deals** (runs: daily): "List my deals in the Proposal milestone with a close date in the past, add a note with what is overdue and create a follow-up task for tomorrow." → `list_deals`, `get_contact`, `add_note`, `create_task`
- **Log a call and set the follow-up**: "Add this call summary as a note on Dana Whitfield's contact and create an EMAIL task for Friday to send the quote." → `list_contacts`, `add_note`, `create_task`
- **Move won deals to the next milestone** (runs: weekly): "Take the deals I listed as signed and move them to the Won milestone." → `list_deals`, `move_deal`

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

Yes. Cotlet does not replace your automation platform: it gives it a Agile CRM 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 weekly campaign performance report, 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/agile-crm/campaigns. | 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/agile-crm/campaigns with your API key. | cron or GitHub Actions. |

## Tools

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

### list_contacts

Lists contacts or companies, filtered by search text, tag or owner. Access: read. REST: `GET /api/v1/agile-crm/contacts`. MCP: `agile_crm_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Search text matched against names, emails and companies |
| `tag` | string | no | Only contacts with this tag, spelled as in Agile CRM |
| `owner_email` | string | no | Only contacts owned by this user |
| `type` | string | no | person (default) or company |
| `cursor` | string | no | next_cursor from the previous page |

Returns one page of contacts with id, name, email, company, tags, lead score, star value and owner, plus next_cursor while more remain.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "5698320417841152",
      "name": "Dana Whitfield",
      "email": "dana@example.com",
      "company": "Northwind Studio",
      "tags": [
        "webinar_oct",
        "lead"
      ],
      "score": 40,
      "star": 3,
      "owner": "sam@example.com"
    },
    {
      "contact_id": "5701182246576128",
      "name": "Luis Ortega",
      "email": "luis@example.org",
      "company": "Ortega Print",
      "tags": [
        "webinar_oct"
      ],
      "score": 15,
      "star": 0,
      "owner": "sam@example.com"
    }
  ],
  "next_cursor": null
}
```

### get_contact

Reads one contact with its properties, tags, notes, tasks and deals. Access: read. REST: `GET /api/v1/agile-crm/contacts/{contact_id}`. MCP: `agile_crm_read → get_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact id from list_contacts |

Returns the contact card as Agile CRM shows it: properties, tags, score, star value and owner, then the contact's notes and open tasks newest first and its deals with their milestones. Use it before writing a note or task so the agent works from the latest state.

Example response:

```json
{
  "contact_id": "5698320417841152",
  "name": "Dana Whitfield",
  "email": "dana@example.com",
  "company": "Northwind Studio",
  "tags": [
    "webinar_oct",
    "lead"
  ],
  "score": 40,
  "owner": "sam@example.com",
  "notes": [
    {
      "note_id": "5712044310921216",
      "subject": "Call",
      "body": "Asked for a quote for 20 seats."
    }
  ],
  "tasks": [
    {
      "task_id": "5733100225388544",
      "subject": "Send quote",
      "type": "EMAIL",
      "due": "2026-10-26"
    }
  ],
  "deals": [
    {
      "deal_id": "5640291877404672",
      "name": "Northwind 20 seats",
      "milestone": "Proposal",
      "value": 4200
    }
  ]
}
```

### list_deals

Lists deals of a track, grouped by milestone, optionally for one milestone or owner. Access: read. REST: `GET /api/v1/agile-crm/deals`. MCP: `agile_crm_read → list_deals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `track` | string | no | Track name as shown in Agile CRM; the default track when left out |
| `milestone` | string | no | Only deals in this milestone |
| `owner_email` | string | no | Only deals owned by this user |
| `cursor` | string | no | next_cursor from the previous page |

Returns deals with id, name, value, milestone, probability, expected close date, owner and the contacts linked to it.

Example response:

```json
{
  "track": "Default",
  "deals": [
    {
      "deal_id": "5640291877404672",
      "name": "Northwind 20 seats",
      "milestone": "Proposal",
      "value": 4200,
      "probability": 60,
      "close_date": "2026-11-06",
      "owner": "sam@example.com",
      "contact_ids": [
        "5698320417841152"
      ]
    },
    {
      "deal_id": "5655120934133760",
      "name": "Ortega Print rollout",
      "milestone": "Proposal",
      "value": 9500,
      "probability": 40,
      "close_date": "2026-11-20",
      "owner": "sam@example.com",
      "contact_ids": [
        "5701182246576128"
      ]
    }
  ],
  "next_cursor": null
}
```

### list_tasks

Lists tasks, filtered by type, owner or pending status. Access: read. REST: `GET /api/v1/agile-crm/tasks`. MCP: `agile_crm_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | no | CALL, EMAIL, FOLLOW_UP, MEETING, MILESTONE, SEND, TWEET or OTHER |
| `owner_email` | string | no | Only tasks of this user |
| `pending` | boolean | no | true for tasks not yet done |
| `cursor` | string | no | next_cursor from the previous page |

Returns tasks with id, subject, type, due date, owner and the contact they belong to. Use pending with owner_email to build a rep's open list for the day.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "5733100225388544",
      "subject": "Send quote",
      "type": "EMAIL",
      "due": "2026-10-26",
      "owner": "sam@example.com",
      "contact_id": "5698320417841152"
    },
    {
      "task_id": "5744019933298688",
      "subject": "Check in after demo",
      "type": "FOLLOW_UP",
      "due": "2026-10-27",
      "owner": "sam@example.com",
      "contact_id": "5701182246576128"
    }
  ],
  "next_cursor": null
}
```

### list_campaigns

Lists the campaigns (workflows) of the account with their names and ids. Access: read. REST: `GET /api/v1/agile-crm/campaigns`. MCP: `agile_crm_read → list_campaigns`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | next_cursor from the previous page |

Returns campaign id, name and creator, one page at a time. The id feeds get_campaign_report and add_contacts_to_campaign. Campaign workflows are not returned as a diagram; the nodes inside a campaign are not read.

Example response:

```json
{
  "campaigns": [
    {
      "campaign_id": "5731834621411328",
      "name": "Onboarding series",
      "creator": "Sam Keller"
    },
    {
      "campaign_id": "5748226110054400",
      "name": "October newsletter",
      "creator": "Sam Keller"
    }
  ],
  "next_cursor": null
}
```

### get_campaign_report

Reads the numbers of one campaign: opens, clicks, bounces, unsubscribes and spam complaints. Access: read. REST: `GET /api/v1/agile-crm/campaigns/{campaign_id}/report`. MCP: `agile_crm_read → get_campaign_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign id from list_campaigns |

Returns the counts Agile CRM shows behind the campaign's reporting icon, plus the clicked links with their click counts. Agile tracks opens and clicks only for HTML emails, so a plain-text campaign reports none. The call reads only; nothing is sent to contacts.

Example response:

```json
{
  "campaign_id": "5731834621411328",
  "name": "Onboarding series",
  "opened": 412,
  "clicked": 96,
  "bounced": 18,
  "unsubscribed": 7,
  "spam_complaints": 1,
  "links": [
    {
      "url": "https://example.com/start",
      "clicks": 61
    },
    {
      "url": "https://example.com/pricing",
      "clicks": 35
    }
  ]
}
```

### add_contact_tags

Adds tags to one or more contacts. Access: write. REST: `POST /api/v1/agile-crm/contact-tags`. MCP: `agile_crm_write → add_contact_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_ids` | array | yes | Contact ids from list_contacts |
| `tags` | array | yes | Tag names to add; a tag starts with a letter and holds letters, numbers, underscores and spaces |

Adds the tags to every contact in the list and returns each contact's tags afterwards. Tags reach nobody and a wrong tag is removed from Agile CRM by hand, so the call does not wait for your OK. A tag name Agile CRM rejects fails before any contact changes.

Example response:

```json
{
  "updated": [
    {
      "contact_id": "5698320417841152",
      "tags": [
        "webinar_oct",
        "lead",
        "nurture"
      ]
    },
    {
      "contact_id": "5701182246576128",
      "tags": [
        "webinar_oct",
        "nurture"
      ]
    }
  ]
}
```

### add_note

Adds a note to a contact. Access: write. REST: `POST /api/v1/agile-crm/contacts/{contact_id}/notes`. MCP: `agile_crm_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact id from list_contacts |
| `subject` | string | yes | Short title of the note |
| `body` | string | yes | Text of the note |

Creates the note on the contact's timeline and returns its id. Notes are visible to your team only and reach no customer, so the call does not wait for your OK.

Example response:

```json
{
  "note_id": "5712044310921216",
  "contact_id": "5698320417841152",
  "subject": "Call",
  "created_at": "2026-10-22T09:14:00Z"
}
```

### create_task

Creates a task for a contact with a type, due date and owner. Access: write. REST: `POST /api/v1/agile-crm/contacts/{contact_id}/tasks`. MCP: `agile_crm_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact the task belongs to |
| `subject` | string | yes | What has to be done |
| `type` | string | no | CALL, EMAIL, FOLLOW_UP, MEETING, MILESTONE, SEND, TWEET or OTHER |
| `due_date` | string | yes | Due date, YYYY-MM-DD |
| `owner_email` | string | no | User the task is assigned to; you when left out |

Creates the task on the contact and returns its id. A task shows in the owner's Tasks list inside your team and is deleted in Agile CRM in one step, so the call does not wait for your OK.

Example response:

```json
{
  "task_id": "5733100225388544",
  "contact_id": "5698320417841152",
  "subject": "Send quote",
  "type": "EMAIL",
  "due": "2026-10-26",
  "owner": "sam@example.com"
}
```

### move_deal

Moves a deal to another milestone of its track. Access: write. REST: `POST /api/v1/agile-crm/deals/{deal_id}/move`. MCP: `agile_crm_write → move_deal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `deal_id` | string | yes | Deal id from list_deals |
| `milestone` | string | yes | Milestone name as the deal's track shows it |

Changes the milestone and returns the deal with its new milestone. A milestone name the track does not have fails and the deal stays where it is. Moving a deal reaches no customer and is undone with one more call, so it does not wait for your OK.

Example response:

```json
{
  "deal_id": "5655120934133760",
  "name": "Ortega Print rollout",
  "previous_milestone": "Proposal",
  "milestone": "Negotiation",
  "value": 9500
}
```

### add_contacts_to_campaign

Adds a list of contacts to a campaign, like Bulk Actions > Add to Campaign. Access: write, asks the user first. REST: `POST /api/v1/agile-crm/campaigns/{campaign_id}/contacts-to-campaigns`. MCP: `agile_crm_write → add_contacts_to_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign id from list_campaigns |
| `contact_ids` | array | yes | Contact ids from list_contacts |

Selects the contacts on the Contacts page and runs the Add to Campaign bulk action with your campaign. Agile CRM runs the campaign on those contacts at once, so its emails go out to real people. Returns how many contacts were added. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "campaign_id": "5731834621411328",
  "campaign": "Onboarding series",
  "added": 3,
  "contact_ids": [
    "5698320417841152",
    "5701182246576128",
    "5709775523012608"
  ]
}
```

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

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

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

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

```
Every Monday, read the report of each Agile CRM campaign and send me opens, clicks, bounces, unsubscribes and spam complaints, flagging any campaign with more than 10 unsubscribes or a spam complaint.
```

### Call Agile CRM 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/agile-crm 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/agile-crm/contacts/5698320417841152/notes \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"Call","body":"Asked for a quote for 20 seats. Send by Friday."}'
```

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

```
{
  "note_id": "5712044310921216",
  "contact_id": "5698320417841152",
  "subject": "Call",
  "created_at": "2026-10-22T09:14:00Z"
}
```

## Why use Cotlet for Agile CRM?

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

## Is it safe to connect Agile CRM to Cotlet?

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

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

## Is there a Agile CRM MCP server on GitHub?

Agile CRM has an official Zapier app with triggers such as New Contact and New Deal and actions such as Create Contact, Create Deal and Add to Campaign. It runs on the REST API, so it shares the daily call cap and has no step for campaign reports. Cotlet works inside the signed-in app and complements Zapier, n8n and Make.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect Agile CRM with the API key from Admin Settings > API & Analytics, then build each Zap | Sign up, sign in to Agile CRM once, add one MCP server or API key |
| When Agile CRM changes | Zapier keeps its app up to date; steps the app does not offer stay missing | Our team tests it daily and fixes it for you; failed calls are free |
| Your Agile CRM session | Your API key, stored in the connection | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The key works until you reset it in Agile CRM | Your Cloud Browser keeps you signed in; if Agile CRM logs you out, your agent gets a link to sign in again |
| Upkeep | You maintain each Zap and watch the daily API call cap | Nothing to host or update |
| Where it runs | Zapier, on triggers and schedules | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Zapier subscription by task volume | 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 Agile CRM 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 Agile CRM API cost?

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

**Do I need to be technical?**

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

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

Agile CRM 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).

**Does Cotlet use my Agile CRM API key or its daily call cap?**

No. Agile CRM caps REST calls per day by plan: 500 on Free, 5,000 on Starter, 10,000 on Regular and 25,000 on Enterprise, according to its product update of 22 Jun 2016. Cotlet works in your signed-in Agile CRM session, not with the API key, so the key's daily count stays untouched.

**Can my agent build or edit campaign workflows?**

No. The tools read campaign names and reports and add contacts to a campaign. They do not create a campaign, change its nodes or send a newsletter. You build the campaign in Agile CRM under Campaigns > + Add Campaign, and your agent runs the contacts through it.

**Which Agile CRM role do I need?**

Any user who can open Contacts, Deals, Tasks and Campaigns. Agile CRM's Access Control can remove bulk actions such as Add to Campaign from a role, so a call fails when your role lacks it.

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

No. Every call to add_contacts_to_campaign waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_contact_tags, add_note, create_task, move_deal runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Agile CRM 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/agile-crm 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.