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

# Vimeo API and MCP server

> Vimeo has a full REST API with OAuth 2.0 and an official remote MCP server in public beta that covers only part of it (checked 17 Oct 2026). The MCP server needs a Pro plan or above. Vimeo lists search, analytics, showcases, comments and transcripts for it, and says Claude cannot delete videos through the connector.

Video hosting for businesses and creators: a library with folders, a settings page per video, showcases, review links, captions and viewer analytics.

## What is the Vimeo API?

Cotlet's Vimeo API exposes 13 endpoints for your own Vimeo account: search videos, get video, list folders, list showcases, get video analytics, list comments, update video details, move videos to folder, set video privacy, upload captions, create showcase, add videos to showcase and delete comment. The search_videos endpoint returns search your library by title, tag or folder and return video details. Each endpoint takes simple JSON inputs like video_id, cursor or folder_id and works both as an operation of the vimeo_read or vimeo_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 13 (6 read, 7 write)
- **Updated:** 2026-10-22

Vimeo has a full REST API with OAuth 2.0 and an official remote MCP server in public beta that covers only part of it (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Vimeo with 13 endpoints (6 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Vimeo have an official API?

Vimeo has a full REST API with OAuth 2.0 and an official remote MCP server in public beta that covers only part of it (checked 17 Oct 2026). The MCP server needs a Pro plan or above. Vimeo lists search, analytics, showcases, comments and transcripts for it, and says Claude cannot delete videos through the connector.

| Task | Vimeo official | Cotlet |
|---|---|---|
| Search videos and read their details | Yes: API, and the official MCP server on Pro and above | Yes |
| Edit title, description and tags | Yes: API with an edit scope; you manage the token | Yes |
| Move videos into folders | Yes: API; the official MCP server does not list folders | Yes |
| Upload captions and subtitles | Yes: API text tracks need the upload and edit scopes and a WebVTT file; three calls per track | Yes |
| Change who can watch and where a video embeds | Yes: API with an edit scope | Yes |
| Create showcases and add videos | Yes: API, and the official MCP server can manage showcases | Yes |
| Read and delete comments | Partly: The official MCP server only checks comments and cannot delete | Yes |
| Engagement analytics across videos | Partly: Vimeo says the Engagement tab is not available through the public API | Yes |

Sources: [Vimeo Help: How to connect your Vimeo account to Claude (MCP server)](https://help.vimeo.com/hc/en-us/articles/49442010684689-How-to-connect-your-Vimeo-account-to-Claude-MCP-Server), [Vimeo developers: Working with Authentication](https://developer.vimeo.com/api/authentication), [Vimeo developers: Working with Text Track Uploads](https://developer.vimeo.com/api/upload/texttracks), [Vimeo Help: About engagement analytics](https://help.vimeo.com/hc/en-us/articles/44934439084561-About-engagement-analytics)

## For AI agents

```text
Vimeo has a full REST API with OAuth 2.0 and an official remote MCP server in public beta that covers only part of it (checked 17 Oct 2026). The MCP server needs a Pro plan or above. Vimeo lists search, analytics, showcases, comments and transcripts for it, and says Claude cannot delete videos through the connector.
Cotlet provides a hosted MCP server and REST API for Vimeo: 13 tools (6 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=vimeo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    vimeo_read, vimeo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/vimeo, each operation at its own route, e.g. POST /api/v1/vimeo/folders/{folder_id}/videos-to-folder/move
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_videos, get_video, list_folders, list_showcases, get_video_analytics, list_comments, update_video, move_videos_to_folder, set_video_privacy, upload_captions, create_showcase, add_videos_to_showcase, delete_comment
Confirm      set_video_privacy, upload_captions, delete_comment (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/vimeo-api-mcp-server.md

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

## What can an AI agent do in Vimeo?

Cotlet is best for video and marketing teams who want an AI agent to caption, sort and publish Vimeo videos without running or fixing a server, or managing their own OAuth app.

- **[Add captions to new videos](https://cotlet.dev/integrations/vimeo-api-mcp-server/add-captions-to-videos.md)** (runs: weekly): "Find videos in my Vimeo library that have no captions. For each one, upload the WebVTT file with the same name from my captions folder as English captions. List the videos with no matching file." → `search_videos`, `get_video`, `upload_captions`
- **[Organize videos into folders](https://cotlet.dev/integrations/vimeo-api-mcp-server/organize-videos-into-folders.md)** (runs: weekly): "List the videos in my Vimeo library that are not in a folder. Move the ones whose title starts with "Webinar" to the Webinars folder and the ones with "Tutorial" to Tutorials. Show me the rest." → `search_videos`, `list_folders`, `move_videos_to_folder`
- **[Report video performance](https://cotlet.dev/integrations/vimeo-api-mcp-server/report-video-performance.md)** (runs: weekly): "Pull engagement for my Vimeo videos for the last 30 days. Show views, average percent watched and completion rate, and name the three videos where viewers drop off earliest." → `search_videos`, `get_video_analytics`
- **Publish new videos to a showcase** (runs: weekly): "Make a showcase called "Customer Stories" if it does not exist. Add every video tagged "customer" to it and set those videos to Unlisted. Tell me what changed." → `search_videos`, `create_showcase`, `add_videos_to_showcase`, `set_video_privacy`
- **Clear spam comments** (runs: weekly): "List new comments on my Vimeo videos from the last week. Delete the ones that are links to other sites or ads and show me the rest." → `search_videos`, `list_comments`, `delete_comment`

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

Yes. Cotlet does not replace your automation platform: it gives it a Vimeo 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 add captions to new videos, 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/vimeo/videos/search. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/vimeo/videos/search with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Vimeo.

### search_videos

Search your library by title, tag or folder and return video details. Access: read. REST: `GET /api/v1/vimeo/videos/search`. MCP: `vimeo_read → search_videos`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Words in the title. |
| `tag` | string | no | Only videos with this tag. |
| `folder_id` | string | no | Folder ID from list_folders. Omit for the whole library; 'none' for videos in no folder. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns videos from your library, newest first, with title, tags, privacy, folder and caption languages. Narrow it with a folder or a tag. Each call returns one page; pass the cursor to continue. It sees what your account sees, so a team member sees the Team library only with access.

Example response:

```json
{
  "videos": [
    {
      "video_id": "912345601",
      "title": "Onboarding 01",
      "tags": [
        "onboarding"
      ],
      "privacy": "unlisted",
      "folder": "Training",
      "caption_languages": [],
      "duration_seconds": 412,
      "uploaded_at": "2026-10-12T08:20:00Z"
    },
    {
      "video_id": "912345611",
      "title": "Webinar: Q3 results",
      "tags": [
        "webinar"
      ],
      "privacy": "private",
      "folder": null,
      "caption_languages": [
        "en"
      ],
      "duration_seconds": 3120,
      "uploaded_at": "2026-10-14T14:05:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_video

Read one video: settings, privacy, embed rule, tags and caption tracks. Access: read. REST: `GET /api/v1/vimeo/videos/{video_id}`. MCP: `vimeo_read → get_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |

Returns what the video settings page shows: title, description, tags, privacy, where it can be embedded, thumbnail and the text tracks with language and type. Use it before a write to check the current value.

Example response:

```json
{
  "video_id": "912345601",
  "title": "Onboarding 01",
  "description": "First day in the product.",
  "tags": [
    "onboarding"
  ],
  "privacy": "unlisted",
  "embed": "anywhere",
  "folder": "Training",
  "text_tracks": [],
  "link": "https://vimeo.com/912345601"
}
```

### list_folders

List folders and subfolders with their IDs. Access: read. REST: `GET /api/v1/vimeo/folders`. MCP: `vimeo_read → list_folders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns every folder you can see with its ID, name, parent and video count, top level first. Subfolders go up to 10 levels deep. On a team account it lists the Team library folders you have access to.

Example response:

```json
{
  "folders": [
    {
      "folder_id": "20481",
      "name": "Webinars",
      "parent_id": null,
      "video_count": 14
    },
    {
      "folder_id": "20482",
      "name": "Tutorials",
      "parent_id": null,
      "video_count": 10
    },
    {
      "folder_id": "20490",
      "name": "Customer stories",
      "parent_id": "20482",
      "video_count": 3
    }
  ]
}
```

### list_showcases

List your showcases with privacy and video count. Access: read. REST: `GET /api/v1/vimeo/showcases`. MCP: `vimeo_read → list_showcases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each showcase with ID, title, privacy and the number of videos in it. A video can be in several showcases. Use it to check a showcase exists before creating one.

Example response:

```json
{
  "showcases": [
    {
      "showcase_id": "8830012",
      "title": "Customer Stories",
      "privacy": "unlisted",
      "video_count": 4
    }
  ]
}
```

### get_video_analytics

Read the Engagement table for a date range. Access: read. REST: `GET /api/v1/vimeo/video-analytics`. MCP: `vimeo_read → get_video_analytics`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | no | One video from search_videos. Omit for all videos. |
| `from` | string | no | Start date, YYYY-MM-DD. |
| `to` | string | no | End date, YYYY-MM-DD. |

Returns the Engagement table: views, average percent watched, average completion rate and the views reached at 1%, 25%, 50%, 75% and 100% of the video. It counts views, not unique viewers. The per-video panel needs a paid plan, so on a Free plan the call returns an error that says so.

Example response:

```json
{
  "from": "2026-09-17",
  "to": "2026-10-17",
  "videos": [
    {
      "video_id": "912345601",
      "title": "Onboarding 01",
      "views": 420,
      "average_percent_watched": 58,
      "average_completion_rate": 31,
      "views_at": {
        "p1": 420,
        "p25": 300,
        "p50": 210,
        "p75": 150,
        "p100": 130
      }
    }
  ]
}
```

### list_comments

List viewer comments on a video, newest first. Access: read. REST: `GET /api/v1/vimeo/videos/{video_id}/comments`. MCP: `vimeo_read → list_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns public viewer comments with author, text, date and replies. Collaborator comments from review links are separate and are not included. If comments are turned off on the video, the list is empty.

Example response:

```json
{
  "video_id": "912345601",
  "comments": [
    {
      "comment_id": "c-7781",
      "author": "Sam Rivera",
      "text": "Great walkthrough, thank you.",
      "created_at": "2026-10-15T10:12:00Z",
      "replies": 0
    },
    {
      "comment_id": "c-7790",
      "author": "promo_seller",
      "text": "Cheap followers at example.net",
      "created_at": "2026-10-16T22:40:00Z",
      "replies": 0
    }
  ],
  "next_cursor": null
}
```

### update_video

Change title, description or tags of one video. Access: write. REST: `PATCH /api/v1/vimeo/videos/{video_id}`. MCP: `vimeo_write → update_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |
| `title` | string | no | New title. |
| `description` | string | no | New description, plain text. |
| `tags` | string[] | no | Full tag list. It replaces the current tags. |

Changes the fields you pass on the video settings page and leaves the rest. The title is capped by the field in the app. Changes save at once and a second call puts the old value back, so this tool does not ask for confirmation by default. On a public video the new text is visible to viewers.

Example response:

```json
{
  "video_id": "912345601",
  "title": "Onboarding 01: first day",
  "description": "First day in the product.",
  "tags": [
    "onboarding",
    "training"
  ],
  "updated": true
}
```

### move_videos_to_folder

Move up to 50 videos into one folder. Access: write. REST: `POST /api/v1/vimeo/folders/{folder_id}/videos-to-folder/move`. MCP: `vimeo_write → move_videos_to_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_ids` | string[] | yes | Video IDs from search_videos, 50 at most. |
| `folder_id` | string | yes | Destination folder ID from list_folders. |

Moves the videos to the folder and returns how many moved and which were skipped. Vimeo moves up to 50 selected videos at a time, so a longer list is refused. A video sits in one folder, so a moved video leaves its old one. Share links and embed codes do not change. It reaches no one and a second call moves the videos back, so it does not ask for confirmation by default.

Example response:

```json
{
  "folder_id": "20481",
  "folder": "Webinars",
  "moved": 3,
  "skipped": []
}
```

### set_video_privacy

Change who can watch a video and where it can be embedded. Access: write, asks the user first. REST: `PUT /api/v1/vimeo/videos/{video_id}/privacy`. MCP: `vimeo_write → set_video_privacy`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |
| `privacy` | enum | yes | public, unlisted, password, embed_only or private. |
| `password` | string | no | Required when privacy is password. |
| `embed` | enum | no | anywhere, nowhere or domains. |
| `embed_domains` | string[] | no | Allowed domains when embed is domains. Up to 50. |

Sets the viewing privacy and optionally the embed rule. Privacy is public, unlisted, password, embed_only or private; unlisted, password and embed_only need a paid plan. Embed is anywhere, nowhere or domains. A private video cannot play when embedded elsewhere. A public video appears in search engines and on your profile. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "video_id": "912345611",
  "privacy": "unlisted",
  "embed": "anywhere",
  "updated": true
}
```

### upload_captions

Add a caption or subtitle track to a video from WebVTT or SRT text. Access: write, asks the user first. REST: `POST /api/v1/vimeo/videos/{video_id}/captions`. MCP: `vimeo_write → upload_captions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |
| `language` | string | yes | Language code, for example 'en' or 'es'. |
| `type` | enum | yes | caption or subtitle. |
| `content` | string | yes | The full WebVTT or SRT text. |

Uploads the file as a text track with the language and type you set, then switches it on. WebVTT must start with WEBVTT and SRT with the first cue number; both must be UTF-8. A file in another format is refused with the reason. Viewers see the track at once. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "video_id": "912345601",
  "language": "en",
  "type": "caption",
  "format": "webvtt",
  "active": true
}
```

### create_showcase

Create an empty showcase with a title, description and privacy. Access: write. REST: `POST /api/v1/vimeo/showcases`. MCP: `vimeo_write → create_showcase`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Showcase title. |
| `description` | string | no | Showcase description. |
| `privacy` | enum | no | public, unlisted, password or private. Default: unlisted. |

Creates the showcase and returns its ID and link. Privacy follows the same choices as a video. A showcase reaches no one until you share the link or make it public, and you can change or remove it afterwards, so this tool does not ask for confirmation by default.

Example response:

```json
{
  "showcase_id": "8830012",
  "title": "Customer Stories",
  "privacy": "unlisted",
  "link": "https://vimeo.com/showcase/8830012"
}
```

### add_videos_to_showcase

Add videos to a showcase. Access: write. REST: `POST /api/v1/vimeo/showcases/{showcase_id}/videos-to-showcases`. MCP: `vimeo_write → add_videos_to_showcase`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `showcase_id` | string | yes | Showcase ID from list_showcases or create_showcase. |
| `video_ids` | string[] | yes | Video IDs from search_videos. |

Adds the videos you list and returns the new count. A video can be in several showcases. A video that is not public takes its visibility from the showcase privacy settings. A showcase with more than 100 videos cannot be custom sorted. It does not ask for confirmation by default because one call removes nothing and a second call can take the videos out.

Example response:

```json
{
  "showcase_id": "8830012",
  "added": 2,
  "video_count": 4
}
```

### delete_comment

Delete a viewer comment on your video, with its replies. Access: write, asks the user first. REST: `DELETE /api/v1/vimeo/videos/{video_id}/comments/{comment_id}`. MCP: `vimeo_write → delete_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from search_videos, the number in vimeo.com/{id}. |
| `comment_id` | string | yes | Comment ID from list_comments. |

Deletes the comment and any replies to it. The video owner can delete any comment on the video. It cannot be undone. If comments are turned off on the video the app may hide the delete option, and the call returns an error that says so. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "video_id": "912345601",
  "comment_id": "c-7790",
  "deleted": true,
  "replies_deleted": 0
}
```

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

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

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

2. **Sign in to Vimeo in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Vimeo 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 Vimeo tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Find videos in my Vimeo library that have no captions. For each one, upload the WebVTT file with the same name from my captions folder as English captions. List the videos with no matching file.
```

### Call Vimeo 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/vimeo 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/vimeo/folders/20481/videos-to-folder/move \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"video_ids":["912345611","912345612","912345613"]}'
```

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

```
{
  "folder_id": "20481",
  "folder": "Webinars",
  "moved": 3,
  "skipped": []
}
```

## Why use Cotlet for Vimeo?

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

## Is it safe to connect Vimeo to Cotlet?

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

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

## Is there a Vimeo MCP server on GitHub?

Yes. Community Vimeo MCP servers exist on GitHub, usually maintained by one person. You install one yourself, register a Vimeo app, keep its access token in a file, and fix it when Vimeo changes. Cotlet hosts the same kind of server for you, works through your own Vimeo login, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an app on the Vimeo developer site, generate an access token with the right scopes, add the server to each MCP client | Sign up, sign in to Vimeo once, add one MCP server or API key |
| When Vimeo changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Vimeo access | Access token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you generate a new token or fix the scopes | Your Cloud Browser keeps you signed in; if Vimeo 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, paid for with 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 Vimeo 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 Vimeo API cost?

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

**Do I need to be technical?**

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

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

Vimeo 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 a Pro plan to use Cotlet with Vimeo?**

No. Cotlet works through your own Vimeo login, so it has no plan gate of its own. Vimeo itself limits some features by plan: the official MCP server needs a Pro plan or above, and the per-video analytics panel needs a paid plan (Vimeo Help).

**Will my agent delete or publish anything without asking?**

Only if you switch confirmation off. By default every privacy change, caption upload and comment deletion waits for your OK. Vimeo blocks deletes in its own MCP connector, but a deleted comment in Cotlet is gone, so keep confirmation on for delete_comment (Vimeo Help: How to use comments).

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

No. Every call to set_video_privacy, upload_captions or delete_comment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_video, move_videos_to_folder, create_showcase, add_videos_to_showcase runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Vimeo 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/vimeo 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.