Ext Ops Panel
Open dashboard
Comparison

API Gateway vs Ableton Live MCP Server

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ableton Live MCP Server is an MCP server published by wstierhout. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-28. 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
MarketplaceAPI GatewayAbleton Live MCP Server
Docker MCP Catalog Listed
Version: sha256:9cc67b4a037f
Forks (GitHub): 12
Pulls (Docker Hub): 59 566
Stars (Docker Hub): 6
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.8.1
Downloads/month (PyPI): 2 344
Downloads/week (PyPI): 719
Forks (GitHub): 12
Stars (GitHub): 62
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.8.1
Downloads/month (PyPI): 2 344
Downloads/week (PyPI): 719
Forks (GitHub): 12
Stars (GitHub): 62
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

API Gateway vs Ableton Live MCP Server
FactAPI GatewayAbleton Live MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)44 (worse)62 (better)
Pulls (Docker Hub) (differs)59 566No figure on Docker Hub
Forks (GitHub)1212
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/api-gateway)On your machine (mcp-server-ableton-live)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/rflpazini/mcp-api-gatewaygithub.com/wstierhout/ableton-live-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

API Gateway

In its own words, on Docker MCP Catalog:

A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.

Ableton Live MCP Server

In its own words, on Official MCP Registry:

Control Ableton Live with 156 typed tools for music production and offline .als analysis.

How to run each

API Gateway As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio mcp-api-gateway -- docker run -i --rm mcp/api-gateway

Ableton Live MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio ableton-live-mcp -- uvx mcp-server-ableton-live

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

Tools each declares

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

Settings each asks for

The marketplaces of Ableton Live MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: API Gateway · What it can do: Ableton Live 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. 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