I’m using the latest ManicTime beta with MCP Server and would like MCP access to the AutoTag timeline.

Right now, AutoTag results are not available (or not consistently queryable) through MCP like other timelines, which limits automation workflows for tagging validation, reporting, and reconciliation.

What I’m asking for

• Include AutoTag timeline in MCP timeline discovery.
• Allow querying AutoTag activity in the same date-range/filter model as other timelines.
• Support environment filtering and cross-environment aggregation when applicable.
• Preserve AutoTag-relevant metadata (for example tag combination, notes, and rule/source fields if available).
• Keep behavior consistent with existing MCP timeline endpoints.

Why this matters

• AutoTag is central to automated categorization workflows.
• Without MCP access to AutoTag, users must do manual/UI reconciliation.
• MCP-based agents and scripts cannot fully validate or improve tagging quality.
• By exposing the AutoTag timeline through MCP, MCP workflows and AI agents can compare AutoTag outcomes with actual activity context and help determine when AutoTag should be used versus when alternate/manual tags are more appropriate.

Example outcome

A single MCP query for my activity window returns Applications/Documents/Websites/Tags/Computer Usage plus AutoTag timeline data, with optional aggregation across environments and preserved environment metadata.