GitHub Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub personal access token with repo, read:org, and read:project permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_team_statusB | Get current status of the development team including active issues, due items, and recent completions for each team member |
| get_person_scheduleB | Get the schedule and upcoming work for a specific team member |
| analyze_workloadB | Analyze team workload distribution and identify who can take on new tasks |
| find_best_assigneeB | Find the team member with the lightest workload for assigning new tasks |
| get_calendar_eventsC | Get GitHub project calendar events with optional filtering |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools have distinct purposes, but analyze_workload and get_team_status overlap in providing team-level insights, which could cause minor confusion. The other tools (find_best_assignee, get_calendar_events, get_person_schedule) are clearly differentiated.
All tool names follow a consistent verb_noun pattern (e.g., analyze_workload, get_calendar_events) with clear, descriptive verbs and nouns. There are no deviations in style or convention.
With 5 tools, the server is well-scoped for managing team workload and schedules in a GitHub context. Each tool serves a specific, non-trivial function, making the count appropriate for the domain.
The toolset covers key aspects of team management (analysis, assignment, event retrieval, schedules, and status), but lacks CRUD operations for calendar events (e.g., create or update events), which is a minor gap agents might need to work around.