Forge Engine vs Spec Driven Development
A side-by-side look at the Forge Engine and Spec Driven Development MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Forge Engine for coding agents work as a local process; choose Spec Driven Development for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Forge Engine when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Choose Spec Driven Development when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 40/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 439 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Forge Engine | View Spec Driven Development |
Tools & capabilities
Forge Engine tools
No tool names declared yet. Check the project README from the listing page.
Spec Driven Development tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Forge Engine
{
"mcpServers": {
"forge-engine-2": {
"command": "npx",
"args": [
"-y",
"@forgeengine/cli"
]
}
}
}
Spec Driven Development
{
"mcpServers": {
"spec-driven-development": {
"command": "npx",
"args": [
"-y",
"mcp-server-spec-driven-development@latest"
]
}
}
}