forge-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@forge-mcpList the available templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
forge-mcp
Read-only MCP server that gives Claude Code structured knowledge about the Forge repository, including its templates, project structure, documentation, validation rules, doctor checks, and generated-project conventions.
Forge remains the authoritative application. forge-mcp reads Forge; it does not modify it.
v0.1.1 has no write tools.
Related MCP server: Codelens-MCP
Tools
Tool | Purpose |
| Forge version, CLI entry point, capabilities, templates, doc availability |
| Available local templates with metadata |
| One template: purpose, language, files, variables, output structure |
| Sorted file listing for one template |
| Read a text file inside a template |
| Generated-project conventions per template type |
| Validation commands as inert strings (never executed) |
| Read approved Forge docs by stable identifier |
| Doctor checks, required/optional, overall success rule |
| Source-backed process for changing a Forge template |
Requirements
Python 3.10+
Forge repository at a known path
FORGE_REPOSITORY_ROOTenvironment variable or--forge-rootCLI argument
Installation
cd forge-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"Usage
# Set the Forge root and run the server over stdio
FORGE_REPOSITORY_ROOT=/srv/workspaces/projects/portfolio/forge forge-mcp
# Or pass it explicitly
forge-mcp --forge-root /srv/workspaces/projects/portfolio/forge
# Version check
forge-mcp --version
python -m forge_mcp --versionClaude Code setup
See docs/claude-code-setup.md and examples/claude-code.mcp.json.
Development
python -m pytest -q
python -m ruff check src/ tests/Document availability
get_forge_overview distinguishes between documents that are approved in the allowlist and documents that are currently present on disk:
available_documents— approved identifiers whose files exist in the Forge repository right nowunavailable_documents— approved identifiers configured in the allowlist but whose files are absent
Both fields are always present. Both are sorted alphabetically by identifier. The union of the two sets always equals the full approved-document allowlist.
read_forge_document accepts only approved identifiers. It returns a structured error with code DOCUMENT_NOT_FOUND when the identifier is unknown or the file is absent, and DOCUMENT_ERROR for other read failures (binary content, size limit, encoding). It never accepts arbitrary paths.
Security
forge-mcp is strictly read-only. See docs/security-boundary.md.
Separation
Forge is a separate repository and application. forge-mcp does not modify Forge. forge-mcp does not import Forge modules, execute Forge commands, or touch Forge's Git history.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qmcclellan/forge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server