Toggl Track MCP Server

Created By
vontella year ago
An MCP server for Toggl Track. Built by Claude Code
Overview

What is Toggl Track MCP Server?

Toggl Track MCP Server is a Model Context Protocol (MCP) server designed for integrating Toggl Track time tracking functionalities, allowing users to manage projects and time entries seamlessly.

How to use Toggl Track MCP Server?

To use the server, you need to obtain your Toggl Track API token, build the Docker image from the repository, configure it in your Claude Desktop, and restart the application to start interacting with your Toggl Track account.

Key features of Toggl Track MCP Server?

  • Retrieve projects and workspaces from Toggl Track account.
  • Get detailed time entries with filtering options.
  • Generate aggregated time reports by project.
  • Control timers and manage tasks effectively.
  • Secure API token authentication for user safety.

Use cases of Toggl Track MCP Server?

  1. Managing and tracking time spent on various projects.
  2. Analyzing productivity through detailed time reports.
  3. Creating and managing tasks associated with projects.
  4. Interacting with the server for real-time timer control.

FAQ from Toggl Track MCP Server?

  • Can I use this server without a Toggl Track account?

No, you need a valid Toggl Track account and API token to use this server.

  • Is there a limit on the number of requests I can make?

Yes, Toggl Track API has rate limiting, approximately 1 request per second.

  • What programming language is this server written in?

The server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vontell
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago