github-mcp

Configure a GitHub MCP server with 1Password token retrieval for global and local setups.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lekman/cdn --skill github-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mcp
Source: https://github.com/lekman/cdn/tree/main/.claude/skills/github-mcp
Command: npx skills add https://github.com/lekman/cdn --skill github-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub permissions and token management can be error-prone and insecure. This skill provides a secure integration workflow to configure and manage a GitHub MCP server using 1Password tokens, eliminating manual token handling risks.

Core Features & Use Cases

  • Secure 1Password-based token retrieval to configure Bearer-authenticated MCP server for GitHub.
  • Supports both global (user-wide) and local (project-specific) MCP configurations.
  • Provides a complete workflow for MCP setup, reauthentication, and tool enablement across GitHub repositories, issues, PRs, and workflows.
  • Real-world use: configure tokens for a multi-repo project and use MCP to search repos, list issues, and trigger workflows without exposing tokens.

Quick Start

Start by configuring the GitHub MCP server using your 1Password token, then restart Claude Code to apply the new settings.

Frequently Asked Questions about github-mcp

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

FAQPage Schema
How do I securely manage GitHub MCP server tokens without exposing them in configuration files?

Secure GitHub MCP server tokens by retrieving them via 1Password references for Bearer-authenticated integration, eliminating manual token handling risks in your configuration files.

Can I configure the GitHub MCP server for both global and local project environments?

Yes, the GitHub MCP server supports both global user-wide and local project-specific configurations, allowing you to apply MCP settings across multiple organizations or individual repositories.

How do I set up a GitHub MCP server using 1Password for authentication?

Configure the GitHub MCP server by retrieving your token via 1Password references, applying the Bearer token authentication settings, then restarting Claude Code to apply the new configuration.

What GitHub operations can I automate through the MCP server once token authentication is configured?

Once authenticated, the GitHub MCP server enables automated repository searches, issue listing, pull request management, and workflow triggering across multiple organizations without exposing tokens.

What is the best way to handle reauthentication for a GitHub MCP server across multiple organizations?

The best way to handle reauthentication is using 1Password token retrieval to securely update Bearer-authenticated MCP server configurations, maintaining access across multiple organizations without manual token rotation.

Why does my GitHub MCP configuration fail to authenticate tokens across different repositories?

GitHub MCP token authentication fails when manual token handling introduces errors; using 1Password references for secure Bearer token retrieval ensures consistent configuration across global and local project setups.