toggl-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@toggl-mcp Log 1 hour for design review from 2pm to 3pm ET with tag #design"
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.
Toggl MCP
An MCP (Model Context Protocol) server that lets AI assistants log time entries to Toggl Track.
What it does
Exposes three tools to MCP clients (e.g. Claude):
get_tags— lists existing Toggl tags (cached daily)get_entry_descriptions— lists existing time entry descriptions (cached daily)create_time_entry— logs a new time entry with a start time, end time, description, and tag
Also exposes toggl://tags, toggl://entries, and toggl://now as MCP resources.
Time input is in Eastern Time (America/New_York) and converted to UTC before submission.
Related MCP server: Lazy Toggl MCP Server
Setup
Copy
.env.exampleto.envand fill in your values:
BASEURL=https://api.track.toggl.com/api/v9/
CACHE_FOLDER=cache
TOGGL_APIKEY=<your api key>
WORKSPACE_ID=<your workspace id>To find your workspace ID, call the /me endpoint with your API key.
Install dependencies (requires Python 3.10+):
uv syncRun the server:
uv run main.pyMCP Client Config
To use with Claude Desktop, add to your MCP config:
{
"mcpServers": {
"toggl": {
"command": "uv",
"args": ["run", "/path/to/toggl/main.py"]
}
}
}Running Tests
uv run pytestTests live in the tests/ directory. The dev dependency group includes pytest.
Where to get Toggl API Key
Log in to Toggl Track
Go to Profile Settings (click your avatar in the bottom-left)
Scroll to the bottom — your API token is listed under API Token
Click Click to reveal and copy the token
Available Tools
4 toolscreate_time_entryA
Logs a new time entry into Toggl.
LLM Notes:
- Always use the get_tags tool first to find a matching existing tag before calling this tool.
- Always check with get_entry_descriptions tool to see if there's a very similar description that exists and use that as the description.
@param start_time the start datetime in ET (New York) e.g., "2026-03-07T07:30:00"
@param end_time the end datetime in ET (New York) e.g., "2026-03-07T07:30:00"
@param description the activity performed e.g., "Walked dog"
@param tag the tag associated with the entry e.g., "chore"
@returns a time entry object. Make sure to review it for what was actually added.
Inputs: tag (required), end_time (required), start_time (required), description (required). Returns: result
get_entry_descriptionsA
Get a list of existing time entry descriptions being used in Toggl. Cached daily.
Inputs: no named parameters.
get_tagsA
Get a list of existing tags being used in Toggl. Cached daily.
Inputs: no named parameters. Returns: result
nowA
Get a list of existing tags being used in Toggl. Cached daily.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The tool 'now' has a description identical to 'get_tags', making them indistinguishable. An agent cannot tell which tool to use without further context, and the purpose of 'now' is unclear.
Most tools follow a verb_noun pattern (get_tags, get_entry_descriptions, create_time_entry), but 'now' breaks the pattern with a vague, single-word name. The mixed conventions make the set feel unpolished.
With only 4 tools, and one being a duplicate, the server feels thin for a Toggl integration. However, the focus on time entry creation and reference data is somewhat coherent, so the count is not egregiously low.
The server supports creating time entries and reading tags/descriptions, but there are no operations to list, update, or delete time entries, nor to manage tags. Significant CRUD operations are missing, which will frustrate agents needing full lifecycle management.
Maintenance
Related MCP Connectors
Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.
Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.
Manage Timequip projects, tasks, comments, members, and dashboards through MCP.
Log and read REPS time logs, properties, and categories via MCP. Requires REPSLog Premium.
Related MCP Servers
AlicenseBqualityBmaintenanceEnables natural language control of the Timesheet API for timer management, task tracking, and project management through MCP tools.50351 npm1MIT- FlicenseAqualityDmaintenanceProvides tools to start/stop time tracking, list workspaces, and view current entry in Toggl.44-
- AlicenseNot gradedqualityCmaintenanceEnables natural language time tracking and booking for WorkTracker via MCP tools, allowing users to assign time, list projects, and manage daily schedules through conversational commands.MIT
- AlicenseAqualityDmaintenanceEnables employee time tracking with clock-in/out, workday checking, and time log retrieval via MCP tools.41MIT