Skip to content

Time Tracking

Toggl MCP connector

The Toggl connector links your Toggl workspace to Claude, ChatGPT, Cursor and any MCP client, so your team can review Toggl audit logs, calendars, calendar events and logins by asking in plain language.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Toggl to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Toggl once

  1. Open Connections, choose Add connection, and pick Toggl.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Toggl API key. One person generates a token in Toggl and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

toggl
Toggl
1Password
360learning
7shifts
Acquire
Active Ants
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Toggl MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Toggl MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Toggl MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Toggl to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Toggl through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • IT

    Review who changed what in Toggl

    Pull the Toggl audit log for the last week and ask for a plain summary of the changes, who made them, and when.

  • Security

    Check SAML and desktop logins

    List the SAML logins and desktop logins on your Toggl workspace and spot anything that does not match your staff list.

  • Operations

    Keep connected calendars in order

    See which calendars are connected to Toggl, rename or remove the stale ones, and pick the ones the team should actually track against.

  • Project management

    Turn calendar events into tracked work

    Pull this week's calendar events from Toggl and ask for suggested details for each one before the team logs its time.

  • Finance

    Confirm currencies and countries before billing

    Check the currencies and country subdivisions Toggl supports so client rates and tax regions are set up correctly the first time.

  • People

    Look up a workspace member quickly

    Find a person's Toggl workspace details, update their avatar, or send feedback to Toggl on the team's behalf without opening the admin screens.

Try asking

  • “Summarize this week's Toggl audit log by person”
  • “Which calendars are connected to our Toggl workspace?”
  • “List Toggl SAML logins from the last 30 days”

See all 315 Toggl tools below

AI tools

Toggl tools for your AI agents

315 tools are ready to call through Elaichi's MCP endpoint the moment you connect Toggl, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 239 of 315 Toggl tools here. Connect Toggl and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting Toggl gets you

6 screens from the product, each doing one job for your Toggl account.

The agent

Ask Toggl a question, get a live answer.

Audit logs, calendar events and logins answered from Toggl in plain language.

  • audit logs
  • calendars
  • events
  • logins

Ask Elaichi to work across your apps.

Summarize this week's Toggl audit log by person

Which calendars are connected to our Toggl workspace?

List Toggl SAML logins from the last 30 days

Also runs in Claude, ChatGPT or Cursor

MCP clients

Toggl in Claude, ChatGPT and Cursor, connected once.

One governed endpoint for every MCP client, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

315 Toggl tools, no code to write.

Audit logs, calendars, events, logins and workspace users, ready the moment Toggl is connected.

  • List all Toggl audit logs
  • List all Toggl saml 2 logins
  • Create a Toggl saml 2 login
  • Create a Toggl avatar
ElaichiTools
Tool Action Description
List all Toggl audit logs List List Toggl Track audit log events for an organization over a given time range. Returns a list of audit log event objects; the upstream docs do not enumerate the individual event fields. Required: organization_id, from, to (RFC3339 datetimes).
List all Toggl saml 2 logins List Get the SAML2 Identity Provider (SSO) URL in Toggl Track for a given user email, used for authenticating in an Identity Provider. Returns the SAML2 login response object with provider-specific fields. Required: email. Fails if the email is invalid or SSO is not configured for it.
Create a Toggl saml 2 login Create Submit the SAML2 Identity Provider callback assertion to complete authentication for a Toggl Track workspace. Requires login_id (the numeric workspace ID) and SAMLResponse. Returns a 302 redirect to the authentication result URI with no response body.
Create a Toggl avatar Create Upload a new avatar image for the current Toggl user. Returns the created avatar object (the upstream API does not document its fields). Required: file. The image must have a valid image content type and be resizable — convert it to png or jpeg if the upload is rejected.
Toggl avatars bulk delete Delete Delete the current user's avatar in Toggl. Returns a plain string success message on success.

Toolboxes

Every team gets its own Toggl toolbox.

IT sees audit logs, project managers see calendars, each scoped to the team.

  • IT
  • Security
  • Operations
  • Project management
ElaichiToolboxes
Name Source template Tools Created

IT toolbox

Toggl · audit logs and logins

Toggl starter 18 Mar 4, 2026

Security toolbox

Toggl · SAML and desktop logins

— 9 Mar 2, 2026

Operations toolbox

Toggl · connected calendars

— 24 Feb 27, 2026

Project management toolbox

Toggl · calendar events and suggestions

Toggl starter 6 Feb 19, 2026

Finance toolbox

Toggl · currencies and countries

— 31 Jan 30, 2026

People toolbox

Toggl · workspace users and avatars

— 12 Jan 22, 2026

Shared connections

Teammates use Toggl without seeing the API key.

One person connects Toggl, shares it with teams, and the credential stays private.

  • IT
  • Security
  • Operations
  • Delivery
ElaichiConnections
Connection Scope Status Access
TO

Toggl (IT)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
TO

Toggl (Security)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
TO

Toggl (Operations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
TO

Toggl (Delivery)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
TO

Toggl (Finance)

Connected by Clara Nowak

Personal • Active Not shared
TO

Toggl (People)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Know who touched Toggl and when.

Every call logged with the person, the action, the type and the Toggl resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Toggl Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Toggl Audit logs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Toggl Audit logs List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Toggl events into a digest.

Calendar events fetched, grouped, drafted by an agent, approved by a person, posted to Toggl.

Toggl digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch audit logs

    Toggl

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Toggl

    Queued

Collections and dashboards

Toggl health, computed, refreshed on a schedule.

Events created over 14 days and a breakdown by team, no model in the numbers.

Toggl health

Refreshed 4 minutes ago · every 15 minutes · from the audit logs collection

Live

Audit logs

1,284 ↓ 12%

Calendars

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Audit logs created

Last 14 days

By team

Share of activity

IT 34%

Security 27%

Operations 21%

Delivery 18%

FAQ

Frequently asked questions

How do I connect Toggl to Claude?

Connect Toggl in Elaichi first: open the Toggl connector, paste the API key from your Toggl profile settings, and save. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Toggl is available in your next conversation.

Does Toggl work with ChatGPT and Cursor as well as Claude?

Yes. Once Toggl is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Toggl once and every client you use picks it up.

What can an AI agent actually do with my Toggl data?

With Toggl connected, an agent can read your Toggl audit logs, list SAML and desktop logins, show the calendars connected to your workspace and the events on them, suggest details for an event, look up a workspace member, and check the countries and currencies Toggl supports. You ask in plain language, the agent finds the right Toggl action and runs it. Short, concrete asks work better than long sentences.

Does connecting Toggl give the AI access to my whole workspace?

No. Every call to Toggl through Elaichi runs as the person who signed in, so the agent sees only what that person can already see in Toggl. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond the person's own Toggl access.

Can my team share one Toggl connection?

Yes. One person connects Toggl in Elaichi and shares the connection with a team, and nobody else ever handles the Toggl API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Toggl call.

Can I stop an agent from deleting or changing things in Toggl?

Yes. In Elaichi you restrict Toggl actions one by one, for example removing calendars or deleting avatars. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it, however it is worded.

What happens to a Toggl connection when someone leaves?

When you offboard someone in Elaichi, their access to Toggl through every client ends at once. A shared Toggl connection keeps working for everyone else on the team. If you disconnect Toggl in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

Does the Toggl MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Toggl is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put Toggl in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.