Ext Ops Panel
Open dashboard
Comparison

context-provider vs ContextStream MCP Server

context-provider is a plugin bundle for AI coding tools published by doobidoo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ContextStream MCP Server is an MCP server published by contextstream. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacecontext-providerContextStream MCP Server
Community marketplace doobidoo/mcp-context-provider Listed
Version: 2.0.0-alpha.4
Forks (GitHub): 8
Stars (GitHub): 31
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.28
Downloads/month (npm): 7 686
Downloads/week (npm): 1 269
Forks (GitHub): 12
Stars (GitHub): 44
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

context-provider vs ContextStream MCP Server
Factcontext-providerContextStream MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)31 (worse)44 (better)
Forks (GitHub) (differs)8 (worse)12 (better)
Last release (differs)Not published2026-10-22
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 02, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/doobidoo/mcp-context-providergithub.com/contextstream/mcp-server
Changes in the last 7 days (differs)04
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago

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

context-provider

In its own words, on Community GitHub marketplaces:

MCP server that provides tool-aware context injection and learned instincts with confidence scoring. Includes 6 MCP tools: get_tool_context, get_syntax_rules, list_available_contexts, apply_auto_corrections, build_injection, and list_instincts.

ContextStream MCP Server

In its own words, on Official MCP Registry:

Project memory, semantic code search, and grounded agent context.

How to run each

context-provider As a Claude Code plugin

Claude Code
/plugin marketplace add doobidoo/mcp-context-provider
/plugin install context-provider@mcp-context-provider

ContextStream MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http contextstream-mcp-server https://mcp.contextstream.io/mcp

Requires: CONTEXTSTREAM_API_KEY (secret)

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

Only ContextStream MCP Server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only context-provider asks for

  • CONTEXTS_PATH
  • INSTINCTS_PATH

Only ContextStream MCP Server asks for

  • CONTEXTSTREAM_API_KEY (secret)
  • CONTEXTSTREAM_API_URL

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

What it can do: context-provider · What it can do: ContextStream MCP Server · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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