Ext Ops Panel
Open dashboard
Comparison

Chroma vs TimeBase

Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). TimeBase is an MCP server published by epam. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-13. 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
MarketplaceChromaTimeBase
Docker MCP Catalog Listed
Version: sha256:c050ca8e1d4e
Forks (GitHub): 117
Pulls (Docker Hub): 59 187
Stars (Docker Hub): 5
Stars (GitHub): 600
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.6
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.1.7
Forks (GitHub): 0
Stars (GitHub): 7
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

Chroma vs TimeBase
FactChromaTimeBase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)600 (better)8 (worse)
Pulls (Docker Hub) (differs)59 187No figure on Docker Hub
Forks (GitHub) (differs)117 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/chroma)On your machine (timebase-mcp)
Transportstdiostdio
Tools it declares (differs)13Not published
Environment variables it asks for (differs)1, secrets among them: 115, secrets among them: 2
Parts of the bundle (differs)Not a bundle8
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/chroma-core/chroma-mcpgithub.com/epam/timebase-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

Chroma

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma.

TimeBase

In its own words, on Official MCP Registry:

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

How to run each

Chroma As a local MCP server: Docker image

Claude Code
claude mcp add --env "CHROMA_API_KEY=<YOUR_CHROMA_API_KEY>" --transport stdio chroma -- docker run -i --rm -e CHROMA_API_KEY mcp/chroma

Requires: CHROMA_API_KEY (secret)

TimeBase As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIMEBASE_OAUTH2_CLIENT_SECRET=<YOUR_TIMEBASE_OAUTH2_CLIENT_SECRET>" --env "TIMEBASE_PASSWORD=<YOUR_TIMEBASE_PASSWORD>" --transport stdio timebase-mcp -- uvx --from "timebase-mcp[all]" timebase-mcp

Requires: TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_PASSWORD (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 TimeBase publish no list of tools, so we do not compare tools.

Settings each asks for

Only Chroma asks for

  • CHROMA_API_KEY (secret)

Only TimeBase asks for

  • MCP_AUTH_API_KEYS_FILE
  • MCP_AUTH_AUDIENCE
  • MCP_AUTH_PUBLIC_URL
  • MCP_HOST
  • MCP_LOG_LEVEL
  • MCP_PORT
  • TIMEBASE_AUTH_MODE
  • TIMEBASE_OAUTH2_CLIENT_ID
  • TIMEBASE_OAUTH2_CLIENT_SECRET (secret)
  • TIMEBASE_OAUTH2_SCOPE
  • TIMEBASE_OAUTH2_TOKEN_URL
  • TIMEBASE_PASSWORD (secret)
Show the remaining 3
  • TIMEBASE_SERVERS
  • TIMEBASE_URL
  • TIMEBASE_USERNAME

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

What it can do: Chroma · What it can do: TimeBase · 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. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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