Ext Ops Panel
Open dashboard
Comparison

io.github.dversum/mcp-server vs io.github.theYahia/megaplan-mcp

io.github.dversum/mcp-server is an MCP server published by dversum. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.theYahia/megaplan-mcp is an MCP server published by theYahia. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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.dversum/mcp-serverio.github.theYahia/megaplan-mcp
Official MCP Registry Listed
Version: 2.0.0
Downloads/month (npm): 593
Downloads/week (npm): 139
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Downloads/month (npm): 143
Downloads/week (npm): 18
Forks (GitHub): 1
Stars (GitHub): 2
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

io.github.dversum/mcp-server vs io.github.theYahia/megaplan-mcp
Factio.github.dversum/mcp-serverio.github.theYahia/megaplan-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@dversum/mcp-server)On your machine (@theyahia/megaplan-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/dversum/mcp-servergithub.com/theyahia/megaplan-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

io.github.dversum/mcp-server

In its own words, on Official MCP Registry:

Manage clients, projects, tasks, invoices, time tracking & calendar in dVersum.

io.github.theYahia/megaplan-mcp

In its own words, on Official MCP Registry:

MCP server for Megaplan — tasks, deals management via API v3.

How to run each

io.github.dversum/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "DVERSUM_API_TOKEN=<YOUR_DVERSUM_API_TOKEN>" --env "DVERSUM_API_URL=<YOUR_DVERSUM_API_URL>" --transport stdio io-github-dversum-mcp-server -- npx -y @dversum/mcp-server

Requires: DVERSUM_API_TOKEN (secret), DVERSUM_API_URL

io.github.theYahia/megaplan-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "MEGAPLAN_DOMAIN=<YOUR_MEGAPLAN_DOMAIN>" --transport stdio megaplan-mcp -- npx -y @theyahia/megaplan-mcp

Requires: MEGAPLAN_DOMAIN (secret)

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

Only io.github.dversum/mcp-server asks for

  • DVERSUM_API_TOKEN (secret)
  • DVERSUM_API_URL

Only io.github.theYahia/megaplan-mcp asks for

  • MEGAPLAN_DOMAIN (secret)

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

What it can do: io.github.dversum/mcp-server · What it can do: io.github.theYahia/megaplan-mcp · 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