Hosting

Self-hosted local process.

Transport

stdio.

Endpoint

Local process; no hosted endpoint documented

Authentication

No Task Master account credential is required to start the server. Model-provider API keys may be needed when a selected Task Master workflow calls that provider; the project also documents MCP sampling for compatible clients.

Requirements

• Node.js 20 or newer per the package metadata checked during catalog research.
• npm/npx.
• Optional API credentials only for the chosen provider/model workflow; do not place actual secrets in catalog records.

Setup steps

1. Configure a stdio MCP server with command `npx` and args `-y`, `task-master-ai`; this is the package manifest's MCP configuration.
2. If a selected model provider requires an API key, create the key in that provider's official developer console and enter it in the client's local secure environment/config mechanism. The MCP can also use client sampling where supported.
3. Optionally set the documented `TASK_MASTER_TOOLS` profile to restrict or expand the server's tool set. The default/core profile is smaller; inspect the current configuration guide before changing it.
4. Restart/reconnect the client and inspect tools/list. Start with read-only planning tools; task status and project-planning tools can modify local project data.

Official docs describe core, standard, and all tool profiles. Core examples include the names below; documentation sources disagree on the total count for the all profile (36 in the configuration guide versus 44 in the package manifest). Profile and version affect the actual tools/list result.

• get_tasks

  Read the project's task list.

  01
• next_task

  Identify the next task according to the configured task state.

  02
• get_task

  Read one task by ID.

  03
• set_task_status

  Update a task's status.

  04
• update_subtask

  Update a subtask.

  05
• parse_prd

  Parse product requirements into structured tasks.

  06
• expand_task

  Expand a task into subtasks.

  07

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• The project is independently maintained; do not present it as an official Atlassian, Linear, or other task vendor integration.
• Some workflows require a supported model-provider credential, or an MCP client that supports sampling.
• Tool counts vary by selected profile and the current docs conflict about the all-profile count.
• Task operations can write local project state; no task mutation was tested.
• Documentation and logo were reviewed; MCP initialization, tools/list, and a representative tool call were not tested.

• The Task Master configuration guide documents 36 tools for the all profile, while the package manifest currently documents 44. The saved record therefore records tool-profile availability as dynamic and does not claim a verified exact all-profile count.

• official package manifest

  Documents the npm package MCP command, optional provider environment variables, sampling support, and available MCP integration metadata.

• official configuration documentation

  Documents tool profiles, core tool names, provider-key handling, and the 36-tool all-profile count that conflicts with the manifest.

• official project logo asset

  Square project icon from the canonical Task Master repository; decoded and reviewed on light and dark contact sheets. Selection tier C: project-specific logo.

• official or maintainer tool reference

  Maintainer configuration docs show selectable tool profiles and a 36-tool all profile, conflicting with prior seven-tool subset; actual exposure is profile-dependent.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.