GitHub MCP Server
Allows interaction with GitHub repositories, enabling search, retrieval, and creation of issues and pull requests via the GitHub API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub MCP ServerSearch for issues labeled 'bug' in the 'my-repo' repository."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kage — GitHub MCP Server
Kage (影, shadow) acts as the invisible layer between an LLM and GitHub — an AI agent can command it without ever touching a UI.
What is this?
Kage is a custom Model Context Protocol (MCP) server that exposes GitHub repository operations as structured, schema-validated tools that any MCP-compatible LLM agent (Claude Desktop, Claude Code, etc.) can call autonomously.
Instead of writing hardcoded scripts that chain GitHub API calls, an agent connected to Kage can think, plan, and act — searching for issues, reading their context, and creating new ones — all in one natural language conversation.
Why MCP instead of a plain REST API?
A REST API requires a human (or hardcoded client) to know exactly what endpoints to call. MCP is different: the server advertises its capabilities at runtime via JSON-RPC. An LLM can query the server for what tools exist, read their schemas, and decide autonomously how to use them. No hardcoding, no predefined flows.
Related MCP server: GitHub MCP Server
Architecture
┌─────────────────────────┐ JSON-RPC 2.0 over stdio
│ LLM Agent │◄────────────────────────────────►│ Kage MCP Server (Python) │
│ (Claude Desktop / Code) │ │ │
└─────────────────────────┘ │ FastMCP Framework │
│ ↓ │
│ Pydantic Validation │
│ ↓ │
│ PyGithub Client │
│ ↓ │
│ GitHub REST API │
└──────────────────────────┘sequenceDiagram
participant Agent as LLM Agent (Claude)
participant Kage as Kage MCP Server
participant GH as GitHub API
Agent->>Kage: tools/list → "What can you do?"
Kage-->>Agent: Returns tool names + JSON Schemas
Agent->>Kage: tools/call → search_issues(repo, query)
Note over Kage: Pydantic validates inputs
Kage->>GH: Authenticated search request
GH-->>Kage: Raw issue data
Note over Kage: Formats + limits to top 10 results
Kage-->>Agent: Structured JSON result
Agent->>Kage: tools/call → create_issue(repo, title, body)
Note over Kage: Validates min_length constraints
Kage->>GH: POST /repos/{owner}/{repo}/issues
GH-->>Kage: Created issue data
Kage-->>Agent: { "html_url": "..." }Available Tools
Tool | Description | Type |
| Verifies the server is alive and reachable | Read |
| Search for issues/PRs in a repo using GitHub search syntax | Read |
| Fetch title, body, author, state, and last 5 comments of an issue | Read |
| Create a new issue with a validated title and body | Write |
Tool Schemas
search_issues
{
"repo": "owner/repo",
"query": "is:issue is:open label:bug"
}get_issue_details
{
"repo": "owner/repo",
"issue_number": 42
}create_issue
{
"repo": "owner/repo",
"title": "Min 5 characters required",
"body": "Min 10 characters required"
}Security Design
Least-Privilege Tokens: Uses GitHub Fine-Grained Personal Access Tokens (PAT) scoped to a single repository with only Issues read/write permission. A compromised token cannot touch any other repo or perform any other action.
Pydantic Input Validation: Every tool input is validated against a strict schema before any API call is made. If an LLM hallucinates a bad payload (e.g., an empty issue title), the server rejects it locally with a clear error — no wasted API call, no garbage data in your repo.
Additive-Only Writes: The only write tool (
create_issue) is additive. Destructive operations (delete, close, edit) are deliberately not exposed — preventing an LLM hallucination from causing irreversible damage.Secret Management: The GitHub token is loaded from a
.envfile (never hardcoded) and the.envis in.gitignore.
Project Structure
Kage-The-MCP/
├── server.py # MCP server: all tool definitions and GitHub integration
├── requirements.txt # Python dependencies
├── .env.example # Template for environment variables (copy to .env)
├── .gitignore # Ensures .env and venv are never committed
├── start_inspector.bat # One-click script to launch MCP Inspector for local testing
└── LICENSE # MIT LicenseSetup & Local Testing
Prerequisites
Python 3.10+
Node.js (for MCP Inspector)
A GitHub account and a test repository
1. Clone & Install
git clone https://github.com/YourUsername/Kage-The-MCP.git
cd Kage-The-MCP
python -m venv venv
.\venv\Scripts\activate
pip install -r requirements.txt2. Configure Your Token
Create a GitHub Fine-Grained PAT with:
Repository access: Your test repo only
Permissions: Issues → Read and write, Metadata → Read-only
Then create a .env file:
GITHUB_TOKEN=github_pat_your_token_here3. Run the MCP Inspector
.\start_inspector.batOpen the URL shown in your terminal (e.g., http://localhost:6274), set Command to python and Arguments to server.py, then click Connect.
Stack
Python · FastMCP (MCP SDK 1.28) · PyGithub · Pydantic v2 · python-dotenv · MCP Inspector
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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/decuma02/Kage-The-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server