Skip to main content
Glama
chukaibejih

Task Manager MCP Server

by chukaibejih

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_taskB

Create a new task

Args:
    title: Task title (required)
    description: Detailed description of the task
    priority: Task priority (low, medium, high, urgent)
    due_date: Due date in YYYY-MM-DD format
    tags: Comma-separated tags (e.g., "work,urgent,meeting")
list_tasksB

List all tasks with optional filtering

Args:
    status: Filter by status (pending, in_progress, completed, cancelled)
    priority: Filter by priority (low, medium, high, urgent)
get_taskC

Get a specific task by ID

Args:
    task_id: The ID of the task to retrieve
update_taskB

Update an existing task

Args:
    task_id: ID of the task to update
    title: New title for the task
    description: New description for the task
    priority: New priority (low, medium, high, urgent)
    status: New status (pending, in_progress, completed, cancelled)
    due_date: New due date in YYYY-MM-DD format
    tags: New comma-separated tags
delete_taskC

Delete a task

Args:
    task_id: ID of the task to delete
complete_taskC

Mark a task as completed

Args:
    task_id: ID of the task to complete
get_task_summaryB

Get summary statistics for all tasks

Prompts

Interactive templates invoked by user choice

NameDescription
daily_planningCreate a daily planning prompt with current task context Args: focus_area: What to focus on today (e.g., "development", "meetings", "research")
task_breakdownCreate a conversation for breaking down a complex task Args: task_title: The task that needs to be broken down complexity: Task complexity level (simple, medium, complex)
weekly_reviewGenerate a weekly review prompt with task statistics
project_planningCreate a project planning prompt Args: project_name: Name of the project to plan deadline: Project deadline (YYYY-MM-DD format) team_size: Number of people on the team
task_prioritizationCreate a prompt for task prioritization using current tasks

Resources

Contextual data attached and managed by the client

NameDescription
all_tasksGet all tasks as a formatted list
task_summaryGet formatted task summary statistics
overdue_tasksGet all overdue tasks

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct purposes (create, list, get, update, delete), but complete_task overlaps with update_task since the latter can also set status to completed. The descriptions make the distinction clear enough, but it's a minor point of confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: create_task, list_tasks, get_task, update_task, delete_task, complete_task, get_task_summary. No deviations or mixed conventions.

Tool Count5/5

Seven tools provide a well-scoped set covering standard task management operations plus a summary helper. Each tool earns its place without redundancy.

Completeness5/5

The toolset provides full CRUD coverage (create, read, list, update, delete), a dedicated complete action, and summary statistics. No obvious lifecycle gaps for a task manager; filters are available on list_tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues