Ext Ops Panel
Open dashboard
Comparison

io.github.GhostlyGawd/engineering-board vs io.github.formulahendry/spec-driven-development

io.github.GhostlyGawd/engineering-board is an MCP server published by GhostlyGawd. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.formulahendry/spec-driven-development is an MCP server published by formulahendry. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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.GhostlyGawd/engineering-boardio.github.formulahendry/spec-driven-development
Official MCP Registry Listed
Version: 1.14.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 215
Downloads/week (npm): 49
Forks (GitHub): 41
Stars (GitHub): 439
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.GhostlyGawd/engineering-board vs io.github.formulahendry/spec-driven-development
Factio.github.GhostlyGawd/engineering-boardio.github.formulahendry/spec-driven-development
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)439 (better)
Forks (GitHub) (differs)0 (worse)41 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/GhostlyGawd/engineering-board/releases/download/v1.14.0/engineering-board-mcp.mcpb)On your machine (mcp-server-spec-driven-development)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/ghostlygawd/engineering-boardgithub.com/formulahendry/mcp-server-spec-driven-development
Changes in the last 7 days (differs)40
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.GhostlyGawd/engineering-board

In its own words, on Official MCP Registry:

Repository-owned engineering pattern intelligence - 19 MCP tools over stdio.

io.github.formulahendry/spec-driven-development

In its own words, on Official MCP Registry:

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

How to run each

io.github.GhostlyGawd/engineering-board

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

io.github.formulahendry/spec-driven-development As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio spec-driven-development -- npx -y mcp-server-spec-driven-development

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

The marketplaces of io.github.formulahendry/spec-driven-development publish no settings it asks for, so we do not compare settings.

What it can do: io.github.GhostlyGawd/engineering-board · What it can do: io.github.formulahendry/spec-driven-development · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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