mcp-merge-guard
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-merge-ready | Check if a PR is ready to merge by validating CI status, approvals, and conflicts |
| guard-mergeA | Validate guards and merge PR only if all pass (atomic operation) |
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
With only one tool, there is no possibility of confusion between tools. The single tool has a clearly distinct purpose.
The single tool name 'guard-merge' follows a consistent verb_noun pattern, making it clear and predictable.
The server has only one tool, which is on the low end of appropriate scope. While focused, it feels thin for typical server expectations.
The server only offers an atomic guard-and-merge operation, lacking separate validation or configuration tools. This creates significant gaps for an agent that might need to validate guards without merging.