ForgeMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGEMCP_WORKSPACE | Yes | Must name an existing workspace directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_statusA | Return ForgeMCP version, workspace, lifecycle state, and Core services. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as returning status information.
With a single tool, there is no pattern to violate. The name server_status is descriptive and follows snake_case, which is a common convention.
A single tool feels thin for a server named ForgeMCP, which implies a broader scope. The tool provides status information but lacks other expected operations, making the count borderline.
The server exposes only a status endpoint, with no other tools for managing Forge or interacting with core services. This is a significant gap if the server is intended to provide a functional MCP surface.