PM Context MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_sprint_toolA | Get the active sprint: issues breakdown, completion percentage, in-progress work, blockers, and days remaining. |
| get_my_issues_toolA | Get all issues assigned to a team member, sorted by priority. Use the person's full name (e.g. 'Priya Sharma'). |
| get_blockers_toolA | Get all issues currently flagged as blocked, including the blocking reason and the assignee responsible for resolving them. |
| search_issues_toolA | Search for issues by keyword. Matches against issue title and description. Returns matching issues with status, priority, and assignee. |
| get_roadmap_toolA | Get the product roadmap: all epics with completion percentage, issue counts, status, and target dates. |
| get_team_workload_toolA | Get issue count per team member, with breakdown by status. Optionally filter by team name (e.g. 'Growth', 'Core') or sprint ID. Defaults to the active sprint if no filters are provided. |
| get_velocity_toolA | Get sprint-over-sprint velocity: planned vs completed story points for all past sprints, plus average completion rate. |
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 7 tools
Each tool targets a distinct aspect of PM context: current sprint, assignee issues, blockers, keyword search, roadmap, workload, and velocity. There is no overlap that would cause an agent to select the wrong tool for a given query.
All tools follow a consistent [verb]_[noun]_tool pattern using snake_case. The only non-get verb is 'search', but it still fits the same structure, making the naming predictable and uniform.
With 7 tools, the server is well-scoped for its purpose of providing PM context. Each tool covers a distinct read-only query without unnecessary redundancy or bloat.
The server covers core PM context areas like sprint status, issues, blockers, roadmap, workload, and velocity. However, it lacks a direct way to fetch all issues for a specific sprint or retrieve a single issue by ID, requiring search instead. These are minor gaps but not fatal.