Ext Ops Panel
Open dashboard
Comparison

mcp-tunnels vs MisarDev MCP Server

mcp-tunnels is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). MisarDev MCP Server is an MCP server published by Misar-AI. 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
Marketplacemcp-tunnelsMisarDev MCP Server
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 658
Stars (GitHub): 44 447
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

mcp-tunnels vs MisarDev MCP Server
Factmcp-tunnelsMisarDev MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)44 447 (better)0 (worse)
Forks (GitHub) (differs)4 658 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.misar.io/dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/misar-ai/misardev-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

mcp-tunnels

In its own words, on Claude Code: claude-plugins-official:

Connect Claude to a private MCP server through an Anthropic MCP tunnel. The /create-docker-mcp-tunnel command drives the Docker Compose quickstart end to end: certificates, proxy config, cloudflared, and a verifiable sample server.

MisarDev MCP Server

In its own words, on Official MCP Registry:

Create, build and deploy projects, roll back with checkpoints, connect custom domains, and search…

How to run each

mcp-tunnels As a Claude Code plugin

Claude Code
/plugin install mcp-tunnels@claude-plugins-official

MisarDev MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http misardev-mcp https://api.misar.io/dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MISARDEV_API_KEY (secret), Authorization header

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

Only MisarDev 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

The marketplaces of mcp-tunnels publish no settings it asks for, so we do not compare settings.

What it can do: mcp-tunnels · What it can do: MisarDev MCP Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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