Skip to main content
Glama
feodal01

task-tracker-mcp

by feodal01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_taskA

Creates a new task (or subtask) in the single task tree. Args: description: Task description dod: Definition of Done (optional) deadline: Deadline (optional, ISO8601 string or datetime) assignee: Assignee (optional) parent_id: Parent task ID (if not specified, will be added to the root)

update_taskA
Updates an existing task. You can update any of the following fields:

Args:
    task_id (str): ID of the task to update.
    description (str, optional): New description for the task.
    dod (str, optional): New Definition of Done for the task.
    deadline (str, optional): New deadline for the task.
    assignee (str, optional): New assignee for the task.

Any combination of these fields can be provided. Only non-null values will be updated.
update_statusC

Closes a task. Args: task_id: Task ID status: Status (todo/done/cancelled/in_progress) reason: Close reason (optional)

delete_taskC

Deletes a task. Args: task_id: Task ID

get_taskC

Retrieves information about a task. Args: task_id: Task ID

test_toolA

Test function for checking MCP server health.

list_tasksA

Returns a list of all tasks in the tree (including subtasks).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct action: create, update fields, update status, delete, get, list, and health check. There is no real overlap between updating task fields and updating task status.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern like create_task, update_task, delete_task, get_task, and list_tasks. Minor inconsistencies include update_status instead of update_task_status and the non-domain test_tool.

Tool Count5/5

Seven tools is well-scoped for a task tracker: core CRUD, status transitions, and listing are all covered without unnecessary redundancy. Each tool earns its place.

Completeness4/5

The surface covers create, read, update, delete, status changes, and listing, which is solid for basic task tracking. The main gap is the lack of an operation to move a task within the task tree after creation, since parent_id is only supported on create.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources