mcp-forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forge_addA | Fetch a docs URL (OpenAPI / llms.txt / HTML) and forge lean callable tools from it. Returns {tools: names}. |
| forge_listA | List forged tools in the local store. |
| forge_callB | Call a forged tool by name with args. Loads tool JSON from store then executes with timeout + truncation. |
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 3 tools
Each tool has a clearly distinct role: forge_add creates tools from a URL, forge_list enumerates them, and forge_call executes them. There is no overlap or ambiguity between the three operations.
All tools share the forge_ prefix followed by a lowercase imperative verb: add, list, call. The naming is completely consistent and predictable.
Three tools is appropriate for this focused server's scope: one to create tools, one to list them, and one to call them. Each tool earns its place and no extra tool is needed for the core workflow.
The add/list/call workflow covers the essential lifecycle of dynamically forged tools. However, there is no delete or refresh operation, so stale or outdated forged tools cannot be removed.