Note: Available only to Beta customers for now. The Time Doctor MCP is available on all Time Doctor subscription plans and can be accessed by Owners, Admins, and Managers.
TL;DR
Include seven details when reporting a bug in the Time Doctor MCP: the exact question asked, the expected result, the actual result, the tool call details from the chat, the AI tool used, the timezone in use, and whether the issue repeats. A feature request should describe the underlying goal, not just the missing tool. Feedback needs no set format — plain impressions are useful, especially during the first hour after setup. Send all three types of reports to support@timedoctor.com, with Time Doctor MCP in the subject line.
Reporting a Bug
Something connected but gave a wrong answer, failed, or behaved oddly? Include the following seven details in the report.
- The exact question asked.
Paste the exact wording rather than describing it from memory. Small differences in phrasing change which data the AI assistant requests, so exact wording matters. - The expected result.
State what "correct" would have looked like. The answer is often technically right but not what was meant — a different kind of fix applies in that case. - The actual result.
Include the full reply, an error message, or a screenshot of the entire answer, not just the part that looked wrong. - The tool call details from the chat.
This is the most important detail. It shows exactly what the AI assistant asked Time Doctor for and what came back. See How to Copy the Tool Details below. - The AI tool used.
Different tools request data from Time Doctor in different ways, and each has its own quirks. Knowing whether it was Claude, ChatGPT, Cursor, or another tool often narrows the cause immediately. Include the version number where available. - The timezone in use.
Many reports turn out to be timezone differences rather than incorrect numbers. The AI assistant may have used a different timezone than the one set in Time Doctor reports, which shifts totals at the start and end of a date range. This one detail resolves a large share of tickets on its own. - Whether the issue happens every time.
This determines where to look. An issue that fails consistently is usually reproducible and fixable directly. An issue that happened once may point to a timeout or a temporary condition and needs a different kind of investigation. If it only happened once, note what was different about that occurrence, if known.
How to Copy the Tool Details
When the AI assistant uses Time Doctor, the chat shows what it did. This usually appears as a small, collapsed block near the answer, with a name such as td_get_time_summary.
In most AI tools:
- Find the block in the chat where the assistant called Time Doctor. It normally sits just above the answer.
- Click the block to expand it. The request sent and the response received both appear.
- Copy everything in the expanded block.
- Paste it into the support email, below the question asked and the answer received.
If the block cannot be found, do not worry — send the first three details above, along with a screenshot of the whole conversation, and the support team will work from that.
Before Sending: Check What Is Being Shared
Review tool call details before pasting them into an email. They can include information such as team names and hours, so include only what relates to the problem. Never send an API key or credentials by email. If a key may have been exposed, revoke it and create a new one from Settings / AI Connections.
Requesting a Feature
Missing a tool, a data type, or an AI tool that Time Doctor does not yet support? Include the following in the request:
- The goal, described in plain terms. The goal matters more than the specific feature requested, since there may already be a way to accomplish it today.
- The exact question that would be asked of the AI assistant, written out as it would be typed.
- How often the feature would be used, and who else on the team would use it.
- What is used instead today, if anything.
Requests that describe a real workflow are prioritized more easily than requests for a feature alone, since the underlying need is clearer.
Sending Feedback
Feedback does not need a specific format. Useful feedback includes what worked, what felt clumsy, and what was expected to happen but did not. Answers that were technically correct but not useful are especially worth reporting, since these are the hardest issues to catch internally.
The first hour after setting up the AI connection (MCP) produces the most useful feedback. Anything confusing during that hour is likely confusing to everyone.
Where to Send It
Send bug reports, feature requests, and feedback to support@timedoctor.com, with Time Doctor MCP in the subject line. Send the email from the address associated with the Time Doctor account where possible, since this helps confirm the workspace, plan, and role.
Should there be any inconsistencies or concerns regarding the article, contact support@timedoctor.com for prompt assistance.