GitHub Summary MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with repo scope |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_summaryA | Generate a summary of today's commits authored by the authenticated GitHub user. The tool:
Returns:
A dict with a single key Example return value:: |
| list_repositoriesA | Return all repositories accessible by the authenticated GitHub user. Includes repositories where the user is an owner, collaborator, or organisation member. Returns:
A dict with key Example return value:: |
| get_repo_commits_todayA | Return today's commits for a single repository authored by the authenticated user. Args:
repo_name: The repository to inspect. Accepts either the short name
(e.g. Returns: A dict with keys: Example return value:: |
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 has a clearly distinct purpose: get_daily_summary aggregates commits across all repositories for today, get_repo_commits_today focuses on a single repository's commits for today, and list_repositories provides a repository listing. There is no overlap or ambiguity in functionality.
All tool names follow a consistent verb_noun pattern: get_daily_summary, get_repo_commits_today, and list_repositories. The naming is predictable and readable throughout the set.
With only 3 tools, the server feels thin for a GitHub-related domain, which typically involves more operations like creating issues, managing pull requests, or accessing other repository details. While the tools are well-defined, the scope is limited.
The toolset is severely incomplete for a GitHub server, covering only commit summaries and repository listing. Missing are core operations like issue management, pull request handling, branch operations, or user actions, which are essential for typical GitHub workflows.