Forge Dev Stack vs com.northerngo/build
Forge Dev Stack is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Forge Dev Stack is a plugin bundle for AI coding tools published by Springthrough. No marketplace we read lists it any more. com.northerngo/build is an MCP server published by northerngo.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.northerngo/build | |
|---|---|---|
| Community marketplace brutalsystems/forge | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | Forge Dev Stackno longer listed · | com.northerngo/build |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (northerngo-backend.onrender.com/api/ng-mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/brutalsystems/forge | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Forge Dev Stack
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Full-lifecycle SDLC orchestrator: a 12-stage pipeline (SRS, architecture, spec, plan, build, eval, deploy, monitor, release) driven by specialized agents, persistent cross-session…
-
Operate and onboard Hack-managed local development environments.
-
Autonomous full-stack application factory for AI coding assistants. Clone this repo into your workspace and your AI assistant — Copilot, Claude, Cursor, Codex, or any…
-
atlassian-forge-skills
Forge-focused skills and MCP configuration for Atlassian Forge: scaffold and deploy apps (forge create, templates, dev spaces), pre-deploy review, systematic debugging, plus Forge…
-
Comprehensive mise skill for Claude Code covering the full mise ecosystem: task definition with usage spec arguments, dev tool management across 18 backends, environment…
-
Forge-focused skills and MCP configuration for Atlassian Forge: scaffold and deploy apps (forge create, templates, dev spaces), build Teamwork Graph connectors for Rovo…
What each says it does
Forge Dev Stack
Set up, diagnose, and operate forge-orchestrated multi-repo dev stacks on macOS, Linux, and Windows
com.northerngo/build
Start a NorthernGo cloud build from Cursor, Claude or Codex. EU database included.
How to run each
Forge Dev Stack
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.northerngo/build As a remote MCP server
claude mcp add --transport http build https://northerngo-backend.onrender.com/api/ng-mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.northerngo/build 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: Forge Dev Stack · What it can do: com.northerngo/build · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.