Ext Ops Panel
Open dashboard
Comparison

io.github.runapi-builder/infinitetalk-mcp vs Speak AI

io.github.runapi-builder/infinitetalk-mcp is an MCP server published by runapi-builder. Marketplaces we read that list it: 1 (Official MCP Registry). Speak AI is an MCP server published by speakai. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-17. 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
Marketplaceio.github.runapi-builder/infinitetalk-mcpSpeak AI
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 462
Downloads/week (npm): 49
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.38.2
Downloads/month (npm): 4 063
Downloads/week (npm): 1 641
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.19.0
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.runapi-builder/infinitetalk-mcp vs Speak AI
Factio.github.runapi-builder/infinitetalk-mcpSpeak AI
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (@runapi.ai/infinitetalk-mcp)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)Not a bundle6
Licence (differs)Not statedMIT
Repository (differs)github.com/runapi-ai/infinitetalk-mcpgithub.com/speakai/speakai-mcp
Changes in the last 7 days (differs)06
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

io.github.runapi-builder/infinitetalk-mcp

In its own words, on Official MCP Registry:

RunAPI MCP server for InfiniteTalk: create tasks, poll status, check pricing.

Speak AI

In its own words, on Official MCP Registry:

Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.

How to run each

io.github.runapi-builder/infinitetalk-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "RUNAPI_API_KEY=<YOUR_RUNAPI_API_KEY>" --transport stdio infinitetalk-mcp -- npx -y @runapi.ai/infinitetalk-mcp

Requires: RUNAPI_API_KEY (secret)

Speak AI As a remote MCP server

Claude Code
claude mcp add --transport http speak-ai https://api.speakai.co/v1/mcp

Requires: SPEAK_API_KEY (secret)

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

Only Speak AI 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

Only io.github.runapi-builder/infinitetalk-mcp asks for

  • RUNAPI_API_KEY (secret)

Only Speak AI asks for

  • SPEAK_API_KEY (secret)
  • SPEAK_BASE_URL

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

What it can do: io.github.runapi-builder/infinitetalk-mcp · What it can do: Speak AI · Compare two other plugins

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