github-mcp

Route GitHub MCP operations for issues, comments, labels, and PRs to correct repositories.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill github-mcp-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mcp
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/issue-operations/platforms/github-mcp
Command: npx skills add https://github.com/michael-conrad/.opencode --skill github-mcp-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub platform operations risk misrouting and incomplete API usage; this Skill ensures platform-aware routing through MCP tools to perform GitHub actions safely and consistently.

Core Features & Use Cases

  • Full coverage of GitHub MCP operations including issue creation, comments, labeling, closures, PR actions, and status checks.
  • Platform-aware routing guarantees actions target the correct owner/repo even in multi-tenant environments.
  • Use Case: Route an issue or PR operation through the MCP dispatcher to ensure correct context and permissions.

Quick Start

Instruct the agent to perform a GitHub MCP operation for an issue in the target repository.

Frequently Asked Questions about github-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue and pull request management across multiple repositories?

Automating GitHub issue and pull request management requires a platform-aware routing mechanism to target the correct owner and repo. Using an MCP dispatcher ensures operations like issue creation, updates, closures, and PR reviews execute safely and consistently across multi-tenant environments.

What is the best way to prevent GitHub API misrouting when automating platform operations?

Preventing GitHub API misrouting requires enforcing owner and repository verification before executing actions. A dispatcher-based routing approach guarantees platform-aware targeting, ensuring comments, labels, and PR reviews apply to the correct repository context.

Does MCP support full API coverage for GitHub pull request reviews and issue closures?

MCP supports full API coverage for GitHub pull request reviews and issue closures by leveraging the complete MCP toolset. This includes platform operations for issue creation, updates, labeling, closures, PR actions, and status checks.

How do I route a GitHub MCP operation for an issue in a target repository?

Routing a GitHub MCP operation for an issue requires instructing the agent to perform the action through the MCP dispatcher. The dispatcher enforces owner and repo verification to ensure the operation targets the correct repository context and permissions.

Can I use GitHub MCP workflows for label management and status checks in multi-tenant environments?

GitHub MCP workflows support label management and status checks in multi-tenant environments through platform-aware routing. The dispatcher-based routing mechanism guarantees actions target the correct owner and repo, ensuring consistent and safe API usage.

Why does my GitHub MCP operation fail to target the correct repository context?

GitHub MCP operations fail to target the correct repository context when owner and repo verification is not enforced. Implementing dispatcher-based routing ensures platform-aware targeting and verifies the correct context and permissions before executing actions.