release-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port for the HTTP server when running in streamable HTTP mode. | 3000 |
| GITHUB_TOKEN | Yes | A fine-grained GitHub token with read-only access to the repositories you want to inspect. No write permission is needed. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_changes_between_refsB | Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API. |
| get_pull_requests_in_rangeA | Get all merged pull requests between two refs with full metadata including labels, linked issues, review counts, and files changed. PRs are categorized by label into: breaking, feature, fix, docs, chore, dependencies, other. |
| get_release_summaryA | Generate a structured release context object ready for AI synthesis into release notes. Combines commit data, PR metadata, linked issues, contributor list, and aggregate statistics for the range between two tags. |
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 3 tools
Each tool targets a distinct deliverable: raw commits with PR enrichment, PR metadata with categorization, and a ready-to-use summary. Descriptions clearly differentiate the level of aggregation, so an agent should have no trouble selecting the right one.
All tools follow a consistent get_ prefix followed by a descriptive noun phrase (changes_between_refs, pull_requests_in_range, release_summary). The pattern is uniform and predictable.
With three tools, the surface is tightly scoped to the release-intel domain. Each tool serves a distinct purpose and none feel redundant or missing, making the count ideal for this focused use case.
The trio covers the complete workflow for release note generation: raw commit data, detailed PR information, and an aggregated summary with statistics and contributor lists. There are no obvious dead ends or missing operations within the stated purpose.