Angular PR Review MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PR_REVIEW_REPO_ROOT | No | Override repository root (default current working directory) | . |
| PR_REVIEW_OUTPUT_DIR | No | Review artifacts directory (default 'pr_review' under repo root) | pr_review |
| PR_REVIEW_BASE_BRANCH | No | Target base branch for comparison (default 'main') | main |
| PR_REVIEW_SERVER_NAME | No | MCP server name (default 'angular-pr-review') | angular-pr-review |
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 |
|---|---|
| get_pr_review_templateB | Return the local Angular PR review template used to keep review rules consistent and token-efficient. |
| generate_pr_diffB | Generate a PR review diff for a validated Git commit hash and return the resulting diff file path. |
| read_pr_diffA | Read the most recently generated PR diff file, or a specific diff by commit hash/file path. |
| save_pr_reviewB | Save a completed review as a markdown report inside the configured output folder. |
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 4 tools
Each tool serves a distinct purpose: fetching the review template, generating a diff, reading a diff, and saving a review. There is no overlap or ambiguity in their functionalities.
All tools follow a consistent verb_noun pattern (get, generate, read, save) with clear object references. The only minor deviation is that 'get_pr_review_template' and 'generate_pr_diff' could be seen as slightly more specific verbs, but they are still consistent with the overall style.
With 4 tools, the server is well-scoped for a focused PR review workflow. Each tool covers an essential step: template retrieval, diff generation, diff reading, and saving results, without unnecessary extras.
The tool surface covers the core workflow of generating and reviewing a PR diff. However, a minor gap might be the lack of a tool to fetch PR metadata or commit details beyond the diff, but the current set is sufficient for the stated purpose.