PlanExe vs DevPlan MCP Server
PlanExe is an MCP server published by PlanExeOrg. Marketplaces we read that list it: 1 (Official MCP Registry). DevPlan MCP Server is an MCP server published by mmorris35. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 66 Stars (GitHub): 403 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 4 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
| Fact | PlanExe | DevPlan MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 403 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 66 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.planexe.org/mcp) | Remote server (devplan-mcp-server.mike-c63.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/planexeorg/planexe | github.com/mmorris35/devplan-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Answered with HTTP 301 (3 h 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
PlanExe
MCP server for generating rough-draft project plans from natural-language prompts.
DevPlan MCP Server
Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.
How to run each
PlanExe As a remote MCP server
claude mcp add --transport http planexe https://mcp.planexe.org/mcp --header "X-API-Key: <YOUR_X_API_KEY>"
Requires: X-API-Key header
DevPlan MCP Server As a remote MCP server
claude mcp add --transport http devplan-mcp-server https://devplan-mcp-server.mike-c63.workers.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only DevPlan 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
Neither one's marketplaces publish the settings it asks for.
What it can do: PlanExe · What it can do: DevPlan MCP Server · 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.