mcp-gh-forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SCRIPT_DIR | Yes | Path to the directory containing the shell scripts (e.g., git-orchestrator.sh). |
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 |
|---|---|
| run_forge_macroB | Executes powerful multi-step local Git and cloud GitHub automated scripts (consolidate, get-changed-files, draft-and-save, branch-init, branch-cleanup). |
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 single tool is clearly named and described.
With only one tool, naming consistency is trivially maintained. The tool follows a verb_noun pattern.
A single tool is extremely thin for a server named 'mcp-gh-forge', which implies a broader scope. Packing multiple operations into one macro tool is poor design.
The tool bundles several scripts (consolidate, get-changed-files, etc.) but lacks granular tools for individual operations, making the surface incomplete for typical GitHub automation workflows.