my_pm_tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Classic Personal Access Token with scopes: project, repo, read:org |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_list_fieldsA | List all fields and their options in a GitHub Project V2 |
| project_list_itemsC | List all items in a GitHub Project V2 with status and metadata |
| project_sprint_reportB | Generate a sprint report with velocity, completion rate, and blocker stats |
| project_get_issueA | Get detailed information about a specific issue by number |
| project_add_itemA | Add an Issue or Pull Request to a GitHub Project V2 |
| project_move_statusB | Change the status of a project item (e.g. 'Backlog', '開発中', 'Done'). Supports aliases like 'dev'→'開発中' |
| project_set_priorityA | Set the priority of a project item (P0-P4) |
| project_create_issueB | Create a new issue in a repository (supports Japanese title and body) |
| project_edit_issueA | Edit the title and/or body of an issue |
| project_manage_labelsA | Add or remove labels on an issue |
| project_manage_assigneesA | Add or remove assignees on an issue |
| project_set_issue_stateB | Close or reopen an issue |
| notion_searchB | Search Notion workspace for pages and databases by title |
| notion_get_pageA | Get a Notion page with its content converted to Markdown (recursive block fetch) |
| notion_query_databaseA | Query a Notion database with optional filter and sort (JSON filter/sort syntax) |
| notion_create_pageA | Create a new Notion page under a database or page with optional paragraph content |
| notion_append_blocksA | Append paragraph blocks to an existing Notion page or block |
| notion_update_pageB | Update properties on an existing Notion page (title, status, select, date, etc.) |
| notion_archive_pageA | Archive or unarchive a Notion page (archive=true to archive, archive=false to unarchive) |
| workspace_search_driveC | Search Google Drive for files by query and optional MIME type filter |
| workspace_get_docA | Get a Google Docs document exported as Markdown via Drive export API |
| workspace_get_sheetA | Get values from a Google Sheets range (first row as headers, rest as data rows) |
| workspace_get_slidesA | Get a Google Slides presentation exported as plain text via Drive export API |
| workspace_list_eventsA | List events from a Google Calendar with optional time range filter |
| workspace_search_gmailA | Search Gmail messages and return subject, from, date, and snippet for each |
| workspace_update_sheetA | Update cell values in a Google Sheets range (PUT — overwrites the range completely) |
| workspace_append_sheetA | Append rows to a Google Sheets table (POST — adds rows after the last row in the table) |
| workspace_create_eventA | Create a Google Calendar event (timed or all-day). Supports RFC3339 datetimes and IANA timezones. |
| project_scan_zombiesA | Scan for zombie issues (implemented but still Open). Cross-references code, commits, and issue titles. Never auto-closes — returns proposals only. |
| project_scan_todosA | Scan codebase for TODO/FIXME/HACK/XXX markers, cross-reference with existing issues, and propose new issue creation. Set createIssues=true to auto-create (max 10/run). |
| project_backlog_reportA | Generate a comprehensive backlog health report: zombie issues, untracked TODOs, stale issues, priority distribution, and a 0-100 health score. |
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 31 tools
Tools are clearly grouped by prefix (notion_, project_, workspace_) and each tool has a distinct purpose. No two tools could be easily confused, as the verb-noun combinations are unique within each domain.
The naming convention is predominantly prefix_verb_noun, which is consistent across most tools. However, 'project_backlog_report' and 'project_sprint_report' deviate by using a noun-noun pattern instead of verb-noun, creating a minor inconsistency.
With 31 tools, the server is on the heavier side. The tool count is appropriate given it covers three distinct domains (Notion, GitHub Projects, Google Workspace), but it exceeds the typical well-scoped range of 3-15 tools, making it feel somewhat overloaded.
The tool surface covers core CRUD operations for the main resources (pages, issues, sheets, events) and includes search, scanning, and reporting. Missing operations like deletion or updating events are minor gaps that do not severely hinder common PM workflows.