Forge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-Forge-Site | No | Optional project default: the Forge site id to use when the agent omits `site_id`. Must be a literal value; an empty header value makes every call fail. | |
| FORGE_MCP_URL | Yes | Public HTTPS URL of your self-hosted Forge MCP app; the MCP endpoint is `${FORGE_MCP_URL}/mcp`. Always serve it over HTTPS, since access tokens travel in a header. | |
| X-Forge-Server | No | Optional project default: the Forge server id to use when the agent omits `server_id`. Must be a literal value; an empty header value makes every call fail. | |
| FORGE_MCP_TOKEN | Yes | Access token created in the Forge MCP dashboard (Access tokens), sent as `Authorization: Bearer <token>`. It is shown only once and carries the token's per-capability permissions (read-only by default). | |
| X-Forge-Organization | No | Optional project default: the Forge organization to use when the agent omits the `organization` argument. Must be a literal value (not an environment variable), since an empty header value makes every call fail with `Invalid X-Forge-… header.` |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues