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

# Krisp API and MCP server

> Krisp has no public REST API (checked 22 Oct 2026): its integrations page answers "Not right now". It offers an official MCP server and a Webhook API on the Core and Advanced plans. The MCP reads meetings and changes tags, action item status, speaker names and imports. The webhook sends meeting outputs to your own URL.

AI meeting assistant that records and transcribes calls, cancels noise and writes notes with key points and action items, which you open, share and organize in an account dashboard.

## What is the Krisp API?

Cotlet's Krisp API exposes 11 endpoints for your own Krisp account: list meetings, get meeting, list action items, list folders, list meetings shared with me, get meeting sharing, share meeting, set meeting access, add meeting to folder, tag meeting and update action item. The list_meetings endpoint returns your meetings from My Notes, with tags, folders and open action items. Each endpoint takes simple JSON inputs like meeting_id, from or to and works both as an operation of the krisp_read or krisp_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-21

Krisp has no public REST API (checked 22 Oct 2026): its integrations page answers "Not right now". Cotlet is a hosted MCP server and REST API for Krisp with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Krisp have an official API?

Krisp has no public REST API (checked 22 Oct 2026): its integrations page answers "Not right now". It offers an official MCP server and a Webhook API on the Core and Advanced plans. The MCP reads meetings and changes tags, action item status, speaker names and imports. The webhook sends meeting outputs to your own URL.

| Task | Krisp official | Cotlet |
|---|---|---|
| Search meetings and read transcripts, summaries and notes | Yes: Official MCP, Core and Advanced plans | Yes |
| List action items | Yes: Official MCP | Yes |
| Mark action items done | Yes: Official MCP, up to 50 in one call | Yes |
| Set action item due date, priority or assignee | No | Yes |
| Tag meetings | Yes: Official MCP attaches and removes tags | Yes |
| Add meetings to a folder | No: The MCP lists folders and the meetings in them only | Yes |
| Share a meeting with people | No: Krisp Auto-Share follows the calendar invite, one rule for all meetings | Yes |
| See who a meeting is shared with | No | Yes |

Sources: [Krisp Help: Krisp MCP](https://help.krisp.ai/hc/en-us/articles/25396920405148-Krisp-MCP), [Krisp Help: Krisp MCP supported tools](https://help.krisp.ai/hc/en-us/articles/25416265429660-Krisp-MCP-Supported-tools), [Krisp Help: Webhook API](https://help.krisp.ai/hc/en-us/articles/24514911804316-Webhook-API), [Krisp integrations: Does Krisp have an API?](https://krisp.ai/integrations/)

## For AI agents

```text
Krisp has no public REST API (checked 22 Oct 2026): its integrations page answers "Not right now". It offers an official MCP server and a Webhook API on the Core and Advanced plans. The MCP reads meetings and changes tags, action item status, speaker names and imports. The webhook sends meeting outputs to your own URL.
Cotlet provides a hosted MCP server and REST API for Krisp: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=krisp, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    krisp_read, krisp_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/krisp, each operation at its own route, e.g. POST /api/v1/krisp/meetings/{meeting_id}/share
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_meetings, get_meeting, list_action_items, list_folders, list_shared_with_me, get_meeting_sharing, share_meeting, set_meeting_access, add_meeting_to_folder, tag_meeting, update_action_item
Confirm      share_meeting, set_meeting_access, add_meeting_to_folder, update_action_item (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/krisp-api-mcp-server.md

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

## What can an AI agent do in Krisp?

Cotlet is best for Krisp users who run client calls and team syncs and want an agent to share meetings, file them in folders and assign action items without running or fixing a server.

- **[Share meeting notes after calls](https://cotlet.dev/integrations/krisp-api-mcp-server/share-meeting-notes-after-calls.md)** (runs: daily): "Look at yesterday's Krisp meetings. For client calls, check who the meeting is already shared with and share it by email with the attendees I name, with Can view access. Leave internal calls alone." → `list_meetings`, `get_meeting`, `get_meeting_sharing`, `share_meeting`
- **[Organize meetings into folders and tags](https://cotlet.dev/integrations/krisp-api-mcp-server/organize-meetings-into-folders.md)** (runs: weekly): "Go through this week's Krisp meetings. Put each client call in the folder named after the client and tag it Client. Leave meetings that match no folder for me." → `list_folders`, `list_meetings`, `get_meeting`, `add_meeting_to_folder`, `tag_meeting`
- **[Assign action items with owners and due dates](https://cotlet.dev/integrations/krisp-api-mcp-server/assign-action-items-due-dates.md)** (runs: daily): "List open Krisp action items with no assignee or no due date. Read the source meeting, and where someone said who and by when, set the assignee and due date. Leave the rest for me." → `list_action_items`, `get_meeting`, `update_action_item`
- **Weekly open action items digest** (runs: weekly): "Every Monday, list the action items assigned to me that are still open, grouped by meeting, with due dates." → `list_action_items`, `get_meeting`
- **Catch up on meetings shared with me** (runs: daily): "List meetings shared with me since yesterday and give me three key points from each." → `list_shared_with_me`, `get_meeting`

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

Yes. Cotlet does not replace your automation platform: it gives it a Krisp 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 share meeting notes after calls, 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/krisp/meetings. | 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/krisp/meetings 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 Krisp.

### list_meetings

Your meetings from My Notes, with tags, folders and open action items. Access: read. REST: `GET /api/v1/krisp/meetings`. MCP: `krisp_read → list_meetings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Text to match in the meeting title. |
| `from` | string | no | Earliest start date, YYYY-MM-DD. |
| `to` | string | no | Latest start date, YYYY-MM-DD. |
| `tag` | string | no | Only meetings with this tag. |
| `folder_id` | string | no | Only meetings in this folder, from list_folders. |
| `cursor` | string | no | next_cursor from the previous call. |

Returns meetings in the order My Notes shows them, each with its ID, title, start time, duration, tags, folders and the number of open action items. A next_cursor means there are more. Only your own meetings are listed; meetings shared with you come from list_shared_with_me.

Example response:

```json
{
  "meetings": [
    {
      "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
      "title": "Acme weekly sync",
      "started_at": "2026-10-21T14:00:00Z",
      "duration_minutes": 32,
      "tags": [
        "Client"
      ],
      "folders": [],
      "open_action_items": 4
    },
    {
      "meeting_id": "7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c",
      "title": "Lumen onboarding",
      "started_at": "2026-10-21T09:30:00Z",
      "duration_minutes": 48,
      "tags": [],
      "folders": [
        "Lumen"
      ],
      "open_action_items": 2
    }
  ],
  "next_cursor": null
}
```

### get_meeting

Returns the notes of one meeting: summary, key points, action items, outline and transcript. Access: read. REST: `GET /api/v1/krisp/meetings/{meeting_id}`. MCP: `krisp_read → get_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `include` | string[] | no | Parts to return: summary, key_points, action_items, outline, transcript. Default: summary, key_points, action_items. |

Returns the parts you ask for. The outline exists only if it was generated for the meeting. The transcript is large, so ask for it only when the summary is not enough. Meetings shared with you can be read with the access you were given.

Example response:

```json
{
  "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
  "title": "Acme weekly sync",
  "summary": "Acme approved the revised scope and asked for an updated quote before the board meeting.",
  "key_points": [
    "Scope approved without the reporting module",
    "Quote needed before the board meeting"
  ],
  "action_items": [
    {
      "action_item_id": "91919191919191919191919191919191",
      "text": "Send revised quote",
      "assignee": null,
      "due_date": null,
      "completed": false
    },
    {
      "action_item_id": "92929292929292929292929292929292",
      "text": "Share the new timeline",
      "assignee": "Luis Ortega",
      "due_date": "2026-10-28",
      "completed": false
    }
  ]
}
```

### list_action_items

Lists action items from the Action Items page. Access: read. REST: `GET /api/v1/krisp/action-items`. MCP: `krisp_read → list_action_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `view` | string | no | assigned_to_me or all. Default: assigned_to_me. |
| `status` | string | no | open or done. Default: open. |
| `meeting_id` | string | no | Only items from this meeting. |

Returns each item with its ID, text, assignee, due date, priority, status and source meeting. The all view lists tasks from all meetings and team members, as the app does. Titles are not unique, so use the ID to update an item.

Example response:

```json
{
  "action_items": [
    {
      "action_item_id": "91919191919191919191919191919191",
      "text": "Send revised quote",
      "assignee": null,
      "due_date": null,
      "priority": null,
      "completed": false,
      "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
      "meeting_title": "Acme weekly sync"
    },
    {
      "action_item_id": "93939393939393939393939393939393",
      "text": "Book the venue",
      "assignee": null,
      "due_date": null,
      "priority": null,
      "completed": false,
      "meeting_id": "5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e",
      "meeting_title": "Offsite planning"
    }
  ]
}
```

### list_folders

Lists your meeting folders in Private and Teamspace. Access: read. REST: `GET /api/v1/krisp/folders`. MCP: `krisp_read → list_folders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `space` | string | no | private or teamspace. Default: both. |

Returns each folder with its ID, name, description, space, your permission on it and the number of meetings. Your permission is Owner, Can collaborate or Can view, and only the first two can add meetings.

Example response:

```json
{
  "folders": [
    {
      "folder_id": "21212121212121212121212121212121",
      "name": "Acme",
      "space": "private",
      "permission": "Owner",
      "meetings": 12
    },
    {
      "folder_id": "22222222222222222222222222222222",
      "name": "Product syncs",
      "space": "teamspace",
      "permission": "Can collaborate",
      "meetings": 31
    }
  ]
}
```

### list_shared_with_me

Lists meetings that teammates shared with you, the Shared with me page. Access: read. REST: `GET /api/v1/krisp/shared-with-mes`. MCP: `krisp_read → list_shared_with_me`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | string | no | Earliest start date, YYYY-MM-DD. |
| `to` | string | no | Latest start date, YYYY-MM-DD. |
| `cursor` | string | no | next_cursor from the previous call. |

Returns the owner, title, start time and your access level for each meeting. Meetings shared with your whole work domain do not appear here, because Krisp does not list them in Shared with me either.

Example response:

```json
{
  "meetings": [
    {
      "meeting_id": "5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e",
      "title": "Offsite planning",
      "owner": "Jordan Reyes",
      "started_at": "2026-10-20T15:00:00Z",
      "access": "Can view"
    }
  ],
  "next_cursor": null
}
```

### get_meeting_sharing

Shows who a meeting is shared with, as the Share dialog does. Access: read. REST: `GET /api/v1/krisp/meetings/{meeting_id}/sharing`. MCP: `krisp_read → get_meeting_sharing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |

Returns the general access option and its access level, and every invited email with its level. Only the owner of a meeting sees the full list. Folder members also reach a meeting as Viewers, and the result lists the folders that give that access.

Example response:

```json
{
  "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
  "general_access": "invite_only",
  "general_access_level": "can_view",
  "invited": [
    {
      "email": "luis@acme-example.com",
      "access": "can_view"
    }
  ],
  "via_folders": []
}
```

### share_meeting

Invites people by email to a meeting you own. Access: write, asks the user first. REST: `POST /api/v1/krisp/meetings/{meeting_id}/share`. MCP: `krisp_write → share_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `emails` | string[] | yes | Email addresses to invite. |
| `access` | string | no | can_view, can_comment, can_edit or can_view_ai_notes. Default: can_view. |

Each invited person gets an email with a link and sees the shared transcript, notes and recording at the level you set. Returns the invited list after the call. An address that already has access is left as it is. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
  "invited": [
    {
      "email": "dana@acme-example.com",
      "access": "can_view",
      "status": "invited"
    },
    {
      "email": "luis@acme-example.com",
      "access": "can_view",
      "status": "already_had_access"
    }
  ]
}
```

### set_meeting_access

Changes the general access option of a meeting you own. Access: write, asks the user first. REST: `PUT /api/v1/krisp/meetings/{meeting_id}/access`. MCP: `krisp_write → set_meeting_access`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `general_access` | string | yes | invite_only, work_domain, team or anyone_with_link. |
| `access` | string | no | can_view, can_comment, can_edit or can_view_ai_notes. Default: can_view. |

A meeting has one general access option at a time, and people invited by email keep their access. work_domain needs a team work domain. With work_domain no email is sent, so tell people the link yourself. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
  "general_access": "team",
  "general_access_level": "can_view"
}
```

### add_meeting_to_folder

Adds one of your meetings to a folder. Access: write, asks the user first. REST: `POST /api/v1/krisp/folders/{folder_id}/meetings/{meeting_id}/to-folder`. MCP: `krisp_write → add_meeting_to_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `folder_id` | string | yes | Folder ID from list_folders. |

Works only for meetings you own, in folders where you are Owner or Can collaborate. Folder members see the meeting as Viewers, and everyone on the team sees it in a Teamspace folder. A meeting already in the folder is returned unchanged. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "meeting_id": "7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c",
  "folder_id": "21212121212121212121212121212121",
  "folder": "Acme",
  "space": "private",
  "status": "added"
}
```

### tag_meeting

Adds tags to a meeting, or removes them. Access: write. REST: `POST /api/v1/krisp/meetings/{meeting_id}/tag`. MCP: `krisp_write → tag_meeting`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `tags` | string[] | yes | Tag names. |
| `remove` | boolean | no | true removes the tags instead. Default: false. |

A tag that does not exist yet is created and shared with your team. A meeting holds at most 7 tags, and the call fails with the current list when it would pass that. Removing a tag leaves it in the workspace. This reaches no one and one call with remove set to true undoes it, so it does not wait for your OK.

Example response:

```json
{
  "meeting_id": "7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c",
  "tags": [
    "Client",
    "Onboarding"
  ],
  "created": [
    "Onboarding"
  ]
}
```

### update_action_item

Sets the due date, priority, assignee or completion of an action item. Access: write, asks the user first. REST: `PATCH /api/v1/krisp/action-items/{action_item_id}`. MCP: `krisp_write → update_action_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `action_item_id` | string | yes | Action item ID from list_action_items. |
| `due_date` | string | no | Due date, YYYY-MM-DD. |
| `priority` | string | no | Priority, as the item's Priority field shows it in Krisp. |
| `assignee_email` | string | no | Email of a team member to assign the item to. |
| `completed` | boolean | no | true marks it done, false reopens it. |

Changes only the fields you send. Assigning an item adds an assignment to the assignee's Activity Center, so it reaches another person. Returns the item after the change. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "action_item_id": "91919191919191919191919191919191",
  "text": "Send revised quote",
  "assignee": "Dana Whitfield",
  "due_date": "2026-10-30",
  "completed": false
}
```

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

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

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

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

```
Look at yesterday's Krisp meetings. For client calls, check who the meeting is already shared with and share it by email with the attendees I name, with Can view access. Leave internal calls alone.
```

### Call Krisp 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/krisp 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/krisp/meetings/3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a/share \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails":["dana@acme-example.com"],"access":"can_view"}'
```

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

```
{
  "meeting_id": "3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a3a",
  "invited": [
    {
      "email": "dana@acme-example.com",
      "access": "can_view",
      "status": "invited"
    }
  ]
}
```

## Why use Cotlet for Krisp?

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

## Is it safe to connect Krisp to Cotlet?

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

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

## Is there a Krisp MCP server on GitHub?

Krisp's own MCP server is the right tool for searching and reading meetings, tagging them and ticking off action items. It runs on the Core and Advanced plans. It has no tool to share a meeting, file it in a folder or set an action item owner or due date. Cotlet covers those in your Krisp account, and you can run both side by side.

|  | Official Krisp MCP | Cotlet |
|---|---|---|
| Setup | Add https://mcp.krisp.ai/mcp to your MCP client and finish the OAuth sign-in | Sign up, sign in to Krisp once, add one MCP server or API key |
| What it covers | Search, transcripts, summaries, action items, tags, speaker names, recording import | Reads plus sharing, folders and action item owners and due dates |
| When Krisp changes | Krisp maintains it | Our team runs automatic checks and fixes it for you; failed calls are free |
| Your Krisp session | An OAuth token kept by your MCP client | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | Nothing to host | Nothing to host or update |
| Where it runs | MCP clients such as Claude Code, Cursor, VS Code and ChatGPT | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Included with the Core or Advanced plan | 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 Krisp 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 Krisp API cost?

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

**Do I need to be technical?**

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

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

Krisp 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 Krisp plan do I need?**

Krisp's own MCP server and Webhook API are for the Core and Advanced plans (Krisp Help, checked 22 Oct 2026). Cotlet works in your Krisp account dashboard, so it sees what your plan and role show there. Features such as the Outline need Core, and a call fails with a clear error when your plan or role does not allow the action.

**Does Cotlet record meetings?**

No. Krisp records and transcribes in its own app, and each recorded meeting is saved to your account dashboard. Cotlet works with those saved meetings: it reads them, shares them, files them and updates their action items. Nothing changes your Krisp app, audio settings or billing.

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

No. Every call to share_meeting, set_meeting_access, add_meeting_to_folder or update_action_item waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. tag_meeting runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Krisp 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/krisp 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.