Ext Ops Panel
Open dashboard
Comparison

Glean Remote MCP Server vs Context Engine

Glean Remote MCP Server is an MCP server published by glean.com. Marketplaces we read that list it: 1 (Official MCP Registry). Context Engine is an MCP server published by melonelish. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceGlean Remote MCP ServerContext Engine
Official MCP Registry Listed
Version: 1.2.1
Forks (GitHub): 3
Stars (GitHub): 166
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (PyPI): 73
Downloads/week (PyPI): 16
Forks (GitHub): 1
Stars (GitHub): 329
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

Glean Remote MCP Server vs Context Engine
FactGlean Remote MCP ServerContext Engine
Marketplaces that list it11
Stars (GitHub) (differs)166 (worse)329 (better)
Forks (GitHub) (differs)3 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Not statedOn your machine (melonelish-context-engine)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/gleanwork/remote-mcp-servergithub.com/melonelish/context-engine
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

Glean Remote MCP Server

In its own words, on Official MCP Registry:

Remote MCP Server that securely connects Glean Enterprise Knowledge with your IDE, LLM, or agents.

Context Engine

In its own words, on Official MCP Registry:

Compress logs, retrieval chunks, and code context into structured LLM-ready signal.

How to run each

Glean Remote MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Context Engine As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio context-engine -- uvx melonelish-context-engine

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

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Glean Remote MCP Server · What it can do: Context Engine · Compare two other plugins

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