Arnie Cilliers
My feedback
4 results found
-
5 votes
An error occurred while saving the comment Arnie Cilliers
shared this idea
·
-
267 votes
As of now, MS Teams does not share data about calls, so there is not way to add this feature.
Nov 2023: To our knowledge, this is still not possible
Arnie Cilliers
supported this idea
·
An error occurred while saving the comment Arnie Cilliers
commented
Agree this would be a very welcome addition.
-
7 votes
An error occurred while saving the comment Arnie Cilliers
commented
I really like this idea and too would want to see this against other VOIP/PBX solutions. We use GotoConnect (Jive) as our PBX.
-
29 votes
An error occurred while saving the comment Arnie Cilliers
commented
I think Adam Law is onto something and agree that ManicTime would greatly benefit from a Xero Plug-In.
An error occurred while saving the comment Arnie Cilliers
commented
I am also very interested in a XERO export capabilities.
Maybe the Tag system can be setup where
Tag1 = Xero Customer,
Tag2=Project Reference,
Tag3=Invoice Line
Timesheet Thru Date =Invoice DateThis would allow one to create a summary invoice Summaries by Tag1, Tag2, Tag3 for the Timesheet Period.
Challenges might include:
- how to deal with different gl accounts by Tag
- how to deal with different billing rates by Tag
- adding an attachment to the invoice with full time entry detail, i.e. including notes
- might be more challenges to think about.Arnie Cilliers
supported this idea
·
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.