ReviewLens MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVIEWLENS_MODE | No | Set to 'live' for live mode. Default is demo mode. | demo |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pull_requestsC | List open pull requests without changing the repository. |
| get_pull_requestC | Get typed pull-request metadata. |
| get_pull_request_filesC | Get changed files and patches for a pull request. |
| get_pull_request_diffC | Get a bounded, redacted unified diff. |
| search_repository_codeC | Search code in a repository using a bounded query. |
| find_related_testsC | Find test paths related to changed files. |
| build_review_reportC | Build deterministic structured evidence; never asks an LLM for a verdict. |
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 7 tools
Each tool has a mostly distinct purpose: listing PRs, fetching metadata, fetching diffs/files, finding tests, searching code, and building a report. The main overlap is between get_pull_request_diff and get_pull_request_files, since both expose changed content, though the descriptions distinguish unified diff from file-level patches.
All tools use a consistent snake_case verb_noun pattern, such as get_pull_request, list_pull_requests, find_related_tests, and build_review_report. The naming is predictable and easy to scan.
Seven tools are well-scoped for a read-only PR review/evidence server. Each tool supports a clear part of the review workflow, and there is no obvious bloat.
The surface covers core read-only review needs: listing PRs, fetching metadata, diffs, changed files, related tests, code search, and report generation. Minor gaps remain around existing review comments, CI/check status, or commit context, but the core workflow is workable.