Yellhorn MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPO_PATH | No | Path to your repository | current directory |
| GEMINI_API_KEY | Yes | Your Gemini API key | |
| YELLHORN_MCP_MODEL | No | Gemini model to use | gemini-2.5-pro-exp-03-25 |
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 |
|---|---|
| create_workplanA | Creates a GitHub issue with a detailed implementation plan. This tool will:
The AI will analyze your entire codebase (respecting .gitignore) to create a detailed plan with:
Codebase reasoning modes:
Returns the created issue URL and number immediately. |
| get_workplanB | Retrieves the workplan content (GitHub issue body) for a specified issue number. |
| revise_workplanA | Updates an existing workplan based on revision instructions. This tool will:
The AI will use the same codebase analysis mode and model as the original workplan. Returns the issue URL and number immediately. |
| curate_contextA | Analyzes the codebase and creates a .yellhorncontext file listing directories to be included in AI context. This tool helps optimize AI context by:
The .yellhorncontext file acts as a whitelist - only files matching the patterns will be included. This significantly reduces token usage and improves AI focus on relevant code. Example .yellhorncontext: src/api/ src/models/ tests/api/ *.config.js |
| judge_workplanA | Triggers an asynchronous code judgement comparing two git refs against a workplan. This tool will:
The judgement will evaluate:
Supports comparing:
Returns the sub-issue URL immediately. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/msnidal/yellhorn-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server