GitHub Projects MCP 569db2fd

MCP办公协作

提供方 ProRanked

办公协作 未标注 会话登录 社区 / 第三方 Claude DesktopClaude

一个通过GraphQL API与GitHub Projects交互的MCP服务器,提供项目管理和问题管理功能,适用于团队协作和软件开发项目管理。

一句话选型结论

按资料字段整理

GitHub Projects MCP 569db2fd 属于办公协作类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

项目管理JavaScript本地部署问题管理团队协作软件开发GitHub集成

安装与配置

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

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

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

值得选的地方

  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

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

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
GitHub Projects MCP 569db2fd当前 未标注 未标注 未标注 无 2026-05-17
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

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

详细介绍

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

GitHub Projects MCP Server

An MCP (Model Context Protocol) server that provides tools for interacting with GitHub Projects via GraphQL API. This repo is managed by the Model Context Protocol (MCP) and is designed to work seamlessly with Claude Desktop. Written by ProRanked.

Features

Project Management

  • Create new projects for repositories or organizations
  • List projects for repositories and organizations
  • Get detailed project information including fields
  • List items in a project
  • Create new project items from issues/PRs
  • Update project item field values

Issue Management

  • Create new issues with automatic type detection and labeling
  • Smart detection of issue types: Epic, Feature, Bug, Task, Story, Documentation
  • Create parent-child relationships between issues (Epic > Feature > Story/Task)
  • Update existing issues (title, body, state, labels, assignees, milestone)
  • List issues with filtering options (state, labels, assignee)
  • Get detailed issue information including comments and project associations
  • View complete issue hierarchy (parents and children)
  • Ensure standard issue type labels exist in repositories

Setup

  1. Clone this repository
  2. Install dependencies:bash npm install

  3. Build the project:bash npm run build

  4. Configure your GitHub token in Claude Desktop settings (see Integration section below)

Usage

Running the server

The server is designed to be run through Claude Desktop's MCP integration.

For local development with a .env file:```bash
npm run dev


**Note:** The production server (`npm start`) requires the `GITHUB_TOKEN` environment variable to be set externally.

### Available Tools

#### Project Tools

##### create_project
Create a new GitHub project.

Parameters:
- `owner` (required): Repository owner or organization name
- `title` (required): Project title
- `repo` (optional): Repository name (omit for organization project)

##### list_projects
List GitHub projects for a repository or organization.

Parameters:
- `owner` (required): Repository owner or organization name
- `repo` (optional): Repository name (omit for organization projects)
- `projectsType` (optional): "repository" or "organization" (default: "repository")

##### get_project
Get detailed information about a specific project.

Parameters:
- `projectNumber` (required): Project number
- `owner` (required): Repository owner or organization name
- `repo` (optional): Repository name (omit for organization projects)

##### list_project_items
List items in a GitHub project.

Parameters:
- `projectId` (required): Project node ID
- `first` (optional): Number of items to return (default: 20)

##### create_project_item
Add an existing issue or pull request to a project.

Parameters:
- `projectId` (required): Project node ID
- `contentId` (required): Issue or PR node ID

##### update_project_item_field
Update a field value for a project item.

Parameters:
- `projectId` (required): Project node ID
- `itemId` (required): Project item node ID
- `fieldId` (required): Field node ID
- `value` (required): New value for the field

#### Issue Tools

##### create_issue
Create a new issue in a repository with automatic type detection.

Parameters:
- `owner` (required): Repository owner (automatically converted to lowercase)
- `repo` (required): Repository name
- `title` (required): Issue title
- `body` (optional): Issue body/description
- `labels` (optional): Array of label names to assign
- `assignees` (optional): Array of usernames to assign
- `milestone` (optional): Milestone number to assign
- `parentIssueNumber` (optional): Parent issue number to link this issue to

**Automatic Type Detection**: The tool analyzes the title and body to automatically add appropriate labels:
- **Epic**: Large initiatives, milestones, parent tasks
- **Feature**: New functionality, enhancements, implementations
- **Bug**: Errors, fixes, crashes, broken functionality
- **Task**: General tasks, chores, refactoring, updates
- **Story**: User stories, "as a user" scenarios
- **Documentation**: Docs, README, guides

##### update_issue
Update an existing issue.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `issueNumber` (required): Issue number
- `title` (optional): New title
- `body` (optional): New body
- `state` (optional): "open" or "closed"
- `labels` (optional): Replace all labels with this array
- `assignees` (optional): Replace all assignees with this array
- `milestone` (optional): New milestone number (or null to remove)

##### list_issues
List issues in a repository.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `state` (optional): "open", "closed", or "all" (default: "open")
- `labels` (optional): Array of labels to filter by
- `assignee` (optional): Filter by assignee username
- `first` (optional): Number of issues to return (default: 20)

##### get_issue
Get detailed information about a specific issue.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `issueNumber` (required): Issue number

##### ensure_labels
Ensure standard issue type labels exist in the repository.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `labels` (optional): Array of label definitions with:
  - `name` (required): Label name
  - `color` (required): Hex color without #
  - `description` (optional): Label description

If no labels are provided, creates default issue type labels (epic, feature, bug, task, story, documentation).

##### link_issues
Create parent-child relationships between issues.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `parentIssueNumber` (required): Parent issue number (e.g., Epic or Feature)
- `childIssueNumber` (required): Child issue number to link
- `linkType` (optional): Relationship type - "tracks" (default), "blocks", or "related"

##### set_parent
Set or update the parent of an issue (simpler alternative to link_issues).

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `issueNumber` (required): Issue number to set parent for
- `parentIssueNumber` (required): Parent issue number (e.g., Epic or Feature)

##### get_issue_hierarchy
Get the complete hierarchy of an issue showing all parents and children.

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `issueNumber` (required): Issue number to get hierarchy for

##### add_sub_issue
Add a native sub-issue relationship using GitHub beta API (creates parent-child relationship visible in GitHub's UI).

Parameters:
- `owner` (required): Repository owner
- `repo` (required): Repository name
- `parentIssueNumber` (required): Parent issue number
- `childIssueNumber` (required): Child issue number to add as sub-issue

Note: This uses GitHub's beta API. If not available, it falls back to task list approach.

## Integration with Claude Desktop

Add to your Claude Desktop configuration file:
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json````json
{
  "mcpServers": {
    "github-projects": {
      "command": "node",
      "args": ["/path/to/github-projects-mcp/dist/index.js"],
      "env": {
        "GITHUB_TOKEN": "your_github_personal_access_token"
      }
    }
  }
}

Required GitHub Token Permissions:

  • repo - For accessing repository projects
  • read:org - For accessing organization projects
  • project - For full project access (read/write)

Create your token at: https://github.com/settings/tokens

Example Usage

Project Examples

  1. Create a new project:Tool: create_project Arguments: { "owner": "octocat", "repo": "hello-world", "title": "My New Project" }

  2. List all projects in a repository:Tool: list_projects Arguments: { "owner": "octocat", "repo": "hello-world" }

  3. Get project details:Tool: get_project Arguments: { "owner": "octocat", "repo": "hello-world", "projectNumber": 1 }

Issue Examples

  1. Ensure issue type labels exist:Tool: ensure_labels Arguments: { "owner": "octocat", "repo": "hello-world" }

  2. Create a new issue (auto-detects as bug):Tool: create_issue Arguments: { "owner": "octocat", "repo": "hello-world", "title": "Bug: Application crashes on startup", "body": "When I try to start the application, it crashes with error XYZ.", "labels": ["high-priority"], "assignees": ["octocat"] }

  3. Create an epic:Tool: create_issue Arguments: { "owner": "octocat", "repo": "hello-world", "title": "Epic: Implement user authentication system", "body": "This epic covers the implementation of a complete authentication system including login, registration, and password recovery." }

  4. Create a feature under an epic:Tool: create_issue Arguments: { "owner": "octocat", "repo": "hello-world", "title": "Feature: Implement login functionality", "body": "Implement secure login with JWT tokens", "parentIssueNumber": 100 }

  5. Link existing issues:Tool: link_issues Arguments: { "owner": "octocat", "repo": "hello-world", "parentIssueNumber": 100, "childIssueNumber": 101, "linkType": "tracks" }

  6. Set parent for an issue (simpler syntax):Tool: set_parent Arguments: { "owner": "octocat", "repo": "hello-world", "issueNumber": 101, "parentIssueNumber": 100 }

  7. View issue hierarchy:Tool: get_issue_hierarchy Arguments: { "owner": "octocat", "repo": "hello-world", "issueNumber": 100 }

  8. Add native sub-issue relationship (beta):Tool: add_sub_issue Arguments: { "owner": "octocat", "repo": "hello-world", "parentIssueNumber": 100, "childIssueNumber": 101 }

  9. Update an issue:Tool: update_issue Arguments: { "owner": "octocat", "repo": "hello-world", "issueNumber": 42, "state": "closed", "labels": ["bug", "fixed"] }

  10. List open issues with a specific label:Tool: list_issues Arguments: { "owner": "octocat", "repo": "hello-world", "state": "open", "labels": ["bug"] }

  11. Add an issue to a project:Tool: create_project_item Arguments: { "projectId": "PVT_kwDOBgKK184AAAAA", "contentId": "I_kwDOBgKK185BBBBB" }

Development

The server is built with:
- TypeScript for type safety
- @modelcontextprotocol/sdk for MCP server implementation
- @octokit/graphql for GitHub GraphQL API access
- dotenv for environment configuration

Author

Created by ProRanked

License

MIT License - see LICENSE file for details

常见问题

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

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

GitHub Projects MCP 569db2fd 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

GitHub Projects MCP 569db2fd 收费吗?

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

GitHub Projects MCP 569db2fd 需要 API Key 吗?

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

GitHub Projects MCP 569db2fd 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

GitHub Projects MCP 569db2fd 能提供哪些能力?

资料显示能力标签包括 软件开发、团队协作、JavaScript、Claude、问题管理。具体工具清单以官方文档为准。

热门专题

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

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