Minor Changes
-
#1181
a69d8c9
Thanks @karol-f! - Add configurable MCP tool loading to optimize LLM context usageYou can now control which Task Master MCP tools are loaded by setting the
TASK_MASTER_TOOLS
environment variable in your MCP configuration. This helps reduce context usage for LLMs by only loading the tools you need.Configuration Options:
all
(default): Load all 36 toolscore
orlean
: Load only 7 essential tools for daily development- Includes:
get_tasks
,next_task
,get_task
,set_task_status
,update_subtask
,parse_prd
,expand_task
- Includes:
standard
: Load 15 commonly used tools (all core tools plus 8 more)- Additional tools:
initialize_project
,analyze_project_complexity
,expand_all
,add_subtask
,remove_task
,generate
,add_task
,complexity_report
- Additional tools:
- Custom list: Comma-separated tool names (e.g.,
get_tasks,next_task,set_task_status
)
Example .mcp.json configuration:
{ "mcpServers": { "task-master-ai": { "command": "npx", "args": ["-y", "task-master-ai"], "env": { "TASK_MASTER_TOOLS": "standard", "ANTHROPIC_API_KEY": "your_key_here" } } } }
For complete details on all available tools, configuration examples, and usage guidelines, see the MCP Tools documentation.
-
#1312
d7fca18
Thanks @Crunchyman-ralph! - Improve next command to work with remote