AI-Code-Reviewer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Gemini API key from Google AI Studio |
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 |
|---|---|
| pingA | Health check — confirms the server is reachable and responding over MCP. |
| explain_conventionA | Answer a question about a repo's own coding conventions, grounded in chunks retrieved from that repo's indexed code/docs/config (run index_repo first). |
| get_index_statusA | Report whether a repo has been indexed, whether the index is stale relative to its current HEAD commit, and basic index size stats. |
| index_repoA | Index (or incrementally re-index) a local git repository's source, docs, and lint/format config so its own conventions can be retrieved during review. Only files whose git blob sha changed since the last index are re-chunked/re-embedded, unless force=True. |
| review_diffA | Review a diff against this repo's own conventions, grounded via RAG over its
indexed code/docs/config (run index_repo first). If |
| review_fileA | Whole-file review — a simpler fallback that reuses the same review pipeline as review_diff, with the entire file synthesized as an all-added unified diff. |
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 6 tools
Each tool serves a distinct purpose: ping for health, index_repo for indexing, get_index_status for checking indexing state, explain_convention for Q&A on conventions, and review_diff/review_file for reviewing code changes. No two tools overlap in functionality.
Most tool names follow a consistent verb_noun pattern (e.g., index_repo, review_diff), but 'ping' deviates as a noun-only name. This minor inconsistency is acceptable.
With 6 tools, the server is well-scoped for its purpose of indexing and reviewing code conventions. Each tool earns its place, covering indexing, status, health, and two review methods.
The tool set covers the core workflow (index, check status, review diff/file, explain conventions). Missing a tool to retrieve all conventions or clear the index are minor gaps, but the essential review cycle is complete.