github-repo-summarizer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_HOST | No | Ollama HTTP endpoint. | http://localhost:11434 |
| OLLAMA_MODEL | No | Tag of the Ollama model to use. Must be pulled. | llama3.2 |
| OLLAMA_NUM_CTX | No | Context window in tokens. Bump for larger repos; lower if memory-constrained. | 16384 |
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 |
|---|---|
| summarize_github_repoA | Generate a PDF report summarizing a public GitHub repository. The PDF contains the repository's metadata, an LLM-written technical summary of the codebase, the most recent commits, and a list of suggested improvements. Args: repo_url: A public GitHub repository URL (e.g. https://github.com/owner/repo) or "owner/repo" shorthand. output_dir: Directory where the PDF will be written. Defaults to the current working directory. Returns: The absolute path of the generated PDF file. |
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 1 tool
Only one tool exists, so there is no ambiguity or risk of misselection. An agent can clearly identify its purpose.
The single tool follows a clear verb_noun pattern ('summarize_github_repo'), which is consistent and predictable.
With only one tool, the server feels thin for a typical MCP server, but it is still acceptable for a focused summarization task. The scope is narrow but complete.
The tool covers the full workflow of summarizing a GitHub repository into a PDF, including metadata, technical summary, recent commits, and suggested improvements. There are no obvious gaps in the stated purpose.