MCP Project Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the SSE server | 8000 |
| DB_PATH | No | Path to the SQLite database file | tasks.db |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskA | Create a new task with a title, optional description, and priority level. |
| list_tasksB | List tasks. Optionally filter by status and/or priority. |
| update_taskA | Update the status of an existing task by its ID. |
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 3 tools
Each tool has a clearly distinct purpose: creation, listing, and status update. No overlap or ambiguity.
All tool names follow the consistent verb_noun pattern with snake_case, making them predictable and easy to use.
Three tools is a minimal but reasonable set for a task manager. Each tool is essential, though the server could benefit from a few more operations.
The server covers create, list, and update status, but misses delete and get details. This is a notable gap for a task management domain.