Ext Ops Panel
Open dashboard
Comparison

Iaptic vs Transistor MCP Server

Iaptic is an MCP server published by iaptic. Marketplaces we read that list it: 1 (Docker MCP Catalog). Transistor MCP Server is an MCP server published by conorbronsdon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceIapticTransistor MCP Server
Docker MCP Catalog Listed
Version: sha256:7f86e3becb71
Forks (GitHub): 6
Pulls (Docker Hub): 16 337
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (npm): 231
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 1
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

Iaptic vs Transistor MCP Server
FactIapticTransistor MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)1 (worse)
Pulls (Docker Hub) (differs)16 337No figure on Docker Hub
Forks (GitHub) (differs)6 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/iaptic)On your machine (transistor-mcp)
Transportstdiostdio
Tools it declares (differs)17Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/iaptic/mcp-server-iapticgithub.com/conorbronsdon/transistor-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

Iaptic

In its own words, on Docker MCP Catalog:

Model Context Protocol server for interacting with iaptic.

Transistor MCP Server

In its own words, on Official MCP Registry:

Manage Transistor.fm podcasts: episodes, analytics, transcripts, and webhooks.

How to run each

Iaptic As a local MCP server: Docker image

Claude Code
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iaptic

Requires: IAPTIC_API_KEY (secret)

Transistor MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "TRANSISTOR_API_KEY=<YOUR_TRANSISTOR_API_KEY>" --transport stdio transistor-mcp -- npx -y transistor-mcp

Requires: TRANSISTOR_API_KEY

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

Tools each declares

The marketplaces of Transistor MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only Iaptic asks for

  • IAPTIC_API_KEY (secret)
  • IAPTIC_APP_NAME

Only Transistor MCP Server asks for

  • TRANSISTOR_API_KEY

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

What it can do: Iaptic · What it can do: Transistor MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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