atlas-mcp-server
by cyanheads
Verified
get_tasks_by_path
Find tasks matching a path pattern.
When to Use:
- Analyzing specific project areas
- Reviewing component progress
- Planning related tasks
- Identifying gaps in coverage
Best Practices:
- Use specific patterns for focused results
- Include wildcards for broader searches
- Consider task hierarchy in patterns
- Combine with status checks for detailed analysis
Example: { "pathPattern": "project//security/", "reasoning": "Searching for all security-related tasks across project components to ensure comprehensive security coverage and identify any missing security considerations." }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pathPattern | Yes | Glob pattern for matching task paths: - Use * for any segment - Use ** for recursive matching - Examples: - project/* (top-level tasks) - project/backend/** (all backend tasks) - */security/* (security tasks anywhere) |