MCP Config 6dbe3cab

MCP开发工具

提供方 Johnwainey7

开发工具 未标注 会话登录 社区 / 第三方

一个基于MCP协议的GitHub集成服务器,提供创建GitHub问题、探索仓库和文档等功能,适用于AI助手和其他MCP客户端。

一句话选型结论

按资料字段整理

MCP Config 6dbe3cab 属于开发工具类 MCP 服务器,传输方式未标注,会话登录,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 7 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量7暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

GitHub集成JavaScript本地部署MCP协议问题管理文档探索TypeScript

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 7 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 7 个工具,职责相对集中,接入后不容易误操作。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Config 6dbe3cab当前 7 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Johnwainey7上游标注的维护方 Johnwainey7
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.5 KB
来自项目仓库与上游目录的原文,未做删改

GitHub MCP Server

A Model Context Protocol (MCP) server that provides GitHub integration capabilities, specifically for creating GitHub issues through the MCP interface.

Overview

This MCP server allows AI assistants and other MCP clients to interact with GitHub repositories by creating issues and exploring repositories/documentation. It implements the MCP protocol to provide a standardized interface for GitHub operations.

Features

  • Create GitHub Issues: Create new issues in GitHub repositories
  • Discover Repositories: List user/org repos and search public repos
  • Read Documentation: Fetch README and markdown docs, or arbitrary files
  • Input Validation: Robust parameter validation using Zod schemas
  • Error Handling: Comprehensive error handling with proper MCP error codes
  • Type Safety: Full TypeScript implementation with strict type checking

Prerequisites

  • Node.js (v18 or higher)
  • npm or yarn
  • GitHub Personal Access Token

Installation

  1. Clone the repository:```bash
    git clone <repository-url>
    cd git_mcp

2. Install dependencies:```bash
npm install
  1. Set up environment variables:```bash
    cp .env.example .env

4. Edit `.env` and add your GitHub token:```
GITHUB_TOKEN=your_github_token_here

Configuration

GitHub Token Setup

  1. Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
  2. Generate a new token with the following scopes:
    - repo (Full control of private repositories)
    - public_repo (Access public repositories)
  3. Copy the token and add it to your .env file

Environment Variables

Variable Description Required
GITHUB_TOKEN Your GitHub Personal Access Token Yes

Usage

Development Mode

Run the server in development mode with hot reloading:```bash
npm run dev


### Production Mode

1. Build the project:```bash
npm run build
  1. Start the server:```bash
    npm start

### MCP Client Integration

The server communicates via stdio transport, making it compatible with any MCP client. Here&#x27;s how to configure it in your MCP client:```json
{
  &quot;mcpServers&quot;: {
    &quot;github&quot;: {
      &quot;command&quot;: &quot;node&quot;,
      &quot;args&quot;: [&quot;dist/github-mcp-server.js&quot;],
      &quot;env&quot;: {
        &quot;GITHUB_TOKEN&quot;: &quot;your_token_here&quot;
      }
    }
  }
}

API Reference

Available Tools

create-issue

Creates a new GitHub issue in a specified repository.

Parameters:
- title (string, required): The title of the issue
- body (string, optional): The body/description of the issue
- owner (string, required): The repository owner (username or organization)
- repo (string, required): The repository name
- labels (array of strings, optional): Labels to add to the issue
- assignees (array of strings, optional): Usernames to assign to the issue

Example Usage:```json
{
"name": "create-issue",
"arguments": {
"title": "Fix login bug",
"body": "Users are unable to log in with their credentials",
"owner": "myorg",
"repo": "myproject",
"labels": ["bug", "high-priority"],
"assignees": ["developer1"]
}
}


**Response:**```json
{
  &quot;content&quot;: [
    {
      &quot;type&quot;: &quot;text&quot;,
      &quot;text&quot;: &quot;Successfully created issue #123: Fix login bug\nURL: https://github.com/myorg/myproject/issues/123&quot;
    }
  ]
}

list-user-repos

Lists repositories for a user or the authenticated user.

Parameters:
- username (string, optional): If omitted, lists repos for the authenticated user
- visibility ("all" · "public" · "private", optional, default "all")
- per_page (integer, 1-100, default 50)
- page (integer, default 1)

Example:```json
{ "name": "list-user-repos", "arguments": { "visibility": "public" } }


#### list-org-repos

Lists repositories in an organization.

**Parameters:**
- `org` (string, required)
- `type` (&quot;all&quot; · &quot;public&quot; · &quot;private&quot; · &quot;forks&quot; · &quot;sources&quot; · &quot;member&quot;, default &quot;all&quot;)
- `per_page` (integer, 1-100, default 50)
- `page` (integer, default 1)

**Example:**```json
{ &quot;name&quot;: &quot;list-org-repos&quot;, &quot;arguments&quot;: { &quot;org&quot;: &quot;myorg&quot;, &quot;type&quot;: &quot;public&quot; } }

search-repos

Searches public repositories using GitHub search syntax.

Parameters:
- q (string, required): Query, e.g. &quot;lang:ts topic:mcp sdk&quot;
- sort ("stars" · "forks" · "help-wanted-issues" · "updated")
- order ("desc" | "asc", default "desc")
- per_page (integer, 1-100, default 30)
- page (integer, default 1)

Example:```json
{ "name": "search-repos", "arguments": { "q": "mcp in:name language:TypeScript" } }


#### get-readme

Fetches the README file as text from a repository.

**Parameters:**
- `owner` (string, required)
- `repo` (string, required)
- `ref` (string, optional): Branch, tag, or SHA

**Example:**```json
{ &quot;name&quot;: &quot;get-readme&quot;, &quot;arguments&quot;: { &quot;owner&quot;: &quot;myorg&quot;, &quot;repo&quot;: &quot;myrepo&quot; } }

list-docs

Lists markdown documentation files in common docs directories and root.

Parameters:
- owner (string, required)
- repo (string, required)
- ref (string, optional)

Example:```json
{ "name": "list-docs", "arguments": { "owner": "myorg", "repo": "myrepo" } }


#### get-file

Fetches an arbitrary repository file as text.

**Parameters:**
- `owner` (string, required)
- `repo` (string, required)
- `path` (string, required)
- `ref` (string, optional)

**Example:**```json
{ &quot;name&quot;: &quot;get-file&quot;, &quot;arguments&quot;: { &quot;owner&quot;: &quot;myorg&quot;, &quot;repo&quot;: &quot;myrepo&quot;, &quot;path&quot;: &quot;docs/intro.md&quot; } }

Error Handling

The server implements comprehensive error handling:

  • Invalid Parameters: Returns InvalidParams error code with detailed validation messages
  • GitHub API Errors: Returns InternalError with GitHub API error details
  • Authentication Errors: Returns InternalError when GitHub token is invalid
  • Unknown Tools: Returns MethodNotFound for unsupported tool requests

Development

Project Structure```

src/
├── github-mcp-server.ts # Main server implementation
package.json # Dependencies and scripts
tsconfig.json # TypeScript configuration
README.md # This documentation


### Key Components

1. **GitHubMCPServer Class**: Main server class that handles MCP protocol
2. **Schema Validation**: Uses Zod for robust parameter validation
3. **Error Handling**: Comprehensive error handling with proper MCP error codes
4. **Transport Layer**: Uses stdio transport for MCP communication

### Code Changes Made

#### 1. Fixed Syntax Error
**Problem**: Double `this` keyword on line 34```typescript
// Before (incorrect)
this this.server.setRequestHandler(...)

// After (correct)
this.server.setRequestHandler(...)

2. Added Schema Definition

Problem: Missing CreateIssueRequestSchema definition
Solution: Created comprehensive Zod schema with validation:```typescript
const CreateIssueRequestSchema = z.object({
title: z.string().describe("The title of the issue"),
body: z.string().optional().describe("The body/description of the issue"),
owner: z.string().describe("The repository owner (username or organization)"),
repo: z.string().describe("The repository name"),
labels: z.array(z.string()).optional().describe("Labels to add to the issue"),
assignees: z.array(z.string()).optional().describe("Usernames to assign to the issue"),
});


#### 3. Implemented Tool Handler
**Problem**: Empty `handleRequest()` method
**Solution**: Complete implementation with:
- Parameter validation using Zod
- GitHub API integration
- Proper error handling
- MCP-compliant responses

#### 4. Added Server Startup
**Problem**: Server created but never started
**Solution**: Added complete startup sequence:
- Transport initialization
- Server connection
- Main execution function
- Graceful shutdown handling

#### 5. Enhanced Imports
**Problem**: Missing type imports causing linter errors
**Solution**: Separated runtime and type imports:```typescript
import { CallToolRequestSchema, ListToolsRequestSchema, ErrorCode, McpError } from &quot;@modelcontextprotocol/sdk/types.js&quot;;
import type { Tool, CallToolResult, TextContent } from &quot;@modelcontextprotocol/sdk/types.js&quot;;

Dependencies Added

  • zod: Runtime schema validation for robust parameter checking
  • @types/node: TypeScript definitions for Node.js

Testing

Manual Testing

  1. Start the server:```bash
    npm run dev

2. Test with an MCP client that supports the create-issue tool

### Integration Testing

The server can be tested with any MCP-compliant client by sending proper MCP protocol messages.

## Troubleshooting

### Common Issues

1. **&quot;GITHUB_TOKEN environment variable is required&quot;**
   - Ensure your `.env` file contains a valid `GITHUB_TOKEN`
   - Verify the token has the required permissions

2. **&quot;Failed to create issue: 404 Not Found&quot;**
   - Check that the repository owner and name are correct
   - Ensure the token has access to the repository

3. **&quot;Invalid parameters&quot;**
   - Verify all required parameters are provided
   - Check parameter types match the schema

### Debug Mode

Enable debug logging by setting the `DEBUG` environment variable:```bash
DEBUG=* npm run dev

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

License

ISC License - see LICENSE file for details

Support

For issues and questions:
1. Check the troubleshooting section
2. Review GitHub API documentation
3. Open an issue in the repository

Changelog

v1.0.0

  • Initial release
  • GitHub issue creation functionality
  • MCP protocol compliance
  • Comprehensive error handling
  • TypeScript implementation

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
MCP Config 6dbe3cab 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP Config 6dbe3cab 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP Config 6dbe3cab 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Config 6dbe3cab 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

MCP Config 6dbe3cab 能提供哪些能力?

资料显示约 7 个工具;能力标签包括 GitHub、JavaScript、问题管理、TypeScript。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。