mm_get_task_context

Get dynamically-derived context for a specific task. Returns primary files, reference files, test files, similar completed examples, and decisions — scoped to exactly what’s needed for the task. Works with both spec tasks (by spec_folder + task_id) and standalone tasks (by filename).

At a Glance

• Category: Workflows
• Source: Built-in
• Required parameters: 1
• Total parameters: 5

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root
spec_folder	string	No	Spec folder name (for spec tasks)
task_id	string	No	Task ID within spec (e.g., ‘T4’)
standalone_task	string	No	Standalone task filename (e.g., ‘fix-login-03-24-2026.md’)
token_budget	number	No	Max approximate tokens for output (default: 8000)

Example

{
  "tool": "mm_get_task_context",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "spec_folder": "example-spec_folder",
    "task_id": "my-example"
  }
}

Related Tools

• mm_plan_feature - Create a complete feature scaffold in one call — creates the feature, creates…
• mm_daily_brief - Generate a structured morning summary with active tasks, blockers, recently c…
• mm_suggest_next - Recommend what to work on next based on in-progress tasks, feature priority, …
• mm_get_guidance - Get contextual guidance suggestions based on project state
• mm_start_task - Mark a task as in-progress and return context for starting work — spec conten…