Code Reader MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub fine-grained personal access token with read-only access to repositories. | |
| SERVICES_CONFIG | Yes | JSON array of service configurations with name, repoOwner, repoName, automationRepoPath, apiPatterns. | |
| DEFAULT_BASE_BRANCH | No | Default base branch for comparing branches. | master |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_servicesB | List all configured services and their automation repo paths |
| get_api_changesB | Get API changes between two branches or commits for a service. Detects new/modified API endpoints. |
| get_api_detailsC | Get the full content of an API file for detailed analysis |
| get_recent_commitsC | Get recent commits for a service to identify recent changes |
| get_pull_requestsC | Get pull requests for a service to find API changes in PRs |
| analyze_api_endpointC | Analyze an API file and extract all endpoint definitions with their methods, paths, and handlers |
| get_test_templateC | Get a test template based on API type and service |
| compare_branchesC | Compare two branches and get a summary of all changes including API-related files |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| example-service Automation Repo | Automation repository for example-service at /app |
TDQS
Scored across 8 tools
Most tools target distinct actions (listing services, comparing branches, extracting commits/PRs, analyzing API files). However, compare_branches and get_api_changes overlap in comparing branches for API-related changes, which could cause misselection, though descriptions provide some differentiation.
All tool names use consistent snake_case and a verb_noun pattern (list_services, get_api_changes, analyze_api_endpoint, compare_branches). The verbs vary appropriately by action without breaking the pattern.
8 tools is well-scoped for a code/API reading server; each tool covers a distinct read or analysis operation without obvious redundancy.
The surface covers service listing, branch/commit/PR inspection, API diffing, API file retrieval, endpoint analysis, and test templates. Minor gaps exist, such as general file search or branch listing, but core API-change workflows are covered.