mcp-github-project-manager

MCP GitHub Project Manager

A Model Context Protocol (MCP) server implementation that provides GitHub Projects functionality through standardized tools and resources. This server enables LLM clients and applications to manage GitHub Projects programmatically through the MCP interface.

Overview

This server implements the Model Context Protocol to expose GitHub Projects functionality to LLM clients and applications. It provides tools for managing projects, milestones, sprints, and metrics through GitHub's GraphQL API while maintaining state and handling errors according to MCP specifications.

Table of Contents

• Overview
• Quick Start
• Key Features
• Installation
• Configuration
• Usage
  • As a command-line tool
  • Running from source with TypeScript
  • As a Node.js module
  • Integration with MCP clients
  • Installing in AI Assistants
    • Claude
    • Roocode
    • Windsurf
    • VS Code
    • Cursor
    • Using Docker
  • Troubleshooting
• Architecture
• Contributing
• License
• References
• Current Status

Quick Start

Using NPM

# Install the package globally
npm install -g mcp-github-project-manager

# Set up your environment variables
export GITHUB_TOKEN="your_github_token"
export GITHUB_OWNER="your_github_username_or_organization"
export GITHUB_REPO="your_repository_name"

# Run the MCP server
mcp-github-project-manager

Using Docker

# Build the Docker image
docker build -t mcp-github-project-manager .

# Run with environment variables
docker run -it \
  -e GITHUB_TOKEN=your_github_token \
  -e GITHUB_OWNER=your_github_username_or_organization \
  -e GITHUB_REPO=your_repository_name \
  mcp-github-project-manager

For more details on Docker usage, see .

Key Features

• Project Management

  • Create and manage GitHub Projects (v2)
  • Handle project settings and configurations
  • Manage project visibility and access

• Project Resources

  • Issues and milestones management
  • Sprint planning and tracking
  • Custom fields and views
  • Resource versioning and locking

• MCP Implementation

  • Full MCP specification compliance
  • Standardized tool definitions with Zod validation
  • Resource state management
  • Progressive response handling
  • Comprehensive error handling

• GitHub Integration

  • GraphQL API integration with pagination support
  • Intelligent rate limit handling
  • Optimistic concurrency
  • Webhook support (planned)

Installation

Option 1: Install from npm (recommended)

# Install the package globally
npm install -g mcp-github-project-manager

# Or install in your project
npm install mcp-github-project-manager

Option 2: Install from source

# Clone the repository
git clone https://github.com/kunwarVivek/mcp-github-project-manager.git
cd mcp-github-project-manager

# Install dependencies
npm install
# or
pnpm install

# Build the project
npm run build

Set up environment variables

# Copy the example environment file
cp .env.example .env

# Edit .env with your GitHub token and details

Configuration

Required environment variables:

GITHUB_TOKEN=your_github_token
GITHUB_OWNER=repository_owner
GITHUB_REPO=repository_name

The GitHub token requires these permissions:

• repo (Full repository access)
• project (Project access)
• write:org (Organization access)

Usage

As a command-line tool

If installed globally:

# Start the MCP server using stdio transport
mcp-github-project-manager

# Start with environment variables
GITHUB_TOKEN=your_token mcp-github-project-manager

# Start with command line arguments
mcp-github-project-manager --token=your_token --owner=your_username --repo=your_repo

# Use a specific .env file
mcp-github-project-manager --env-file=.env.production

# Show verbose output
mcp-github-project-manager --verbose

# Display help information
mcp-github-project-manager --help

Running from source with TypeScript

If you're developing or running from source:

# Run directly with ts-node
node --loader ts-node/esm src/index.ts

# Run with command line arguments
node --loader ts-node/esm src/index.ts --token=your_token --owner=your_username --repo=your_repo

# Use the npm dev script (watches for changes)
npm run dev

# Display help information
node --loader ts-node/esm src/index.ts --help

Command Line Options

Command line arguments take precedence over environment variables.

As a Node.js module

import { Server } from "mcp-github-project-manager";

// Create and start an MCP server instance
const server = new Server({
  transport: "stdio", // or "http" for HTTP server
  config: {
    githubToken: process.env.GITHUB_TOKEN,
    githubOwner: process.env.GITHUB_OWNER,
    githubRepo: process.env.GITHUB_REPO
  }
});

server.start();

Integration with MCP clients

// Example using an MCP client library
import { McpClient } from "@modelcontextprotocol/client";
import { spawn } from "child_process";

// Create a child process running the MCP server
const serverProcess = spawn("mcp-github-project-manager", [], {
  env: { ...process.env, GITHUB_TOKEN: "your_token" }
});

// Connect the MCP client to the server
const client = new McpClient({
  transport: {
    type: "process",
    process: serverProcess
  }
});

// Call MCP tools
const result = await client.callTool("create_project", {
  title: "My Project",
  description: "A new GitHub project"
});

For more examples, see the and the directory.

Installing in AI Assistants

Install in Claude

To install the MCP server in Claude Desktop:

{
  "mcpServers": {
    "github-project-manager": {
      "command": "npx",
      "args": ["-y", "mcp-github-project-manager"],
      "env": {
        "GITHUB_TOKEN": "your_github_token",
        "GITHUB_OWNER": "your_username",
        "GITHUB_REPO": "your_repo"
      }
    }
  }
}

For Claude Code CLI, run:

claude mcp add github-project-manager -- npx -y mcp-github-project-manager

Install in Roocode

Add this to your Roocode configuration:

{
  "mcpServers": {
    "github-project-manager": {
      "command": "npx",
      "args": ["-y", "mcp-github-project-manager"],
      "env": {
        "GITHUB_TOKEN": "your_github_token",
        "GITHUB_OWNER": "your_username",
        "GITHUB_REPO": "your_repo"
      }
    }
  }
}

Install in Windsurf

Add this to your Windsurf MCP config file:

{
  "mcpServers": {
    "github-project-manager": {
      "command": "npx",
      "args": ["-y", "mcp-github-project-manager"],
      "env": {
        "GITHUB_TOKEN": "your_github_token",
        "GITHUB_OWNER": "your_username",
        "GITHUB_REPO": "your_repo"
      }
    }
  }
}

See Windsurf MCP docs for more information.

Install in VS Code

Add this to your VS Code MCP config file:

{
  "servers": {
    "github-project-manager": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-github-project-manager"],
      "env": {
        "GITHUB_TOKEN": "your_github_token",
        "GITHUB_OWNER": "your_username",
        "GITHUB_REPO": "your_repo"
      }
    }
  }
}

See VS Code MCP docs for more information.

Install in Cursor

Add this to your Cursor MCP config file:

{
  "mcpServers": {
    "github-project-manager": {
      "command": "npx",
      "args": ["-y", "mcp-github-project-manager"],
      "env": {
        "GITHUB_TOKEN": "your_github_token",
        "GITHUB_OWNER": "your_username",
        "GITHUB_REPO": "your_repo"
      }
    }
  }
}

See Cursor MCP docs for more information.

Using Docker

If you prefer to run the MCP server in a Docker container:

1. Build the Docker Image:

   Create a Dockerfile in your project directory:

   FROM node:18-alpine
   
   WORKDIR /app
   
   # Install the package globally
   RUN npm install -g mcp-github-project-manager
   
   # Default command to run the server
   CMD ["mcp-github-project-manager"]
   

   Build the image:

   docker build -t github-project-manager-mcp .
   

2. Configure Your MCP Client:

   Update your MCP client's configuration to use the Docker command:

   {
     "mcpServers": {
       "github-project-manager": {
         "command": "docker",
         "args": ["run", "-i", "--rm", "github-project-manager-mcp"],
         "env": {
           "GITHUB_TOKEN": "your_github_token",
           "GITHUB_OWNER": "your_username",
           "GITHUB_REPO": "your_repo"
         }
       }
     }
   }
   

Troubleshooting

Common Issues

1. Module Not Found Errors

   If you encounter module resolution issues, try using bunx instead of npx:

   {
     "mcpServers": {
       "github-project-manager": {
         "command": "bunx",
         "args": ["-y", "mcp-github-project-manager"]
       }
     }
   }
   

2. Windows-Specific Configuration

   On Windows, you may need to use cmd to run the command:

   {
     "mcpServers": {
       "github-project-manager": {
         "command": "cmd",
         "args": [
           "/c",
           "npx",
           "-y",
           "mcp-github-project-manager"
         ]
       }
     }
   }
   

3. Permission Issues

   If you encounter permission issues, make sure your GitHub token has the required permissions listed in the Configuration section.

Architecture

The server follows Clean Architecture principles with distinct layers:

• Domain Layer: Core entities, repository interfaces, and Zod schemas
• Infrastructure Layer: GitHub API integration and implementations
• Service Layer: Business logic coordination
• MCP Layer: Tool definitions and request handling

See for detailed architecture documentation.

Contributing

Contributions are welcome! Please see for guidelines.

1. Fork the repository
2. Create a feature branch: git checkout -b feature/amazing-feature
3. Commit your changes: git commit -m 'Add some amazing feature'
4. Push to the branch: git push origin feature/amazing-feature
5. Open a Pull Request

License

This project is licensed under the MIT License - see the file for details.

References

• Model Context Protocol
• GitHub Projects API

Current Status

Core Features

MCP Implementation

See for detailed implementation status. | Resource Management | ✅ Complete | With optimistic locking and relationship tracking | | Response Handling | ✅ Complete | Rich content formatting with multiple content types | | Error Handling | ✅ Complete | Comprehensive error mapping to MCP error codes | | State Management | ✅ Complete | With conflict resolution and rate limiting |

Recent Improvements

• Enhanced Resource System:

  • Added Zod schema validation for all resource types
  • Implemented resource relationship tracking
  • Created a centralized ResourceFactory for consistent resource access

• Improved GitHub API Integration:

  • Added intelligent rate limiting with automatic throttling
  • Implemented pagination support for REST and GraphQL APIs
  • Enhanced error handling with specific error types

• Advanced Tool System:

  • Created tool definition registry with Zod validation
  • Implemented standardized tool response formatting
  • Added example-based documentation for all tools

• Rich Response Formatting:

  • Added support for multiple content types (JSON, Markdown, HTML, Text)
  • Implemented progress updates for long-running operations
  • Added pagination support for large result sets

Identified Functional Gaps

Despite the recent improvements, the following functional gaps still exist and are prioritized for future development:

1. Persistent Caching Strategy:

   • While the ResourceCache provides in-memory caching, it lacks persistence across server restarts
   • No distributed caching for multi-instance deployments
   • Missing cache eviction policies for memory management

2. Real-time Event Processing:

   • No webhook integration for real-time updates from GitHub
   • Missing event-based subscription system for clients
   • Lack of server-sent events (SSE) support for streaming updates

3. Advanced GitHub Projects v2 Features:

   • Limited support for custom field types and validation
   • Incomplete integration with GitHub's newer Projects v2 field types
   • Missing automation rule management

4. Performance Optimization:

   • No query batching for related resources
   • Missing background refresh for frequently accessed resources
   • Incomplete prefetching for related resources

5. Data Visualization and Reporting:

   • No built-in visualization generators for metrics
   • Missing report generation capabilities
   • Limited time-series data analysis

See for detailed implementation status.

Documentation

• - Detailed usage instructions
• - Comprehensive tool documentation
• - Step-by-step guides
• - Code examples for common tasks
• - System architecture and design
• - Development guidelines
• - MCP-specific details

Interactive Documentation

For an interactive exploration of the API, open the in your browser.

Development

Testing

# Unit tests
npm test

# Integration tests
npm run test:integration

# End-to-end tests
npm run test:e2e

Code Quality

# Lint code
npm run lint

# Type check
npm run type-check

# Format code
npm run format

Contributing

We welcome contributions to the GitHub Project Manager MCP Server! Please see our for details on:

License