tpm-mcp
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roadmap_viewA | PROJECT MANAGEMENT (TPM): Get project roadmap showing work status. USE THIS TOOL WHEN:
Returns summary of organizations, projects, and tickets. Use project_id filter to reduce output. |
| ticket_createA | PROJECT MANAGEMENT (TPM): Create a new ticket, epic, or issue to track. USE THIS TOOL WHEN:
Use roadmap_view first to get the project_id. Tickets are high-level work items (like Jira epics/stories). ID AUTO-GENERATION: IDs are always auto-generated as {PREFIX}-{NNN} (e.g., FEAT-001, ISSUE-042). The number is automatically incremented based on existing tickets with that prefix. OPTIONAL PREFIX PARAMETER: Provide a prefix to categorize the ticket type:
If no prefix is provided, uses the project ID as the prefix (e.g., FRONTEND-001, BACKEND-042). |
| ticket_updateA | PROJECT MANAGEMENT (TPM): Update a ticket's status, priority, or details. USE THIS TOOL WHEN:
Use roadmap_view first to find the ticket_id. |
| ticket_listA | PROJECT MANAGEMENT: List ticket IDs with status/priority. Returns id, status, priority only - use ticket_get for details. |
| ticket_searchA | PROJECT MANAGEMENT (TPM): Search tickets by keyword. USE THIS TOOL WHEN:
Searches title and description. Supports prefix matching (e.g., "org" matches "organization"). Case-insensitive. All filters are combinable. |
| ticket_getA | PROJECT MANAGEMENT: Get info about a ticket and its tasks. IMPORTANT: Do NOT pass detail='full' unless explicitly asked for full/all details. The default 'summary' is sufficient for most queries. Only use 'full' when user specifically asks for implementation details, metadata, or complete task information. |
| task_getA | PROJECT MANAGEMENT: Get full details of ONE specific task. Use this to drill into a single task's implementation details (metadata, files_to_modify, technical_notes). Prefer ticket_get for overview, use this only when you need deep task details. |
| task_createA | PROJECT MANAGEMENT (TPM): Create a task (sub-item) under a ticket. USE THIS TOOL WHEN:
|
| task_updateA | PROJECT MANAGEMENT (TPM): Update a task's status or details. Use when completing or updating task progress. |
| task_listA | PROJECT MANAGEMENT (TPM): List task IDs with status. Returns id, ticket_id, status only - use task_get for details. |
| note_addB | PROJECT MANAGEMENT (TPM): Add a note/comment to a ticket or task for context or decisions. |
| note_listA | PROJECT MANAGEMENT (TPM): List notes for an entity. Returns id, created_at, preview (first 100 chars). Use note_get for full content. |
| note_getB | PROJECT MANAGEMENT (TPM): Get full content of a specific note by ID. |
| org_listB | PROJECT MANAGEMENT: List all organizations. Usually only one org exists. |
| org_createA | PROJECT MANAGEMENT: Create a new organization (rarely needed). |
| project_listC | PROJECT MANAGEMENT: List projects in an organization. |
| project_createC | PROJECT MANAGEMENT: Create a new project under an organization. |
| infoA | Get information about the tracker MCP server: database location, stats, and usage. |
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 18 tools
Most tools have distinct purposes targeting specific entities (notes, orgs, projects, tasks, tickets), but some overlap exists between note_get/note_list and ticket_get/ticket_list where the 'get' vs 'list' distinction is clear but could still cause minor confusion. The roadmap_view tool is well-scoped for status overviews, and search functions are appropriately separated.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., note_add, org_list, project_create, ticket_search). The pattern is maintained across all 18 tools, making them predictable and easy to understand at a glance.
With 18 tools, the count is slightly high but reasonable for a project management domain that covers multiple entities (notes, orgs, projects, tasks, tickets). Each tool appears to serve a specific function, though some could potentially be consolidated (e.g., note_get and note_list).
The toolset provides comprehensive CRUD/lifecycle coverage for the project management domain, including create, get, list, update, and search operations for notes, organizations, projects, tasks, and tickets. There are no obvious gaps, and tools like roadmap_view and ticket_search enhance workflow completeness.