GitHub Activity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token with repo and read:user scopes. Optional but recommended for higher rate limits. |
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 | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_repositoriesB | Search GitHub repositories by query. Supports GitHub search qualifiers. |
| get_repositoryA | Get detailed information about a specific GitHub repository. |
| get_file_contentsB | Read the contents of a file from a GitHub repository. |
| list_commitsA | List recent commits for a repository, optionally filtered by path or author. |
| list_issuesB | List issues in a GitHub repository with optional filters. |
| get_issueA | Get detailed information about a specific issue, including its comments. |
| create_issueB | Create a new issue in a GitHub repository. |
| add_issue_commentB | Add a comment to an existing GitHub issue. |
| list_pull_requestsC | List pull requests in a GitHub repository. |
| get_pull_requestC | Get detailed information about a specific pull request. |
| get_pull_request_diffB | Get the diff/patch of a pull request to review code changes. |
| get_user_profileA | Get public profile information for a GitHub user. |
| list_user_reposB | List repositories for a GitHub user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_repo | Comprehensively analyze a GitHub repository — architecture, code quality, activity, and recommendations. |
| review_pr | Review a pull request with focus on code quality, bugs, and best practices. |
| issue_triage | Triage and categorize open issues in a repository. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: repositories, files, commits, issues, pull requests, and user profiles are cleanly separated. There is no meaningful overlap between tools like get_repository and search_repositories or list_issues and get_issue.
All tool names follow a consistent snake_case verb_noun pattern, such as search_repositories, get_file_contents, and create_issue. Minor semantic differences between verbs like get and list are still predictable and uniform across the set.
Thirteen tools is well within the ideal range for a domain-focused server and each tool covers a meaningful capability. The count feels appropriately scoped for GitHub browsing, issue interaction, and pull request review without being bloated.
The server covers read-heavy repository activity well, including search, file access, commits, issues, pull requests, and user profiles. Issue comments are supported, but lifecycle operations like updating/ closing issues or creating/merging pull requests are absent, which is a minor gap if the server is intended for broader GitHub management.