Skip to main content
Glama
toggl-mcp

toggl-mcp

by saaqibz

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

  1. Copy .env.example to .env and 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.

  1. Install dependencies (requires Python 3.10+):

uv sync
  1. Run the server:

uv run main.py

MCP 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 pytest

Tests live in the tests/ directory. The dev dependency group includes pytest.

Where to get Toggl API Key

  1. Log in to Toggl Track

  2. Go to Profile Settings (click your avatar in the bottom-left)

  3. Scroll to the bottom — your API token is listed under API Token

  4. Click Click to reveal and copy the token

Available Tools

4 tools
create_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

    B3.3/5.0

    Scored across 4 tools

    Disambiguation1/5

    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.

    Naming Consistency2/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers