MCP: Access and aggregate timelines from all my workstations via on-prem ManicTime Server
I’m using the latest beta with MCP Server and I’d like support for querying timelines from my on-prem ManicTime Server across all environments linked to my same user account.
I often work across multiple machines (local workstation + remote desktop via RDP). Today, my local timeline mostly shows Remote Desktop Connection, while the detailed activity (Applications, Documents, Websites, etc.) is captured on the remote workstation timeline. This splits my work context across devices and makes MCP-based analysis incomplete unless I manually reconcile timelines.
I’d like MCP to support cross-workstation timeline access and aggregation for a single user identity, sourced from on-prem server data.
What I’m asking for
Ability for MCP to query timelines from multiple environments/workstations under the same ManicTime user account.
Ability to filter by environment and/or aggregate results across environments in one request.
Consistent support for core timeline/summary types (Applications, Documents, Websites, Tags, Computer Usage) across those environments.
Optional de-duplication/merge logic for overlapping intervals when combining timelines.
Why this matters
RDP-heavy workflows are common, and local-only timeline access misses most real activity context.
Cross-device visibility would significantly improve accuracy of reporting, tagging, and analytics.
This would make MCP much more useful for users working in hybrid local/remote setups with on-prem ManicTime Server.
Example outcome
A single MCP query for “my activity from 2026-03-09 08:00–17:00” returns a combined timeline view from both my local machine and remote workstation(s), with environment metadata preserved.
Arnie Cilliers
shared this idea
-
Seton Carmichael
commented
Yes! This would be incredible!
Having an MCP endpoint available on the One Prem server itself would be perfect! Could probably reuse a lot of the work put into the one made for ManicTime Cloud.
My specific use case is so I can query call logs/location data from my phone as well as my in Desktop and my field laptop.
I do think the dedupe mentioned above is useful, but it shouldn't be something that holds up an initial beta release as I imagine it'll take a while to find a good middle ground between context efficiency and utility.
-
Arnie Cilliers
commented
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.