Ext Ops Panel
Open dashboard
Comparison

twelvelabs vs Memo AI – meeting assistant

twelvelabs is a plugin bundle for AI coding tools published by twelvelabs-io. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Memo AI – meeting assistant is an MCP server published by memoai.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
MarketplacetwelvelabsMemo AI – meeting assistant
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 6
Stars (GitHub): 26
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 110
Downloads/week (npm): 51
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

twelvelabs vs Memo AI – meeting assistant
FacttwelvelabsMemo AI – meeting assistant
Marketplaces that list it11
Stars (GitHub) (differs)26No figure on GitHub
Forks (GitHub) (differs)6No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (twelvelabs-mcp)On your machine (memoai-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Hooks it runs (differs)6Not published
Parts of the bundle (differs)24Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/twelvelabs-io/twelve-labs-claude-code-pluginNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

twelvelabs

In its own words, on Claude Code: claude-plugins-community:

A lightweight plugin that integrates TwelveLabs video understanding capabilities directly into Claude Code - enabling semantic video search and dynamic video analysis.

Memo AI – meeting assistant

In its own words, on Official MCP Registry:

Search transcripts and summaries of your meetings, calls, and recordings in Memo AI

How to run each

twelvelabs As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install twelvelabs@claude-community

Memo AI – meeting assistant As a local MCP server: npm package

Claude Code
claude mcp add --env "MEMO_API_KEY=<YOUR_MEMO_API_KEY>" --transport stdio memo-ai -- npx -y memoai-mcp-server

Requires: MEMO_API_KEY (secret)

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

Tools each declares

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

Settings each asks for

Only twelvelabs asks for

  • TWELVELABS_API_KEY (secret)

Only Memo AI – meeting assistant asks for

  • MEMO_API_KEY (secret)
  • MEMO_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: twelvelabs · What it can do: Memo AI – meeting assistant · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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