How to integrate Toggl MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Toggl logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Toggl to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Toggl agent that can start a new time entry for coding, list all clients in your workspace, get details of your current running timer through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Toggl account through Composio's Toggl MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Toggl with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Toggl
  • Configure an AI agent that can use Toggl as a tool
  • Run a live chat session where you can ask the agent to perform Toggl operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Toggl MCP server, and what's possible with it?

The Toggl MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Toggl account. It provides structured and secure access to your time tracking data, so your agent can perform actions like logging time entries, managing clients and projects, handling tags, and retrieving detailed activity reports on your behalf.

  • Automated time entry management: Let your agent start, stop, and create new time entries with precise details, making it easy to track your work hours hands-free.
  • Client and project organization: Easily add new clients or projects, fetch client details, or remove outdated clients to keep your workspace up to date and well-structured.
  • Real-time activity tracking: Ask your agent to retrieve the currently running time entry or list recent activities, so you always know where your time is going.
  • Tag management and organization: Automatically create or delete tags to categorize your time entries, helping you analyze how your time is spent across different tasks.
  • Comprehensive workspace administration: Have your agent create organizations, set up workspaces, and ensure all your time tracking infrastructure is ready to go without manual setup.

Supported Tools & Triggers

Tools
Create ClientTool to create a new client in a workspace.
Create GroupTool to create a new group in a Toggl organization.
Create InvitationTool to send invitations to join a Toggl organization.
Create OrganizationTool to create a new organization with a default workspace in Toggl Track.
Create ProjectCreates a new project in a Toggl workspace.
Create TagTool to create a new tag in a workspace.
Create Time EntryTool to create a new time entry in the specified workspace.
Add User to Workspace ProjectTool to add a user to workspace project users.
Delete Toggl ClientTool to delete a client in Toggl.
Delete GroupTool to delete a group from a Toggl organization.
Delete Project GroupTool to delete a project group from a Toggl workspace.
Delete SubscriptionTool to delete a webhook subscription in Toggl.
Delete TagDeletes a tag from a Toggl workspace.
Disable Weekly ReportTool to disable weekly report email notifications.
Bulk Edit Time EntriesTool to bulk edit multiple time entries in a workspace using JSON Patch operations.
Get All PlansTool to retrieve all available Toggl subscription plans and their features.
Get Client DetailsRetrieves detailed information about a specific client in Toggl Track by its client ID and workspace ID.
Get CountriesTool to retrieve all countries supported by Toggl.
Get Country SubdivisionsTool to retrieve all subdivisions (states, provinces, regions) for a specific country in Toggl Track.
Get CurrenciesTool to retrieve the list of all currencies supported by Toggl Track.
Get Current Time EntryRetrieves the currently running time entry for the authenticated user.
Get Event FiltersRetrieve the list of supported event filters for Toggl webhooks.
Get JWKS KeysRetrieves the current JWKS (JSON Web Key Set) keyset used to sign JWT tokens.
List ClientsRetrieve a list of clients from a Toggl Track workspace with optional filtering by status and name.
Get My LocationRetrieves the authenticated user's last known location information including city, state, country, and coordinates.
Get My QuotaTool to retrieve API rate limit quota for the authenticated user.
Get Organization DetailsRetrieves detailed information about a specific Toggl organization including subscription plan, trial status, user count, and workspace settings.
Get Organization GroupsRetrieves all groups within a Toggl organization, including group members and workspace assignments.
Get Organization UsersRetrieves a list of users belonging to a Toggl organization.
Get Project DetailsTool to retrieve details of a specific project.
Get ProjectsTool to retrieve a list of projects from a Toggl workspace.
Get Public Subscription PlansTool to retrieve all publicly available subscription plans from Toggl.
Get Webhooks StatusTool to retrieve the Toggl Webhooks server status.
Get TagsRetrieve all tags in a Toggl workspace.
List TasksTool to list tasks in a workspace or within a specific project.
Get Time EntriesRetrieve time entries for the authenticated user with flexible filtering options.
Get Time EntryTool to retrieve a specific time entry by its ID.
Get Timezone OffsetsTool to retrieve all available timezone offsets from Toggl.
Get TimezonesTool to retrieve all available timezones supported by Toggl Track.
Get User ClientsRetrieves all clients accessible to the authenticated user across all their workspaces.
Get User PreferencesRetrieves the authenticated user's preferences including timezone, date/time formats, notification settings, and enabled alpha/experimental features.
Get User ProjectsTool to retrieve all projects for the authenticated user.
Get User TagsTool to retrieve tags associated with the current user.
Get User TasksRetrieve all tasks across all workspaces accessible to the authenticated user.
Get User WorkspacesTool to retrieve all workspaces the authenticated user belongs to.
Get Workspace DetailsRetrieves comprehensive details and settings for a specific Toggl workspace by ID.
Get Workspace LogoTool to get workspace logo.
Get Workspace PreferencesRetrieves workspace preferences including the initial pricing plan and whether start/end times are hidden.
Get Workspace UsersRetrieves all users who belong to a specific Toggl workspace.
Stop Time EntryTool to stop a running time entry in a workspace.
Disable Product EmailsTool to disable product emails for the authenticated user using a disable code.
Update TagTool to update an existing tag in a specified workspace.
Send Demo EmailTool to send a demo request email through Toggl's system.
Send Email to ContactTool to send an email to a contact via Toggl's smail service.
Send Smail MeetTool to send an email for meet.
Update ClientUpdates an existing client in a Toggl workspace.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Toggl account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Toggl functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Toggl
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["toggl"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Toggl
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Toggl tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Toggl
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Toggl and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Toggl
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["toggl"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Toggl tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Toggl through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Toggl MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Toggl MCP?

With a standalone Toggl MCP server, the agents and LLMs can only access a fixed set of Toggl tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Toggl and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Toggl tools.

Can I manage the permissions and scopes for Toggl while using Tool Router?

Yes, absolutely. You can configure which Toggl scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Toggl data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.