Simple Merge Review MCP
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 |
|---|---|
| show_merge_diffA | Show changes between branches before merge |
| quick_merge_summaryB | Quick summary of changes for merge |
| show_file_diffB | Show specific changes in a file between branches |
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 clear, distinct purpose: one provides a summary, one shows diffs for a specific file, and one shows the overall diff between branches. There is no overlap or ambiguity.
All tools use snake_case and start with a descriptive term. However, 'quick_merge_summary' uses an adjective, while the others use a verb, creating a slight inconsistency in pattern.
With only 3 tools, the server is well-scoped for its purpose of simple merge review. Each tool is essential and nothing seems unnecessary or missing.
The tools cover the core needs for merge review: a summary, overall diff, and file-level diff. Minor features like listing changed files or branch management are not present but are not essential for the minimal scope.