Project Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection string (e.g., postgresql://username:password@localhost:5432/project_tracker) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_projectC | Create a new project to organize epics and stories |
| list_projectsC | List all projects with optional status filter |
| get_projectB | Get detailed information about a specific project including all its epics and stories |
| update_projectD | Update project information |
| delete_projectB | Delete a project and all its associated epics and stories |
| create_epicC | Create a new epic (idea) within a project |
| list_epicsC | List all epics for a specific project |
| get_epicB | Get detailed information about a specific epic including all its stories |
| update_epicC | Update epic information |
| delete_epicB | Delete an epic and all its associated stories |
| create_storyC | Create a new story within an epic |
| list_storiesC | List all stories for a specific epic |
| get_storyC | Get detailed information about a specific story |
| update_storyC | Update story information |
| delete_storyC | Delete a story |
| get_project_summaryA | Get a comprehensive summary of all projects with counts of epics and stories |
| create_summaryC | Create a new summary/note to track important information, decisions, or AI-generated content |
| list_summariesB | List summaries with optional filters for type, tags, or related entities |
| get_summaryC | Get a specific summary by ID |
| search_summariesC | Search summaries by keyword in title or content |
| update_summaryC | Update an existing summary |
| delete_summaryC | Delete a summary |
| create_status_updateB | Create a status update/report to track progress, blockers, or achievements |
| list_status_updatesC | List status updates with optional filters |
| get_status_updateB | Get a specific status update by ID |
| search_status_updatesC | Search status updates by keyword |
| update_status_updateC | Update an existing status update |
| delete_status_updateC | Delete a status update |
| create_contextB | Save conversation context, chat summaries, or important knowledge to preserve understanding across sessions |
| list_contextC | List saved context entries with optional filters |
| get_contextC | Get a specific context entry by ID |
| search_contextB | Search context entries by keyword to find relevant conversations or knowledge |
| update_contextC | Update an existing context entry |
| delete_contextC | Delete a context entry |
| create_issueC | Create a new issue/bug in a project |
| list_issuesC | List issues for a project with optional filters |
| get_issueA | Get a specific issue by ID |
| search_issuesB | Search issues by keyword |
| update_issueC | Update an existing issue |
| delete_issueC | Delete an issue |
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 40 tools
Each tool maps to a distinct entity and action (project, epic, story, issue, summary, status_update, context), so overlap is minimal. However, get_summary vs. get_project_summary and list_summaries vs. get_project_summary could cause some selection confusion.
All tool names follow a consistent snake_case verb_noun pattern (create_issue, list_projects, get_epic, delete_story, etc.). Compound entities like status_update are handled uniformly.
40 tools is excessive for a project tracker, even with seven entity types. The full CRUD/listing/search surface for every entity creates bloat and increases the risk of agent misselection.
The tool set provides complete CRUD coverage for projects, epics, stories, issues, summaries, status updates, and context, plus search and summary operations. No obvious lifecycle operations appear to be missing.