MCP PR Workflow Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub token | |
| SLACK_BOT_TOKEN | Yes | Slack bot token (xoxb-...) | |
| SLACK_CHANNEL_ID | Yes | Slack channel ID |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_file_changesA | Analyzes file changes in a GitHub PR to determine the type of changes made. |
| suggest_templateA | Suggests an optimal PR template based on the analysis of file changes. |
| analyze_ci_resultsB | Analyzes GitHub Actions workflow runs for a PR and provides a formatted summary. |
| update_pr_statusC | Updates a pull request with CI results or other process updates. |
| send_slack_notificationC | Sends a generic notification message to a Slack channel. |
| notify_deployment_statusB | Sends a formatted deployment status message (success/failure) to Slack. |
| create_follow_up_issueA | Creates a follow-up GitHub issue for tasks identified during the PR process. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| suggest-pr-template | Generates a suggestion for which PR template to use based on file changes. |
| analyze-ci-failure | Analyzes a CI failure and suggests next steps based on team policy. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Team PR Guidelines | Standard operating procedures for pull requests and code reviews. |
| Notification Preferences | Team preferences for Slack notifications and alerts. |
| Escalation Policy | Guidelines for when to escalate CI failures or deployment issues. |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: analyzing file changes, analyzing CI, updating PR status, and creating issues are distinct. However, send_slack_notification and notify_deployment_status both send Slack messages, which could cause confusion for an agent despite the latter being more specific.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., analyze_file_changes, suggest_template, create_follow_up_issue). There are no mixed conventions or vague verbs, making the pattern predictable.
Seven tools is within the ideal 3-15 range and each tool serves a distinct step in the PR workflow. The count feels well-scoped without being excessive or too thin.
The tool set covers the main PR workflow: analyzing changes, suggesting templates, analyzing CI, updating status, sending notifications, and creating follow-ups. Minor gaps exist, such as no direct way to fetch PR details or comment on a PR, but the core lifecycle is reasonably covered.