Back to MCP directory
publicPublicdnsLocal runtime

mcp-github-issue

启用大型语言模型(LLM)与GitHub问题进行交互,通过将详情提供为任务,从而实现通过GitHub平台的无缝集成和任务管理。

article

README

MCP GitHub Issue Server

smithery badge

smithery badge

An MCP server that provides LLMs with the ability to use GitHub issues as the task to complete. This server allows LLMs to fetch GitHub issue details and use them as task descriptions.

GitHub Issue Server MCP server

Installation

Manual Installation

npx mcp-github-issue

Installing via Smithery

To install MCP GitHub Issue Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-github-issue --client claude

Usage

As an MCP Server

Add to your MCP configuration:

{
  "mcpServers": {
    "github-issue": {
      "command": "npx",
      "args": ["mcp-github-issue"]
    }
  }
}

Available Tools

get_issue_task

Fetches GitHub issue details to use as a task.

Input Schema:

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "GitHub issue URL (https://github.com/owner/repo/issues/number)"
    }
  },
  "required": ["url"]
}

Example Usage:

<use_mcp_tool>
<server_name>github-issue</server_name>
<tool_name>get_issue_task</tool_name>
<arguments>
{
  "url": "https://github.com/owner/repo/issues/123"
}
</arguments>
</use_mcp_tool>

Response Format:

{
  "task": {
    "title": "Issue Title",
    "description": "Issue Description/Body",
    "source": "https://github.com/owner/repo/issues/123"
  }
}

Features

  • Fetches GitHub issue details from public repositories
  • No authentication required for public repositories
  • Returns structured task data including title, description, and source URL
  • Compatible with the Model Context Protocol (MCP)

Development

# Install dependencies
npm install

# Build the project
npm run build

# Run the server locally
npm run serve

# Format code
npm run format

# Run MCP inspector
npm run inspector

License

MIT

Author

Sam McLeod (https://smcleod.net)

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client