Ext Ops Panel
Open dashboard
Comparison

io.github.Couchbase-Ecosystem/mcp-server-couchbase vs InfluxDB 3

io.github.Couchbase-Ecosystem/mcp-server-couchbase is an MCP server published by Couchbase-Ecosystem. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). InfluxDB 3 is an MCP server published by influxdata. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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.Couchbase-Ecosystem/mcp-server-couchbaseInfluxDB 3
Official MCP Registry Listed, marked deprecated
Version: 0.8.0
Downloads/month (PyPI): 1 200
Downloads/week (PyPI): 261
Forks (GitHub): 34
Stars (GitHub): 34
Not marked · First seen
Listed
Version: 2.0.0
Downloads/month (npm): 854
Downloads/week (npm): 164
Forks (GitHub): 14
Stars (GitHub): 38
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:85a104706d8b
Forks (GitHub): 34
Pulls (Docker Hub): 36 930
Stars (Docker Hub): 4
Stars (GitHub): 34
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 1.0.1.post1
Downloads/month (PyPI): 1 200
Downloads/week (PyPI): 261
Forks (GitHub): 34
Stars (GitHub): 34
Not marked · First seen
Not listed

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.Couchbase-Ecosystem/mcp-server-couchbase vs InfluxDB 3
Factio.github.Couchbase-Ecosystem/mcp-server-couchbaseInfluxDB 3
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)34 (worse)38 (better)
Pulls (Docker Hub) (differs)36 930No figure on Docker Hub
Forks (GitHub) (differs)34 (better)14 (worse)
Last release (differs)Not published2026-10-27
Where it runs (differs)On your machine (couchbase-mcp-server)On your machine (@influxdata/influxdb3-mcp-server)
Transportstdiostdio
Tools it declares (differs)20Not published
Environment variables it asks for (differs)33, secrets among them: 17, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/couchbase-ecosystem/mcp-server-couchbasegithub.com/influxdata/influxdb3_mcp_server
Changes in the last 7 days (differs)01
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

io.github.Couchbase-Ecosystem/mcp-server-couchbase

In its own words, on Official MCP Registry:

Couchbase Model Context Protocol Server to interact with Couchbase clusters

InfluxDB 3

In its own words, on Official MCP Registry:

Official InfluxDB 3 MCP server: query, write and manage Core, Enterprise and Cloud databases.

How to run each

io.github.Couchbase-Ecosystem/mcp-server-couchbase As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CB_PASSWORD=<YOUR_CB_PASSWORD>" --transport stdio mcp-server-couchbase -- uvx couchbase-mcp-server

Requires: CB_PASSWORD (secret)

InfluxDB 3 As a local MCP server: npm package

Claude Code
claude mcp add --env "INFLUX_DB_MANAGEMENT_TOKEN=<YOUR_INFLUX_DB_MANAGEMENT_TOKEN>" --env "INFLUX_DB_PRODUCT_TYPE=<YOUR_INFLUX_DB_PRODUCT_TYPE>" --env "INFLUX_DB_TOKEN=<YOUR_INFLUX_DB_TOKEN>" --transport stdio influxdb3-mcp-server -- npx -y @influxdata/influxdb3-mcp-server

Requires: INFLUX_DB_MANAGEMENT_TOKEN (secret), INFLUX_DB_PRODUCT_TYPE, INFLUX_DB_TOKEN (secret)

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

Tools each declares

The marketplaces of InfluxDB 3 publish no list of tools, so we do not compare tools.

Settings each asks for

Only io.github.Couchbase-Ecosystem/mcp-server-couchbase asks for

  • CB_BUCKET_NAME
  • CB_CA_CERT_PATH
  • CB_CLIENT_CERT_PATH
  • CB_CLIENT_KEY_PATH
  • CB_CONNECTION_STRING
  • CB_MCP_CONFIRMATION_REQUIRED_TOOLS
  • CB_MCP_DISABLED_TOOLS
  • CB_MCP_HOST
  • CB_MCP_LOG_DEBUG_RETENTION_BACKUP_COUNT
  • CB_MCP_LOG_DEBUG_ROTATION_MAX_SIZE_MB
  • CB_MCP_LOG_ERROR_RETENTION_BACKUP_COUNT
  • CB_MCP_LOG_ERROR_ROTATION_MAX_SIZE_MB
Show the remaining 23
  • CB_MCP_LOG_FILE
  • CB_MCP_LOG_INFO_RETENTION_BACKUP_COUNT
  • CB_MCP_LOG_INFO_ROTATION_MAX_SIZE_MB
  • CB_MCP_LOG_LEVEL
  • CB_MCP_LOG_MAX_BYTES
  • CB_MCP_LOG_RETENTION_BACKUP_COUNT
  • CB_MCP_LOG_ROTATION_MAX_SIZE_MB
  • CB_MCP_LOG_SINKS
  • CB_MCP_LOG_WARNING_RETENTION_BACKUP_COUNT
  • CB_MCP_LOG_WARNING_ROTATION_MAX_SIZE_MB
  • CB_MCP_OAUTH_JWT_ALGORITHM
  • CB_MCP_OAUTH_JWT_AUDIENCE
  • CB_MCP_OAUTH_JWT_ISSUER
  • CB_MCP_OAUTH_JWT_JWKS_URI
  • CB_MCP_OAUTH_MCP_BASE_URL
  • CB_MCP_OAUTH_SCOPE_READ_LABEL
  • CB_MCP_OAUTH_SCOPE_WRITE_LABEL
  • CB_MCP_PORT
  • CB_MCP_READ_ONLY_MODE
  • CB_MCP_READ_ONLY_QUERY_MODE
  • CB_MCP_TRANSPORT
  • CB_PASSWORD (secret)
  • CB_USERNAME

Only InfluxDB 3 asks for

  • INFLUX_DB_ACCOUNT_ID
  • INFLUX_DB_CLUSTER_ID
  • INFLUX_DB_INSTANCE_URL
  • INFLUX_DB_MANAGEMENT_TOKEN (secret)
  • INFLUX_DB_PRODUCT_TYPE
  • INFLUX_DB_TOKEN (secret)
  • INFLUX_MCP_TOOL_PROFILE

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

What it can do: io.github.Couchbase-Ecosystem/mcp-server-couchbase · What it can do: InfluxDB 3 · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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