mcp-github-recovery

Diagnose GitHub MCP transport or authentication failures and restore automation.

17|8|Updated Apr 11, 2022
One-click install
npx skills add https://github.com/LucasSantana-Dev/Lucky --skill mcp-github-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-github-recovery
Source: https://github.com/LucasSantana-Dev/Lucky/tree/main/.cursor/skills/mcp-github-recovery
Command: npx skills add https://github.com/LucasSantana-Dev/Lucky --skill mcp-github-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves issues where GitHub MCP (Model Context Protocol) calls fail due to transport or authentication errors, specifically when the gh CLI tool is still functional, and Lucky requires its Codex or OpenCode GitHub automation to be restored.

Core Features & Use Cases

  • Diagnose MCP Failures: Identifies specific error signatures indicating transport or auth issues with GitHub MCP.
  • Validate Configuration: Checks local Codex MCP configuration for GitHub, ensuring correct paths and absence of sensitive environment variables.
  • Install Official Binary: Downloads and installs the latest official github-mcp-server binary.
  • Update Wrappers: Modifies or creates wrapper scripts (run-mcp-github.sh) for Codex, OpenCode, and Cursor to use the official binary and fall back to gh tokens.
  • Smoke Testing: Verifies that Codex and OpenCode can successfully execute GitHub MCP calls after the recovery process.
  • Use Case: When your development environment's automated issue tracking or PR creation via MCP stops working, but you can still use gh pr list from your terminal, this Skill guides you through fixing the underlying MCP service.

Quick Start

Run the mcp-github-recovery skill to fix GitHub MCP automation failures.

Frequently Asked Questions about mcp-github-recovery

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

FAQPage Schema
How do I fix GitHub MCP automation failures when the gh CLI is still working?

You can fix GitHub MCP automation failures by diagnosing transport or authentication errors, validating local Codex configurations, and installing the official `github-mcp-server` binary to restore functionality.

Why does my Codex GitHub MCP integration stop working with transport or auth errors?

Codex GitHub MCP integration fails with transport or auth errors due to misconfigured local MCP paths, sensitive environment variables, or missing official binaries. Validating configurations and updating wrapper scripts resolves these issues.

How do I install the official github-mcp-server binary for OpenCode and Codex?

You install the official `github-mcp-server` binary by downloading the latest release, updating wrapper scripts like `run-mcp-github.sh` for OpenCode and Codex, and configuring them to fall back to `gh` tokens for authentication.

Can I use gh CLI tokens as a fallback for github-mcp-server authentication?

Yes, you can use `gh` CLI tokens as a fallback for `github-mcp-server` authentication by aligning wrapper scripts for Codex, OpenCode, and Cursor to use the official binary while securely managing token injection.

How do I verify that GitHub MCP recovery is successful for OpenCode?

Verify GitHub MCP recovery for OpenCode by running smoke tests that execute actual GitHub MCP calls, ensuring the automated issue tracking or PR creation processes are fully restored without transport errors.