tai-mcp-github
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with Pull requests: Read and Write permissions |
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 |
|---|---|
| list_pull_requestsB | List pull requests for a repository. Args: owner: Repository owner (user or organisation). repo: Repository name. state: Filter by state — 'open' (default), 'closed', or 'all'. |
| get_pull_requestA | Get full details of a specific pull request. Args: owner: Repository owner. repo: Repository name. pr_number: Pull request number. |
| list_pr_commentsA | List general thread comments on a pull request (conversation tab). These are top-level comments, not inline review comments on the diff. Use list_unresolved_review_threads for inline code review comments. Args: owner: Repository owner. repo: Repository name. pr_number: Pull request number. |
| list_unresolved_review_threadsA | List unresolved inline review threads on a pull request. Returns only threads that have not been resolved yet, so the agent has a clear picture of what still needs attention. Each thread includes its GitHub node ID (thread_id), file path, line number, and all comments. Pass thread_id to resolve_review_thread to mark a thread as done. Args: owner: Repository owner. repo: Repository name. pr_number: Pull request number. |
| resolve_review_threadA | Mark a pull request review thread as resolved. Use list_unresolved_review_threads to get thread_id values. Args: thread_id: GitHub GraphQL node ID of the review thread. |
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 5 tools
Each tool targets a distinct aspect of pull request workflows: listing PRs, getting a specific PR, listing comments, listing unresolved review threads, and resolving them. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (list_pull_requests, get_pull_request, list_pr_comments, list_unresolved_review_threads, resolve_review_thread), using lowercase with underscores.
Five tools is an appropriate and focused scope for a GitHub pull request review assistant. Each tool earns its place, covering listing, detail, comment viewing, unresolved thread viewing, and resolution.
The tool set covers the core PR review workflow well—listing, reading, and resolving threads. However, it lacks tools to create or reply to comments or threads, which agents may need to fully participate in reviews.