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. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cindyylim/MCP-PR-Workflow-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server