gitlumen-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host for the optional HTTP server. Default is 0.0.0.0. | |
| PORT | No | Port for the optional HTTP server. Default is 3333. | |
| GITHUB_TOKEN | No | Optional GitHub personal access token for higher rate limits and private repository access. Not required for small/medium public repositories. | |
| MCP_AUTH_TOKEN | No | Optional authorization token for the HTTP server. Clients must send Authorization: Bearer <token>. | |
| GITLUMEN_MCP_DATA_DIR | No | Directory path for storing local reports. Defaults to .gitlumen-mcp in the project root. | |
| GITLUMEN_MAX_FILE_BYTES | No | Maximum file size in bytes to fetch. Default is 120000. |
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 |
|---|---|
| screen_repositoryA | Screen a public GitHub repository or GitHub pull request URL and generate a GitLumen-style risk report. Supports repo URLs and /pull/ URLs. |
| get_review_reportA | Get a previously generated GitLumen MCP report by reportId. |
| list_review_reportsA | List previously generated GitLumen MCP reports stored locally. |
| get_repository_structureA | Fetch public GitHub repository or PR structure without generating a full risk report. |
| explain_gitlumen_mcp_flowA | Explain how this Path 1 MCP server fits into GitLumen and how it later connects to Base MCP Path 2. |
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 5 tools
Each tool has a clearly distinct purpose: generating reports, retrieving specific reports, listing reports, fetching repository structure, and explaining the flow. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., screen_repository, get_review_report, list_review_reports), making them predictable and easy to distinguish.
With 5 tools, the server is well-scoped for its purpose. Each tool serves a necessary function without bloat or insufficiency.
Core operations are covered: generate, get, list, and structure exploration. Missing delete or update functionality for reports, but the server's focus on one-time generation and review makes this a minor gap.