Forge MCP server
Commit Nov 15, 2026An opinionated Go and React framework that enables AI agents to build, test, and deploy full-stack applications and APIs.
Also known as reliant-labs/forge
- Stars
- 10
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is Forge MCP?
Forge is an opinionated Go and React framework that enables AI agents to build, test, and deploy full-stack applications and APIs.
Summary generated from the project's README
About Forge MCP server
Building and deploying full-stack Go and React applications is what Forge enables for AI agents and developers. This framework provides a complete production system from the first commit, including dev environments, testing, secrets management, and observability. It is designed to be driven by any tool capable of running shell commands, such as Claude Code, Cursor, or Aider, as well as through a dedicated MCP server interface.
Users can manage the entire lifecycle locally or remotely. Locally, commands like forge env up dev bring up Postgres, run migrations, and start services with integrated HyperDX observability. For deployment, forge env deploy staging allows for releasing applications to Reliant hosting or a Kubernetes cluster. The system includes built-in guardrails like forge lint to prevent errors and forge scaffold to ensure services and entities are correctly wired into the project structure.
What you can do with it
- 1Scaffold new servicesAn agent can quickly generate a new backend service or database entity with all necessary wiring.
- 2Verify code qualityDevelopers can use automated linting to ensure AI-generated code meets project standards.
- 3Deploy static applicationsUsers can take a Vite or Next.js application and make it live on the web immediately.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablereliant-labs/forge is public and reachablegithub.com/reliant-labs/forge ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/reliant-labs/forge ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubForge
Forge is an opinionated, open-source Go + React framework and deploy platform that ships the production system — dev environments, tests, secrets, multiple environments, releases, observability and hosting — from the first commit, built for AI agents to work in.
Most teams build that system in year two, under deadline, on top of a codebase that wasn't shaped for it. With Forge the first commit already has it, wired into files you own and can change.
Try it in the browser first: the live demo.
Quick start
# Install (macOS / Linux; Windows, Homebrew, npm and go install: see Install below)
curl -fsSL https://raw.githubusercontent.com/reliant-labs/forge/main/install.sh | sh
forge project new my-app && cd my-app
forge scaffold service billing
forge generate
forge env up dev
That last command brings up Postgres, runs your migrations, and starts your
services and frontends, then prints a table of URLs and a log file for each
process, including the HyperDX UI, already receiving the app's traces, metrics
and logs. With a frontend (forge project new my-app --frontend web) it also
starts a local identity provider, so the app's own sign-in page works on the
first run. No signup, no external accounts, no cloud project, no cluster.
Add tables (a // forge:entity message and forge scaffold) and a fresh
database is seeded with foreign-key-coherent rows that satisfy every constraint
your schema declares, so the app boots alive instead of empty.
When you want it online, forge env deploy staging builds a release once and
deploys it. A new project's staging and prod are bound to Reliant hosting; the
same environments deploy to a Kubernetes cluster you run, or as host processes,
by changing where each workload is bound. Before you call a change done:
forge generate && forge lint && go build ./... && task test.
Everything included
What a new app would otherwise stitch together from separate tools:
Every benefit, with how to use it and the code that backs it: docs/benefits.md
Add Reliant and the list grows an agent harness, cloud dev machines, AI code and security review, and an on-call agent. Forge doesn't need any of them.
Built for your agent
When an agent writes most of the code, the bottleneck stops being how fast you
can write it and becomes knowing whether it's right. Forge is one binary on
your PATH with no plugin, editor extension or server, so anything that can run
a shell command can drive it: Claude Code, Codex, Cursor, Copilot, Gemini CLI,
Aider, a harness you wrote, or a CI job. A person at a terminal uses the same
commands, so there is nothing an agent can do that you can't check by hand.
- Skills live in the binary.
forge skill search <topic>andforge skill load <name>print the playbook for an area, about 150 of them, matched to the installed version. Nothing to paste into a prompt, nothing to drift. - It explains itself.
forge startprints the path from an empty directory to authored protos.forge project capabilities --jsonlists every verb, lint analyzer and marker, enumerated from the binary, so it can't go stale. - Scaffolding and lints are guardrails against AI slop.
forge scaffoldlands each service, rpc, worker or entity in the right place, already wired.forge lintrejects what review misses, names the file, line, rule and fix, andforge lint --quietends with the verdict, so the agent reads one line to know whether it is done. - It debugs from real telemetry.
forge obs status,forge obs issuesandforge obs traceread a running app's logs, traces, errors and alerts, so a fix starts from what happened rather than a guess. - Checks never fake a pass. A check that cannot obtain its facts reports UNDETERMINED, never green, never skipped.
- The project tells the agent all of this.
forge project newwritesAGENTS.mdand a pointer for the agent it detects (Claude Code, Cursor, Copilot). Any MCP-capable harness can runforge mcpinstead: see Use as an MCP server.
To use Forge from any agent, put this in the prompt or its instructions file:
Use Forge (github.com/reliant-labs/forge) for this project.
Run `forge start` first and follow it. Load depth with
`forge skill search <topic>` and `forge skill load <name>`.
A change is done when `forge lint`, `go build ./...` and `task test` pass.
Use as an MCP server
forge mcp serves forge over the Model Context Protocol on stdio. It is in the
official MCP registry as io.github.reliant-labs/forge, and npx runs it with
nothing to install, no API key and no config. For Claude Code:
claude mcp add forge -- npx -y @reliantlabs/forge mcp
Or commit a .mcp.json to the project (Cursor reads the same shape from
.cursor/mcp.json):
{
"mcpServers": {
"forge": {
"command": "npx",
"args": ["-y", "@reliantlabs/forge", "mcp"]
}
}
}
For Codex (CLI, IDE extension and desktop app share the config):
codex mcp add forge -- npx -y @reliantlabs/forge mcp
or in ~/.codex/config.toml (or a trusted project's .codex/config.toml):
[mcp_servers.forge]
command = "npx"
args = ["-y", "@reliantlabs/forge", "mcp"]
For Gemini CLI, this repository is an extension (gemini-extension.json):
gemini extensions install https://github.com/reliant-labs/forge
deploy_claimable puts a Vite app or a Next.js static export live with no
account and returns its URL plus a claim link that is good for 72 hours. The
other tools introspect the project, read the skill catalog, and run lint and
generate. Every tool, and the config for Codex: docs/mcp.md.
Opinionated, never a wall
The opinions come from a principal engineer with more than a decade of building reliable systems, and several exist because the unsafe version caused a real incident:
- An error message once shipped a database password to an unauthenticated
caller. Now
svcerr.Wrapreplaces unrecognized errors withinternal server errorand keeps the original server-side. - Images built on an arm64 laptop once got pushed to amd64 nodes. Now cloud
targets require an explicit
platform, and it fails at author time. - Replicas once half-migrated a schema. Now migrations apply from an initContainer under a Postgres advisory lock, and a failed one stalls the rollout with the old pods still serving.
Every default is overridable and every generated file has an owned seam beside it:
- An ORM you can drop out of to raw SQL.
- A middleware chain in a
serve.goyou own and can reorder. pkg/as a library you import, not a framework you live inside.- Each workload binds to a host process, Compose, a cluster you operate or Reliant hosting, in the same KCL. It deploys code it never compiled, in any language: our own control plane builds three services out of a separate repository that Forge never compiles.
More in docs/concepts.md.
Who this isn't for
- You don't want generated code in your repo. Forge writes real files and regenerates them; if you'd rather hand-author everything, the ownership model is overhead.
- You need a REST-first public API. Connect RPC is the native surface; REST URLs are available via Vanguard, but a hand-shaped OpenAPI contract works against the grain.
- Postgres isn't your database. MySQL, SQLite and non-relational stores aren't supported.
- Your backend isn't a container. A service deploys as an image (static sites are the exception: they ship as files).
- You want a framework you'll outgrow and replace. Forge holds structure for the life of the project; for a one-time scaffold, use a template repo.
Install
All of them give you a single forge binary; none needs a C toolchain.
# macOS / Linux (amd64, arm64): no sudo, no prompts, checks the release's sha256
curl -fsSL https://raw.githubusercontent.com/reliant-labs/forge/main/install.sh | sh
# Windows (amd64, arm64)
irm https://raw.githubusercontent.com/reliant-labs/forge/main/install.ps1 | iex
# Homebrew (macOS and Linux)
brew install reliant-labs/reliant/forge
# npm / npx: downloads the same verified binary on first run
npx @reliantlabs/forge version
# Go toolchain
go install github.com/reliant-labs/forge/cmd/forge@latest
To install forge's agent skill with skills.sh: npx skills add reliant-labs/forge --skill forge
Pinning a version for CI, verifying a release's signature, and building from a clone: docs/install.md.
Learn more
- Forge user guide: quick start, project anatomy, environments and deploys, hosting, secrets, domains, observability, troubleshooting
- docs/getting-started.md: the first journey from a checkout, and which files are yours
- docs/concepts.md: why Forge is shaped this way
- docs/benefits.md: every benefit, how to use it and the code that backs it
- docs/mcp.md:
forge mcpfor Claude Code, Codex and Cursor - CONTRIBUTING.md: the dev loop, pre-commit hooks and PR process
License
Copyright 2025-2026 Reliant Labs, Inc. Licensed under the
Apache License, Version 2.0; see also NOTICE. That
covers all of forge: the CLI, the github.com/reliant-labs/forge/pkg/...
libraries your services import, the KCL modules, and the
@reliantlabs/forge-web-runtime npm package your frontends bundle.
Earlier versions. Forge versions published before this change were
released under the Business Source License 1.1. Reliant Labs, Inc., as their
copyright holder, also licenses every one of those versions — every commit of
this repository, tagged or not, and every published version of
@reliantlabs/forge-web-runtime — under the Apache License, Version 2.0. You
may use any of them under either license.
What forge writes into your project is yours. Generated code, scaffolded
files, and the components forge copies into your frontends become part of
your project. Where any of that output reproduces or derives from forge's own
templates or component library, Reliant Labs, Inc. grants you a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable license to use,
reproduce, modify, sublicense and distribute it under terms of your choice,
without any obligation to carry forge's license text, NOTICE or other
attribution. This grant covers that output only. Forge itself, including the
libraries and packages your project depends on, stays under the Apache
License 2.0.
Forge MCP questions
How do I use Forge with an AI agent?
You can use Forge from any agent that can run shell commands, such as Claude Code, Cursor, or Copilot, by running its CLI commands.
How can I run Forge as an MCP server?
You can run forge mcp to serve Forge over the Model Context Protocol on stdio using npx.
Does using Forge as an MCP server require an API key?
No, it can be run with npx without any API key or configuration.
What happens when I run `forge env up dev`?
It brings up Postgres, runs migrations, starts services and frontends, and provides a table of URLs and log files, including the HyperDX UI.