Toggl MCP Server

Created By
taiseimiyajia year ago
Overview

what is Toggl MCP Server?

Toggl MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to interact with the Toggl time tracking API, enabling management of time entries, projects, and workspaces through natural language.

how to use Toggl MCP Server?

To use Toggl MCP Server, configure the MCP connection in your .cursor/mcp.json file with your Toggl API token, and your AI assistant can then interact with Toggl using natural language commands.

key features of Toggl MCP Server?

  • Get time entries with filtering options
  • Create, update, and delete time entries
  • Retrieve current running time entry
  • Stop running time entries
  • Access workspace information and projects
  • Multi-platform support (linux/amd64, linux/arm64)

use cases of Toggl MCP Server?

  1. Automating time tracking for projects
  2. Managing time entries through voice commands
  3. Integrating time tracking into AI-driven productivity tools

FAQ from Toggl MCP Server?

  • What is required to use Toggl MCP Server?

You need a valid Toggl API token for authentication.

  • Is there support for multiple platforms?

Yes, it supports both linux/amd64 and linux/arm64 platforms.

  • What license is Toggl MCP Server under?

It is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
taiseimiyaji
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago