Get the FREE Ultimate OpenClaw Setup Guide →

github-calendar

MCP Server for GitHub project calendar integration with team management features

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio blackgirlbytes-github-calendar-mcp-server node /full/path/to/github-calendar-mcp-server/index.js \
  --env GITHUB_TOKEN="your_github_token_here"

How to use

This MCP server provides GitHub project calendar and team management capabilities. It exposes tools to fetch calendar events from GitHub projects, inspect team workloads and statuses, analyze workload distribution, and smartly assign new tasks to team members based on current load. You can interact with it via MCP-enabled assistants (like Goose) by invoking the available tools such as get_calendar_events, get_team_status, get_person_schedule, analyze_workload, and find_best_assignee. The server is designed to pull data from GitHub using a Personal Access Token and present it in calendar-like, date-oriented formats suitable for scheduling and planning.

How to install

Prerequisites:

  • Node.js v16+ installed on your system
  • npm or yarn
  • A GitHub Personal Access Token with at least repo, read:org, and read:project permissions

Installation steps:

  1. Create a project directory and install dependencies mkdir github-calendar-mcp-server cd github-calendar-mcp-server npm init -y npm install

  2. Configure environment

    • Create a .env file or export environment variables in your shell
    • Example (bash): export GITHUB_TOKEN=your_github_personal_access_token
  3. Run the server npm start

  4. Alternative: run with a specific node script path (as used in MCP config) node /full/path/to/github-calendar-mcp-server/index.js

  5. Verify access and connections Ensure the GITHUB_TOKEN has the required permissions and that the server starts without errors.

Additional notes

Tips and caveats:

  • Make sure the GITHUB_TOKEN has access to the organizations, projects, and issues you intend to query.
  • The server defaults target organization 'squareup', project 333, and label filter 'area: devrel-opensource'. These defaults can be edited in the index.js file if you need different scopes.
  • If you hit API rate limits, consider implementing caching or staggering requests, and monitor error handling paths for fallbacks to REST API when GraphQL queries fail.
  • The provided tools are designed to be called via MCP prompts; for integration with Goose, reference the tool names exactly as listed (get_calendar_events, get_team_status, get_person_schedule, analyze_workload, find_best_assignee).
  • Ensure Node.js permissions allow executing index.js and that network access to GitHub APIs is available.

Related MCP Servers

Sponsor this space

Reach thousands of developers