Ext Ops Panel
Open dashboard
Comparison

API Gateway vs com.jamesrosingmd/tebra

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.jamesrosingmd/tebra is an MCP server published by jamesrosingmd.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 Gatewaycom.jamesrosingmd/tebra
Docker MCP Catalog Listed
Version: sha256:9cc67b4a037f
Forks (GitHub): 12
Pulls (Docker Hub): 58 945
Stars (Docker Hub): 6
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.5
Downloads/month (npm): 1 889
Downloads/week (npm): 162
Forks (GitHub): 2
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

API Gateway vs com.jamesrosingmd/tebra
FactAPI Gatewaycom.jamesrosingmd/tebra
Marketplaces that list it11
Stars (GitHub) (differs)44 (better)1 (worse)
Pulls (Docker Hub) (differs)58 945No figure on Docker Hub
Forks (GitHub) (differs)12 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/api-gateway)On your machine (tebra-mcp-server)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)3, secrets among them: 03, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/rflpazini/mcp-api-gatewaygithub.com/jamesrosing/tebra-mcp-server
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.

com.jamesrosingmd/tebra

In its own words, on Official MCP Registry:

MCP server for Tebra/Kareo practice management — patients, billing, scheduling, FHIR (45 tools)

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

com.jamesrosingmd/tebra As a local MCP server: npm package

Claude Code
claude mcp add --env "TEBRA_CUSTOMER_KEY=<YOUR_TEBRA_CUSTOMER_KEY>" --env "TEBRA_SOAP_PASSWORD=<YOUR_TEBRA_SOAP_PASSWORD>" --env "TEBRA_SOAP_USER=<YOUR_TEBRA_SOAP_USER>" --transport stdio tebra -- npx -y tebra-mcp-server

Requires: TEBRA_CUSTOMER_KEY (secret), TEBRA_SOAP_PASSWORD (secret), TEBRA_SOAP_USER

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

Tools each declares

The marketplaces of com.jamesrosingmd/tebra publish no list of tools, so we do not compare tools.

Settings each asks for

Only API Gateway asks for

  • API_1_HEADER_AUTHORIZATION
  • API_1_NAME
  • API_1_SWAGGER_URL

Only com.jamesrosingmd/tebra asks for

  • TEBRA_CUSTOMER_KEY (secret)
  • TEBRA_SOAP_PASSWORD (secret)
  • TEBRA_SOAP_USER

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

What it can do: API Gateway · What it can do: com.jamesrosingmd/tebra · 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