timedoctor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Whether to run the browser in headless mode (default: true) | true |
| TD_EMAIL | Yes | Your Time Doctor email address | |
| TD_BASE_URL | No | Base URL of your Time Doctor instance (default: https://2.timedoctor.com) | https://2.timedoctor.com |
| TD_PASSWORD | Yes | Your Time Doctor password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_reportB | Get time tracking report for a specific date from Time Doctor |
| export_weekly_csvA | Get time tracking data for a date range in CSV or JSON format. Maximum 7 days per request (one week). For longer periods, split into multiple requests (e.g., 30 days = 5 weekly requests). Returns data as text that you can save or analyze. Supports parallel scraping for faster retrieval. |
| get_hours_summaryB | Get a quick breakdown of hours by project for a specific date |
| export_today_csvB | Get today's time tracking data in CSV format. Returns CSV data as text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Tools have distinct purposes: CSV export for today vs week, a detailed daily report, and a project summary. Minor overlap between export_today_csv and get_daily_report, but descriptions clarify different output formats.
Two tools use 'export' and two use 'get', which is inconsistent. Additionally, one tool includes the format in its name while others do not. However, the names are still readable and follow a verb_noun pattern.
With 4 tools, the server covers essential reporting needs for time tracking: exporting, daily report, and summary. The count feels appropriate for its scope, though it could be slightly expanded.
The tools cover common retrieval tasks but lack CRUD operations like creating or updating time entries. For a reporting-focused server, this is acceptable, but missing list or search tools for projects or users create gaps.