github-mcp-server

Configure GitHub MCP server modes, toolsets, and authentication for Agentic Workflows.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-mcp-server-cogni-ai-ou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mcp-server
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/github-mcp-server
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-mcp-server-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents misconfigured GitHub Model Context Protocol (MCP) tool setups that lead to missing tools, silent authentication failures, or permission errors in Agentic Workflows.

Core Features & Use Cases

  • Agentic Workflow-ready configuration guidance: Explains how to set the mcp-servers and tools.github blocks correctly for common workflow patterns.
  • Authentication and mode selection: Covers how to choose and configure gh-proxy, local, and remote modes with the right token/headers and read-only behavior.
  • Stable toolset mapping and security guardrails: Provides guidance on using toolsets: (not deprecated allowed:) and selecting only the required toolsets to minimize risk and improve reliability.

Use case example: When you need an agent to read repository contents and create issues with controlled permissions, this Skill guides you to select appropriate toolsets and choose the correct mode and token strategy to avoid write failures.

Quick Start

Use the github-mcp-server skill to configure your workflow’s GitHub MCP toolsets by setting tools.github.toolsets: [default, actions, security_advisories] and ensuring the token and permissions match the enabled toolsets.

Frequently Asked Questions about github-mcp-server

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

FAQPage Schema
How do I configure GitHub MCP server toolsets for agentic workflows?

Configure GitHub MCP toolsets by assigning arrays such as default, actions, and security_advisories to the tools.github.toolsets block. This enforces forward-compatible tool selection and prevents missing tools in automated repository workflows.

What is the difference between local and remote GitHub MCP access modes?

GitHub MCP modes include gh-proxy, local, and remote configurations. Selecting a mode dictates how tokens and headers manage read-only or scoped write operations across repository, issues, and pull requests workflows.

Why does my GitHub MCP workflow fail with permission errors during pull requests?

GitHub MCP workflows fail with permission errors when PAT scope constraints mismatch the enabled toolsets. Enforcing correct authentication and mapping tools to stable toolsets resolves silent failures and prevents unauthorized write operations.

Can I use GitHub MCP tools for read-only repository actions without write access?

Yes, GitHub MCP tools support read-only repository actions by selecting appropriate toolsets and configuring the correct access mode with constrained PAT scopes. This prevents unauthorized write operations while allowing safe data retrieval.

Do I need specific PAT scopes for GitHub MCP server toolsets?

Yes, specific PAT scopes are required for GitHub MCP server toolsets to enforce correct authentication and permissions. Token scope constraints must align with selected toolsets to prevent silent authentication failures during issues and actions workflows.