Ext Ops Panel
Open dashboard
Comparison

Vimeo MCP Server and API by Cotlet vs io.github.AceDataCloud/mcp-veo

Vimeo MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.AceDataCloud/mcp-veo is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceVimeo MCP Server and API by Cotletio.github.AceDataCloud/mcp-veo
Official MCP Registry Listed
Version: 1.0.2
No figure published
Not marked · First seen
Listed
Version: 2026.11.1.0
Downloads/month (PyPI): 1 639
Downloads/week (PyPI): 289
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2026.11.1.0
Downloads/month (PyPI): 1 639
Downloads/week (PyPI): 289
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Vimeo MCP Server and API by Cotlet vs io.github.AceDataCloud/mcp-veo
FactVimeo MCP Server and API by Cotletio.github.AceDataCloud/mcp-veo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)2026-11-10 (better)2026-11-01 (worse)
Where it runs (differs)Remote server (cotlet.dev/mcp/v1/vimeo/connect)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/acedatacloud/veomcp
Changes in the last 7 days (differs)70
First seen (differs)2026-11-092026-10-11
Endpoint at the last check (differs)not checked yetStatus out of date: last check 30 h ago returned HTTP 401

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Vimeo MCP Server and API by Cotlet

In its own words, on Official MCP Registry:

Vimeo business video hosting MCP server: search videos, edit video details, move videos to folder.

io.github.AceDataCloud/mcp-veo

In its own words, on Official MCP Registry:

MCP server for Google Veo AI video generation

How to run each

Vimeo MCP Server and API by Cotlet As a remote MCP server

Claude Code
claude mcp add --transport http vimeo https://cotlet.dev/mcp/v1/vimeo/connect

io.github.AceDataCloud/mcp-veo As a remote MCP server

Claude Code
claude mcp add --transport http mcp-veo https://veo.mcp.acedata.cloud/mcp

Requires: ACEDATACLOUD_API_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.AceDataCloud/mcp-veo has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Vimeo MCP Server and API by Cotlet publish no settings it asks for, so we do not compare settings.

What it can do: Vimeo MCP Server and API by Cotlet · What it can do: io.github.AceDataCloud/mcp-veo · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built