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_repositoryB | 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_reportC | Get a previously generated GitLumen MCP report by reportId. |
| list_review_reportsB | List previously generated GitLumen MCP reports stored locally. |
| get_repository_structureB | Fetch public GitHub repository or PR structure without generating a full risk report. |
| explain_gitlumen_mcp_flowB | 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitlumen-team/gitlumen-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server