Toggl MCP Server

MCP开发工具

提供方 abhinav24jha

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

MCP Server for Toggl

一句话选型结论

按资料字段整理

Toggl MCP Server 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 13 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

developer-toolstogglmcp-servertime-tracking时间追踪Python本地部署项目管理

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
pip install --all

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Toggl MCP Server当前 未标注 stdio · 本地进程 本地部署 有 2026-05-18
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方abhinav24jha上游标注的维护方 abhinav24jha
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

9.9 KB
来自项目仓库与上游目录的原文,未做删改

Toggl MCP Server

Allows MCP clients to interact with Toggl Track, enabling time tracking, project management, and workspace operations through natural language.

Features

Tools

Project Management

  • create_project
  • Description: Creates a new project in a specified Toggl workspace.
  • Input:
    • name (str): The name of the project to be created. This is a required field.
    • workspace_name (str, optional): The name of the workspace where the project will be created. If not provided, it defaults to the user's default workspace.
    • active (bool, optional): Specifies whether the project is active. Defaults to True.
    • billable (bool, optional): Specifies whether the project is billable. Defaults to False.
    • client_id (int, optional): The ID of the client associated with the project.
    • color (str, optional): The hex color code assigned to the project (e.g., "#FF0000").
    • is_private (bool, optional): Specifies whether the project is private. Defaults to True.
    • start_date (str, optional): The start date of the project in ISO 8601 format (e.g., "YYYY-MM-DD").
    • end_date (str, optional): The end date of the project in ISO 8601 format (e.g., "YYYY-MM-DD").
    • estimated_hours (int, optional): The estimated number of hours for the project.
    • template (bool, optional): Specifies whether the project is a template. Defaults to False.
    • template_id (int, optional): The ID of the template to use for creating the project.
  • Output: JSON response containing the data of the newly created project.

  • delete_project

  • Description: Deletes a project identified by its name within a specified workspace.
  • Input:
    • project_name (str): The exact name of the project to be deleted. This is a required field.
    • workspace_name (str, optional): The name of the workspace containing the project. If not provided, it defaults to the user's default workspace.
  • Output: A confirmation message (str) indicating the successful deletion of the project.

  • update_projects

  • Description: Performs bulk updates on multiple projects within a specified workspace using patch operations.
  • Input:
    • project_names (List[str]): A list containing the names of the projects to be updated. This is a required field.
    • operations (List[dict]): A list of patch operations to apply to the selected projects. Each operation is a dictionary specifying the operation type (op), the field path (path), and the new value (value) (e.g., {"op": "replace", "path": "/active", "value": false}). This is a required field.
    • workspace_name (str, optional): The name of the workspace containing the projects. If not provided, it defaults to the user's default workspace.
  • Output: JSON response containing the data of the updated projects.

  • get_all_projects

  • Description: Retrieves a list of all projects within a specified workspace.
  • Input:
    • workspace_name (str, optional): The name of the workspace from which to retrieve projects. If not provided, it defaults to the user's default workspace.
  • Output: JSON response containing a list of project data objects found in the specified workspace.

Time Entry Management

  • new_time_entry
  • Description: Creates a new time entry. Can be used to start a timer (if only start is provided or neither start nor duration are provided) or log a completed time entry (if start and stop, or start and duration are provided).
  • Input:
    • description (str): The description for the time entry.
    • workspace_name (str, optional): Name of the workspace. Defaults to the user's default workspace.
    • project_name (str, optional): Name of the project to associate the time entry with.
    • tags (List[str], optional): A list of tag names to apply to the time entry.
    • start (str, optional): The start time of the entry in ISO 8601 format (e.g., "2023-10-26T10:00:00Z"). Defaults to the current time if creating a running entry.
    • stop (str, optional): The stop time of the entry in ISO 8601 format. If provided, creates a completed entry.
    • duration (int, optional): The duration of the entry in seconds. If start is provided but stop is not, duration determines the stop time. If start is not provided, a negative duration starts a running timer.
    • billable (bool, optional): Whether the time entry should be marked as billable. Defaults to False.
    • created_with (str, optional): The name of the application creating the entry. Defaults to "MCP".
  • Output: JSON response containing the data of the created time entry.

  • stop_time_entry

  • Description: Stops the currently running time entry.
  • Input:
    • workspace_name (str, optional): Name of the workspace where the entry is running. Defaults to the user's default workspace.
  • Output: JSON response containing the data of the stopped time entry.

  • delete_time_entry

  • Description: Deletes a specific time entry by its description and start time.
  • Input:
    • time_entry_description (str): The exact description of the time entry to delete.
    • start_time (str): The exact start time of the entry in ISO 8601 format used for identification.
    • workspace_name (str, optional): Name of the workspace containing the entry. Defaults to the user's default workspace.
  • Output: Success confirmation message (str) upon successful deletion.

  • get_current_time_entry

  • Description: Fetches the details of the currently running time entry.
  • Input: None (implicitly uses the user's context).
  • Output: JSON response containing the data of the currently running time entry, or None if no time entry is currently running.

  • update_time_entry

  • Description: Updates attributes of an existing time entry identified by its description and start time.
  • Input:
    • time_entry_description (str): The current description of the time entry to update.
    • start_time (str): The exact start time of the entry in ISO 8601 format used for identification.
    • workspace_name (str, optional): Name of the workspace containing the entry. Defaults to the user's default workspace.
    • new_description (str, optional): New description for the time entry.
    • project_name (str, optional): New project name to associate with the entry. Set to empty string "" to remove project association.
    • tags (List[str], optional): A new list of tag names. This will replace all existing tags. Provide an empty list [] to remove all tags.
    • new_start (str, optional): New start time in ISO 8601 format.
    • new_stop (str, optional): New stop time in ISO 8601 format.
    • billable (bool, optional): New billable status.
  • Output: JSON response containing the data of the updated time entry.

  • get_time_entries_for_range

  • Description: Retrieves time entries within a specified date range, defined by offsets from the current day.
  • Input:
    • from_day_offset (int): The start day offset from today (e.g., 0 for today, -1 for yesterday, -7 for a week ago).
    • to_day_offset (int): The end day offset from today (e.g., 0 for today, 1 for tomorrow). The range includes both the start and end dates.
    • workspace_name (str, optional): Name of the workspace to fetch entries from. Defaults to the user's default workspace.
  • Output: JSON response containing a list of time entries found within the specified date range.

Getting Started

Prerequisites

  • Python 3.11+
  • Toggl Track account
  • uv installed for dependency management

Environment Variables

Create a .env file inside of the mcp_toggl_server folder with:```bash
EMAIL=your_toggl_email
PASSWORD=your_toggl_password


If you are using Toggl API tokens:```bash
EMAIL=xxxx
PASSWORD="api_token"

Where xxxx indicates your personal token

Installation

First install uv:
- For MacOS/Linux:bash curl -LsSf https://astral.sh/uv/install.sh | sh
- For Windows:bash powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Make sure to restart your terminal afterwards to ensure that the uv command gets picked up.

Now let's clone the repository and set up the project:```bash
git clone [repository-url]
cd mcp_toggl_server
uv venv
uv pip install --all


### Integration with Development Tools

#### VS Code + GitHub Copilot Setup

1. Configure the MCP Server in `.vscode/mcp.json`:```json
"servers": {
  "toggl": {
    "type": "stdio",
    "command": "uv",
    "args": [
      "--directory",
      "/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp_toggl_server",
      "run",
      "toggl_mcp_server.py"],
    "envFile": "${workspaceFolder}/mcp_toggl_server/.env"
  }
}
  1. Update the configuration:
    - Replace /ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp_toggl_server with the absolute path to the server
    - You may need to put the full path to the uv executable in the command field. You can get this by running which uv on MacOS/Linux or where uv on Windows

  2. Enable the server:
    - Look for the start button when hovering over the server configuration /.vscode/mcp.json
    - Click start to let Copilot discover available tools
    - Switch to agent mode in Copilot

For detailed setup instructions, see:
- MCP Servers in VS Code
- Copilot Agent Mode

Additional MCP Client Integration

The Toggl MCP Server works with any MCP-compatible client. For integration steps:

  1. For Claude Desktop, visit the MCP Quick Start Guide
  2. For other MCP clients, consult their respective documentation for server configuration

Note: Configuration typically involves specifying the server path and environment variables similar to the VS Code setup above.

Testing with MCP Inspector

To run in development:bash EMAIL=your_toggl_email PASSWORD=your_toggl_password mcp dev toggl_mcp_server.py

License

This MCP server is licensed under the MIT License.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Toggl MCP Server 怎么安装?

在客户端按下面的安装命令接入:pip install --all。装完在客户端配置里引用同一个包或端点。

Toggl MCP Server 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Toggl MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Toggl MCP Server 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Toggl MCP Server 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Toggl MCP Server 能提供哪些能力?

资料显示能力标签包括 工作区管理、Python、Claude、自然语言交互。具体工具清单以官方文档为准。

Toggl MCP Server 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Toggl MCP Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-18。