RTaskmaster 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rtaskmaster_initB | Initialize RTaskmaster Task Master in a project. Creates .rtaskmaster directory with tasks.json. |
| rtaskmaster_get_tasksB | Get all tasks from the project, optionally filtered by status or priority. |
| rtaskmaster_get_taskB | Get detailed information about a specific task or subtask. |
| rtaskmaster_create_taskC | Create a new task. |
| rtaskmaster_update_taskB | Update an existing task. |
| rtaskmaster_delete_taskC | Delete a task. |
| rtaskmaster_set_statusC | Update the status of a task or subtask. |
| rtaskmaster_add_subtaskB | Add a subtask to an existing task. |
| rtaskmaster_next_taskB | Get the next task to work on based on priority and dependencies. |
| rtaskmaster_statsB | Get task statistics and project progress. |
| rtaskmaster_generate_tasks_mdA | Generate a human-readable TASKS.md checklist file from the current tasks. Creates or updates the file in the project root. |
| rtaskmaster_parse_prdB | Parse a PRD (Product Requirements Document) or README file and create tasks from it. Provide either content directly or a file path. |
| rtaskmaster_bulk_statusB | Update the status of multiple tasks at once. |
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 13 tools
Each tool has a clearly distinct purpose: create, read, update, delete tasks, manage subtasks, set status, bulk operations, generate reports, parse PRDs, and get next task. No overlaps.
All tools follow the consistent 'rtaskmaster_' prefix with verb_noun pattern in snake_case (e.g., create_task, update_task, set_status), making naming predictable.
13 tools is well-scoped for a task management server, covering initialization, CRUD, status, subtasks, bulk updates, and reporting without being excessive.
Covers full task lifecycle CRUD, status updates, subtasks, bulk operations, and import from PRDs. Minor gap: no explicit dependency management tool, but dependencies are considered in next_task.