Which integrations are available for this server?

Integrates with VS Code GitHub Copilot to extract Time Doctor time tracking data. Integrates with Google Gemini CLI to fetch Time Doctor time tracking reports.

How do I use timedoctor-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@timedoctor-mcp show my time report for last week" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

timedoctor-mcp

by frifster

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

Time Doctor MCP

MCP Server for extracting Time Doctor time tracking data via AI assistants.

Buy Me A Coffee

What It Does

Fetches time tracking reports from Time Doctor and returns them as CSV data. Integrates with AI assistants via the Model Context Protocol (MCP).

Supports:

🤖 Claude Desktop & Claude Code
🎯 Cursor IDE
✨ Google Gemini CLI
💻 VS Code with GitHub Copilot

Features:

🚀 Single-session scraping (login once, get multiple dates)
📅 Works with any date range (1 day to 365+ days)
📊 Returns CSV data as text (no file system issues)
⏱️ Parses Time Doctor's "3h 50m" format
📦 Aggregates duplicate tasks
✅ Includes TOTAL row

Related MCP server: EARLY App MCP Server

Installation Methods

Option A: Using uvx (Easiest - No Installation Required)

The simplest way to use Time Doctor MCP is with uvx, which automatically downloads the package from PyPI and runs it locally without manual installation:

Claude Desktop/Code:

{
  "mcpServers": {
    "timedoctor": {
      "command": "uvx",
      "args": ["timedoctor-mcp"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Prerequisites:

Install uv: brew install uv (macOS) or see uv installation
Install Playwright browsers (one-time setup):
```
uvx --with playwright playwright install chromium
```
This downloads the Chromium browser binaries needed for web scraping (~130MB). You only need to run this once.

That's it! No cloning, no virtual environments, no setup scripts. Just add the configuration and restart your AI assistant.

Option B: Clone & Install (For Development)

# Clone the repository
git clone https://github.com/frifster/timedoctor-mcp.git
cd timedoctor-mcp

# Install UV (fastest method)
brew install uv

# Run setup
./setup-with-uv.sh

2. Configure Credentials

Create .env in the project root:

nano .env

Add your Time Doctor credentials:

TD_EMAIL=your-email@example.com
TD_PASSWORD=your-password
TD_BASE_URL=https://2.timedoctor.com
HEADLESS=true

3. Add to Claude Desktop/Code

Edit your Claude MCP configuration:

macOS:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows:

notepad %APPDATA%\Claude\claude_desktop_config.json

Linux:

nano ~/.config/Claude/claude_desktop_config.json

Add this configuration (replace <PATH_TO_REPO> with your actual path):

Option A: Credentials in JSON

{
  "mcpServers": {
    "timedoctor": {
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Option B: Load from .env (Recommended)

{
  "mcpServers": {
    "timedoctor": {
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"]
    }
  }
}

Example paths:

macOS: /Users/yourname/timedoctor-mcp/.venv/bin/python
Linux: /home/yourname/timedoctor-mcp/.venv/bin/python
Windows: C:\Users\yourname\timedoctor-mcp\.venv\Scripts\python.exe

4. Restart Claude

Completely quit and reopen Claude Desktop/Code.

Alternative MCP Clients

This MCP server also works with other AI assistants that support the Model Context Protocol:

Cursor IDE

Edit your Cursor MCP configuration file:

macOS/Linux:

nano ~/.cursor/mcp.json

Windows:

notepad %USERPROFILE%\.cursor\mcp.json

Using uvx (easiest):

{
  "mcpServers": {
    "timedoctor": {
      "command": "uvx",
      "args": ["timedoctor-mcp"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Using local installation (for development):

{
  "mcpServers": {
    "timedoctor": {
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Note: You can also create a project-specific configuration at .cursor/mcp.json in your project root.

Restart Cursor after saving the configuration.

Google Gemini CLI

Edit your Gemini CLI settings:

macOS/Linux:

nano ~/.gemini/settings.json

Windows:

notepad %USERPROFILE%\.gemini\settings.json

Using uvx (easiest):

{
  "mcpServers": {
    "timedoctor": {
      "command": "uvx",
      "args": ["timedoctor-mcp"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      },
      "timeout": 600000
    }
  }
}

Using local installation (for development):

{
  "mcpServers": {
    "timedoctor": {
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      },
      "timeout": 600000
    }
  }
}

Optional settings:

timeout: Request timeout in milliseconds (default: 600,000ms)
trust: Set to true to skip tool confirmations

Restart Gemini CLI after saving the configuration.

VS Code / GitHub Copilot

Create or edit the MCP configuration file:

Workspace-specific (recommended):

mkdir -p .vscode
nano .vscode/mcp.json

User-wide (all workspaces):

macOS: ~/Library/Application Support/Code/User/mcp.json
Linux: ~/.config/Code/User/mcp.json
Windows: %APPDATA%\Code\User\mcp.json

Using uvx (easiest):

{
  "servers": {
    "timedoctor": {
      "type": "stdio",
      "command": "uvx",
      "args": ["timedoctor-mcp"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Using local installation (for development):

{
  "servers": {
    "timedoctor": {
      "type": "stdio",
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"],
      "env": {
        "TD_EMAIL": "your-email@example.com",
        "TD_PASSWORD": "your-password",
        "TD_BASE_URL": "https://2.timedoctor.com",
        "HEADLESS": "true"
      }
    }
  }
}

Using .env file with local installation:

{
  "servers": {
    "timedoctor": {
      "type": "stdio",
      "command": "<PATH_TO_REPO>/.venv/bin/python",
      "args": ["<PATH_TO_REPO>/src/mcp_server.py"],
      "envFile": "<PATH_TO_REPO>/.env"
    }
  }
}

Enable in GitHub Copilot:

Open VS Code Command Palette (Cmd+Shift+P or Ctrl+Shift+P)
Run MCP: Add Server to configure via UI
Or manually edit .vscode/mcp.json as shown above
In Copilot Chat, click the tools icon to see available MCP servers

Restart VS Code after saving the configuration.

Usage

Get data for date range:

Get my Time Doctor data from August 25 to September 5

Today's data:

Show me my Time Doctor hours for today

Last week:

Get my Time Doctor data for the last 7 days

Custom analysis:

Get my Time Doctor data from last month and tell me which project took the most time

Claude will receive CSV data like:

Date,Project,Task,Description,WORK HOUR
08/25/2025,Jira: AYR BMS,ABMS-606,Code Review,5.00
08/25/2025,Jira: AYR BMS,ABMS-700,Bug Fix,3.50
TOTAL,,,,8.50

You can then ask Claude to save it wherever you want!

MCP Tools

1. `export_weekly_csv`

Get time tracking data for any date range in CSV format.

Parameters:

start_date (required): YYYY-MM-DD format
end_date (required): YYYY-MM-DD format

Returns: CSV data as text with summary statistics

2. `get_daily_report`

Get detailed report for a specific date.

Parameters:

date (required): YYYY-MM-DD format or "today"

Returns: Formatted report with project breakdown

3. `get_hours_summary`

Quick hours breakdown by project.

Parameters:

date (required): YYYY-MM-DD format or "today"

Returns: Summary by project

4. `export_today_csv`

Quick access to today's data.

Parameters: None

Returns: Today's CSV data with summary

How It Works

Login: Playwright automation logs into Time Doctor web interface
Navigate: Goes to Projects & Tasks report
Date Navigation: Uses arrow buttons to change dates
Extract: Parses Angular Material tree structure for project/task data
Parse: Converts "3h 50m" format to decimal hours
Aggregate: Combines duplicate tasks
Return: CSV data as text in MCP response

Architecture

Single-Session Efficiency:

Login once
Navigate through all dates in one session
Extract data for each date
Close browser once
Result: 2-3x faster than logging in for each date

CSV Data Format:

Date,Project,Task,Description,WORK HOUR
11/04/2025,Jira: AYR BMS,ABMS-606,Code Review - ABMS-606,0.25
11/04/2025,Jira: AYR BMS,ABMS-4979,Deal template update,2.47
TOTAL,,,,2.72

Date: MM/DD/YYYY format
WORK HOUR: Decimal hours (5.00, 1.50, 0.25)
TOTAL: Sum of all hours

Project Structure

timedoctor-mcp/
├── .env                    # Your credentials (git-ignored)
├── .env.example            # Example configuration
├── requirements.txt        # Python dependencies
├── setup-with-uv.sh       # Setup script
├── src/
│   ├── scraper.py         # Browser automation & login
│   ├── parser.py          # HTML parsing (Angular Material tree)
│   ├── transformer.py     # CSV formatting
│   └── mcp_server.py      # MCP server with 4 tools
└── tests/
    ├── debug_login.py     # Login debugging tool
    ├── test_parser.py     # HTML parsing tests
    ├── test_date_navigation.py  # Date navigation tests
    └── test_complete_flow.py    # End-to-end tests

Troubleshooting

MCP Server Won't Start

Check the log:

tail -f timedoctor_mcp.log

Common issues:

❌ Missing credentials: Add to .env or MCP config
❌ Wrong Python path: Use .venv/bin/python (or .venv/Scripts/python.exe on Windows)
❌ Dependencies not installed: Run ./setup-with-uv.sh
❌ Playwright browsers not installed: Run uvx --with playwright playwright install chromium

Playwright Browser Error

If you see:

Error: BrowserType.launch: Executable doesn't exist at .../chromium_headless_shell-1187/chrome-mac/headless_shell

Solution:

uvx --with playwright playwright install chromium

This is a one-time setup that downloads the browser binaries (~130MB). You only need to run this once per system.

Check log for:

Login failed - still on login page

Solutions:

Verify credentials in .env are correct
Check if Time Doctor requires 2FA (not supported)
Try logging in manually at https://2.timedoctor.com/login
Look for error messages in the log

The scraper logs which email it's using:

TimeDoctorScraper initialized with email: your-email@example.com

No Data Returned

Check log for:

Parsed 0 time entries

Solutions:

Verify you have time tracking data for those dates
Check that "Expand All" button appears on the report page
Try with today's date first to confirm it works
Check log for HTML parsing errors

Claude Not Seeing Tools

Solutions:

Verify config path is correct
Check JSON syntax is valid (use a JSON validator)
Ensure Python path is absolute, not relative
Completely quit and restart Claude
Check Claude settings → MCP Servers

Path Issues

Make sure all paths in your MCP config are absolute paths, not relative:

✅ Good:

macOS/Linux: /Users/name/timedoctor-mcp/.venv/bin/python
Windows: C:\Users\name\timedoctor-mcp\.venv\Scripts\python.exe

❌ Bad:

~/timedoctor-mcp/.venv/bin/python (tilde not expanded)
./timedoctor-mcp/.venv/bin/python (relative path)
timedoctor-mcp/.venv/bin/python (relative path)

Requirements

Python: 3.12 or 3.13 (3.14 not supported yet)
Dependencies: Playwright, BeautifulSoup4, MCP SDK, python-dotenv
System: macOS, Linux, Windows
Time Doctor: Active account with login credentials

Performance

Single-session architecture:

7 days: ~45 seconds (vs ~90 seconds with multiple logins)
30 days: ~3 minutes
Login: 5 seconds (once)
Per date: 3-4 seconds (navigation + extraction)

Security

✅ Credentials stored in .env (git-ignored)
✅ Headless browser (no GUI)
✅ Local execution only
✅ No data sent to third parties
⚠️ Store .env securely (chmod 600 .env recommended)

Development

Test login:

source .venv/bin/activate  # or .venv\Scripts\activate on Windows
python tests/debug_login.py

Test parsing:

python tests/test_parser.py

Test complete flow:

python tests/test_complete_flow.py

View logs:

tail -f timedoctor_mcp.log

Why Web Scraping?

Time Doctor has an API, but this MCP server uses web automation because:

✅ No API token setup needed
✅ Same access as web interface
✅ Works with all Time Doctor plans
✅ More reliable for "Projects & Tasks" report

If you prefer API access, Time Doctor's API is available at: https://api2.timedoctor.com/api/1.0/

Alternative Installation Methods

Manual pip Installation

# Create virtual environment
python3.13 -m venv .venv
source .venv/bin/activate  # or .venv\Scripts\activate on Windows

# Install dependencies
pip install -r requirements.txt

# Install Playwright browsers
playwright install chromium

Using Python venv (without UV)

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
playwright install chromium

Contributing

Contributions welcome! Please feel free to submit issues or pull requests.

License

MIT License - See LICENSE file for details.

Disclaimer

This tool is for personal use and automation of your own Time Doctor data. Ensure you comply with Time Doctor's Terms of Service and your organization's policies when using this scraper.

Support

If this tool saves you time, consider buying me a coffee! ☕

Questions? Check the log file: timedoctor_mcp.log in the project directory

Working? Ask Claude: "Get my Time Doctor data for today"

Available Tools

4 tools

export_today_csvB

Get today's time tracking data in CSV format. Returns CSV data as text.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears full burden. It reveals output format (CSV as text) but omits behavioral details like whether it's read-only, scope (user-specific?), or any limitations. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but contains redundancy: 'Get today's time tracking data in CSV format. Returns CSV data as text.' The second sentence is unnecessary. Could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description covers the basic purpose and output format. However, it lacks details on authentication, data scope, or any constraints, which are reasonable to expect for an export tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so the baseline is 4. The description adds no parameter information, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get', the resource 'today's time tracking data', and the format 'CSV'. It inherently distinguishes from sibling tools like export_weekly_csv by specifying 'today'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., export_weekly_csv, get_daily_report). The description only states what it does, with no exclusions or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
`start_date`	Yes	Start date in YYYY-MM-DD format (e.g., 2025-01-15).
`end_date`	Yes	End date in YYYY-MM-DD format (e.g., 2025-01-21). Maximum 7 days from start_date.
`format`	No	Output format: 'csv' for CSV format (default) or 'json' for JSON format with summary	csv
`parallel`	No	Use parallel scraping: 'auto' (default, chooses based on date age), 'true' (force parallel), 'false' (force sequential). Parallel is 2x faster for recent dates.	auto
`min_hours`	No	Filter out entries with hours less than this value (excludes entries < 6 minutes by default). Set to 0 to disable filter.

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description discloses parallel scraping behavior, min_hours filtering, and output formats. Does not mention potential rate limits or data freshness, but adequately covers key behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three focused sentences, each providing essential information without redundancy. Front-loaded with main purpose, then usage constraints and options.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers date range, format, parallel scraping, and min_hours filter. Lacks details on return format structure and error handling, but sufficient for basic use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters have schema descriptions (100% coverage). The description adds value by explaining the 7-day limit tied to end_date, parallel parameter speed implications, and min_hours filter purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it retrieves time tracking data for a date range in CSV/JSON. Implicitly distinguishes from siblings like 'export_today_csv' by specifying a date range, but could explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says maximum 7 days per request and advises splitting longer periods. Also mentions parallel scraping for faster retrieval. Lacks explicit when-not-to-use or alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_daily_reportB

Get time tracking report for a specific date from Time Doctor

ParametersJSON Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format (e.g., 2025-01-15). Use 'today' for current date.

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It only says 'Get', implying a read operation, but fails to disclose any behavioral traits like required permissions, rate limits, or error handling for invalid dates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one concise sentence that efficiently conveys the core action. However, it lacks any structured breakdown or front-loading of key information beyond the minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool with one parameter and no output schema, the description is adequate but incomplete. It does not mention return format, error conditions, or report contents, which would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with parameter 'date' already documented. The tool description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a time tracking report for a specific date from Time Doctor, which is a specific verb+resource. It distinguishes from sibling tools like export_today_csv or get_hours_summary by focusing on a single date report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., export_today_csv or get_hours_summary). The description lacks any context about eligible scenarios or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_hours_summaryB

Get a quick breakdown of hours by project for a specific date

ParametersJSON Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format (e.g., 2025-01-15). Use 'today' for current date.

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully convey behavioral traits. It only mentions a 'quick breakdown' but does not state whether the operation is read-only, requires authentication, or any other behavioral details (e.g., what happens if date is invalid, rate limits). The description lacks transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is front-loaded with the core purpose. It is concise and to the point, but could be slightly expanded to include usage guidance without becoming verbose. Still, it is effective for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single parameter, no output schema), the description covers the basic purpose. However, it does not mention the output format or any aggregation details, and lacks context on when to prefer this over sibling tools. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the input schema already describes the date parameter format and the 'today' option. The description adds no additional meaning beyond 'specific date', so it provides no extra value over the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get a quick breakdown of hours by project for a specific date', which clearly specifies the verb (Get), resource (breakdown of hours by project), and scope (for a specific date). This distinguishes it from sibling tools like export_today_csv or get_daily_report, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives (e.g., get_daily_report, export_today_csv). No when-to-use, when-not-to-use, or prerequisite information is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv1.3.0Jun 3, 2026
- First observedexport_today_csv
- First observedexport_weekly_csv
- First observedget_daily_report
- First observedget_hours_summary

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Scored 2026-06-03 21:05 across 4 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp-serverOAuth
io.klokin
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
Workplace & Productivity Project Management
2
OneSchema MCP Server
co.oneschema
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Data Platforms App Automation
1
Artificial Wit AIOAuth
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2
mcp-serverOAuth
com.niftypm
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Project Management Communication File Systems
2

Related MCP Servers

actual-mcp
App Automation Finance
s-stefanov
A
license
B
quality
B
maintenance
MCP server for integrating Actual Budget with Claude and other LLM assistants.
Updated 2 days ago (2026-09-10 01:40 UTC)
10
213
226
TypeScript
MIT
EARLY App MCP Server
Workplace & Productivity Project Management
janfincke
A
license
A
quality
A
maintenance
An MCP server that provides AI assistants with access to the EARLY time tracking public API, enabling time entry management, activity management, and report generation through natural language.
Updated a month ago (2026-08-08 10:20 UTC)
14
22
MIT
Hubstaff MCP Server
Project Management Workplace & Productivity
cdmx-in
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server for Hubstaff API integration, enabling seamless time tracking, project management, and team collaboration through AI assistants.
Updated a year ago (2025-07-14 04:14 UTC)
4
MIT
hubstify-mcp
Project Management Workplace & Productivity
farce1
A
license
B
quality
C
maintenance
MCP server enabling natural language interaction with Hubstaff data, including organizations, projects, members, tasks, and tracked-time activities.
Updated 2 months ago (2026-07-06 08:08 UTC)
10
MIT

Time Doctor MCP

What It Does

Installation Methods

Option A: Using uvx (Easiest - No Installation Required)

Option B: Clone & Install (For Development)

2. Configure Credentials

3. Add to Claude Desktop/Code

4. Restart Claude

Alternative MCP Clients

Cursor IDE

Google Gemini CLI

VS Code / GitHub Copilot

Usage

MCP Tools

1. export_weekly_csv

2. get_daily_report

3. get_hours_summary

4. export_today_csv

How It Works

Architecture

Project Structure

Troubleshooting

MCP Server Won't Start

Playwright Browser Error

Login Fails

No Data Returned

Claude Not Seeing Tools

Path Issues

Requirements

Performance

Security

Development

Why Web Scraping?

Alternative Installation Methods

Manual pip Installation

Using Python venv (without UV)

Contributing

License

Disclaimer

Support

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

1. `export_weekly_csv`

2. `get_daily_report`

3. `get_hours_summary`

4. `export_today_csv`