# How to integrate Toggl MCP with CrewAI

```json
{
  "title": "How to integrate Toggl MCP with CrewAI",
  "toolkit": "Toggl",
  "toolkit_slug": "toggl",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/toggl/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/toggl/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:28:49.376Z"
}
```

## Introduction

This guide walks you through connecting Toggl to CrewAI 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 CrewAI 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

- [OpenAI Agents SDK](https://composio.dev/toolkits/toggl/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/toggl/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/toggl/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/toggl/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/toggl/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/toggl/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/toggl/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/toggl/framework/cli)
- [Google ADK](https://composio.dev/toolkits/toggl/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/toggl/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/toggl/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/toggl/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/toggl/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Toggl connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Toggl
- Build a conversational loop where your agent can execute Toggl operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

## 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

| Tool slug | Name | Description |
|---|---|---|
| `TOGGL_CREATE_CLIENT` | Create Client | Tool to create a new client in a workspace. Use when you need to add a client to a workspace after workspace setup. |
| `TOGGL_CREATE_GROUP` | Create Group | Tool to create a new group in a Toggl organization. Use when organizing users into teams and controlling access to workspaces. Groups help manage user permissions and workspace assignments at the organization level. |
| `TOGGL_CREATE_INVITATION` | Create Invitation | Tool to send invitations to join a Toggl organization. Use when you need to invite users by email to an organization and its workspaces. At least one email and one workspace (or project_invite) are required. |
| `TOGGL_CREATE_ORGANIZATION` | Create Organization | Tool to create a new organization with a default workspace in Toggl Track. Use when initializing a new organization and workspace in one step. The authenticated user becomes the organization owner. |
| `TOGGL_CREATE_PROJECT` | Create Project | Creates a new project in a Toggl workspace. Projects are used to organize time entries and track work for specific initiatives. Required parameters: workspace_id (integer) and name (string). Optional parameters include client assignment, privacy settings, billable status, and time estimates. Note: Some features (custom colors, templates, fixed fees, hourly rates) require a premium Toggl plan. |
| `TOGGL_CREATE_TAG` | Create Tag | Tool to create a new tag in a workspace. Use when you need to add a tag after confirming workspace ID and desired tag name. |
| `TOGGL_CREATE_TIME_ENTRY` | Create Time Entry | Tool to create a new time entry in the specified workspace. Use when you have workspace ID, start time, and client name ready. |
| `TOGGL_CREATE_WORKSPACES_PROJECT_USERS` | Add User to Workspace Project | Tool to add a user to workspace project users. Use when you need to assign a user to a project within a workspace with optional manager privileges and custom rates. |
| `TOGGL_DELETE_CLIENT` | Delete Toggl Client | Tool to delete a client in Toggl. Use when you have confirmed the workspace and client IDs and want to remove a client permanently. |
| `TOGGL_DELETE_GROUP` | Delete Group | Tool to delete a group from a Toggl organization. Use when you need to permanently remove a group and its associated permissions. Requires organization and group IDs. |
| `TOGGL_DELETE_PROJECT_GROUP` | Delete Project Group | Tool to delete a project group from a Toggl workspace. Use when you need to remove a project group permanently. Requires workspace and project group IDs. |
| `TOGGL_DELETE_SUBSCRIPTION` | Delete Subscription | Tool to delete a webhook subscription in Toggl. Use when you want to remove an existing subscription for a specific workspace. |
| `TOGGL_DELETE_TAG` | Delete Tag | Deletes a tag from a Toggl workspace. Requires workspace and tag IDs. Only workspace or organization administrators can delete tags. Returns success status upon deletion. |
| `TOGGL_DISABLE_WEEKLY_REPORT` | Disable Weekly Report | Tool to disable weekly report email notifications. Use when you want to unsubscribe from weekly reports using the code provided in report emails. |
| `TOGGL_EDIT_TIME_ENTRIES` | Bulk Edit Time Entries | Tool to bulk edit multiple time entries in a workspace using JSON Patch operations. Use when you need to update the same field(s) across multiple time entries at once (e.g., changing descriptions, billable status, or project associations). Maximum 100 time entries per request. |
| `TOGGL_GET_ALL_PLANS` | Get All Plans | Tool to retrieve all available Toggl subscription plans and their features. Use when you need to display plan options, compare plans, or check available features for different subscription tiers. |
| `TOGGL_GET_CLIENT_DETAILS` | Get Client Details | Retrieves detailed information about a specific client in Toggl Track by its client ID and workspace ID. Use this tool when you need to: - Get complete client details including name, notes, and metadata - Verify if a client exists in a workspace - Check client archive status, timestamps, or external references - Retrieve integration information for JIRA/Salesforce linked clients |
| `TOGGL_GET_COUNTRIES` | Get Countries | Tool to retrieve all countries supported by Toggl. Returns country details including tax information, default currencies, and postal code requirements. Use when you need to validate country data or retrieve country-specific settings for billing. |
| `TOGGL_GET_COUNTRY_SUBDIVISIONS` | Get Country Subdivisions | Tool to retrieve all subdivisions (states, provinces, regions) for a specific country in Toggl Track. Use when you need to get geographical subdivision data for a country, such as US states or Canadian provinces. |
| `TOGGL_GET_CURRENCIES` | Get Currencies | Tool to retrieve the list of all currencies supported by Toggl Track. Use when you need currency codes and symbols for financial operations or display. |
| `TOGGL_GET_CURRENT_TIME_ENTRY` | Get Current Time Entry | Retrieves the currently running time entry for the authenticated user. Returns null if no timer is active. Use this to check timer status or get details about the active time entry. |
| `TOGGL_GET_EVENT_FILTERS` | Get Event Filters | Retrieve the list of supported event filters for Toggl webhooks. Use this when you need to know which event types are available for webhook subscriptions (e.g., client created, project updated, time entry deleted). |
| `TOGGL_GET_KEYS` | Get JWKS Keys | Retrieves the current JWKS (JSON Web Key Set) keyset used to sign JWT tokens. Use this to obtain public keys for verifying JWT token signatures issued by Toggl. |
| `TOGGL_GET_LIST_CLIENTS` | List Clients | Retrieve a list of clients from a Toggl Track workspace with optional filtering by status and name. Use this tool to: - List all clients in a workspace - Filter clients by active/archived status - Search for clients by name (case-insensitive) - Get client details including IDs, names, timestamps, and permissions By default, only active clients are returned unless specified otherwise. |
| `TOGGL_GET_MY_LOCATION` | Get My Location | Retrieves the authenticated user's last known location information including city, state, country, and coordinates. Use this to determine user's geographic location for timezone or region-specific features. |
| `TOGGL_GET_MY_QUOTA` | Get My Quota | Tool to retrieve API rate limit quota for the authenticated user. Use when you need to check remaining API calls before making further requests or to monitor rate limit status. |
| `TOGGL_GET_ORGANIZATION_DETAILS` | Get Organization Details | Retrieves detailed information about a specific Toggl organization including subscription plan, trial status, user count, and workspace settings. Requires a valid organization ID that the authenticated user has access to. |
| `TOGGL_GET_ORGANIZATION_GROUPS` | Get Organization Groups | Retrieves all groups within a Toggl organization, including group members and workspace assignments. Groups are used to organize users and control access to workspaces. Returns an empty list if no groups exist in the organization. |
| `TOGGL_GET_ORGANIZATION_USERS` | Get Organization Users | Retrieves a list of users belonging to a Toggl organization. Returns detailed information about each user including their email, name, role, workspace memberships, and group memberships. Supports filtering by name/email, status (active/inactive/invited), admin privileges, and pagination. Use this when you need to list organization members or find specific users within an organization. |
| `TOGGL_GET_PROJECT_DETAILS` | Get Project Details | Tool to retrieve details of a specific project. Use after confirming the workspace ID and project ID. |
| `TOGGL_GET_PROJECTS` | Get Projects | Tool to retrieve a list of projects from a Toggl workspace. Use after confirming workspace ID. Returns filtered and paginated projects with optional client details. |
| `TOGGL_GET_PUBLIC_SUBSCRIPTION_PLANS` | Get Public Subscription Plans | Tool to retrieve all publicly available subscription plans from Toggl. Use when you need to display available pricing tiers or plan options to users. |
| `TOGGL_GET_STATUS` | Get Webhooks Status | Tool to retrieve the Toggl Webhooks server status. Use when you need to check if the webhooks service is operational before registering or managing webhook subscriptions. |
| `TOGGL_GET_TAGS` | Get Tags | Retrieve all tags in a Toggl workspace. Returns a list of tags with their IDs, names, and metadata. Use this when you need to list available tags for categorizing time entries or when searching for a specific tag by name. Returns an empty list if the workspace has no tags. |
| `TOGGL_GET_TASKS` | List Tasks | Tool to list tasks in a workspace or within a specific project. |
| `TOGGL_GET_TIME_ENTRIES` | Get Time Entries | Retrieve time entries for the authenticated user with flexible filtering options. Use this tool to: - List all recent time entries (no parameters needed) - Filter entries by date range (start_date + end_date) - Get entries modified since a specific time (since parameter for syncing) - Include project/tag metadata and sharing information Returns comprehensive details including project names, tags, duration, and billable status. |
| `TOGGL_GET_TIME_ENTRY` | Get Time Entry | Tool to retrieve a specific time entry by its ID. Use when you have the entry ID and need its full details. |
| `TOGGL_GET_TIMEZONE_OFFSETS` | Get Timezone Offsets | Tool to retrieve all available timezone offsets from Toggl. Use when you need to display timezone information or validate timezone selection for time entry operations. |
| `TOGGL_GET_TIMEZONES` | Get Timezones | Tool to retrieve all available timezones supported by Toggl Track. Use when you need to validate timezone values or display available timezone options to users. |
| `TOGGL_GET_USER_CLIENTS` | Get User Clients | Retrieves all clients accessible to the authenticated user across all their workspaces. Returns a complete list of client details including workspace associations, archive status, notes, and integration information. Use this to view all clients the current user has access to without needing to specify individual workspace IDs. |
| `TOGGL_GET_USER_PREFERENCES` | Get User Preferences | Retrieves the authenticated user's preferences including timezone, date/time formats, notification settings, and enabled alpha/experimental features. Useful for understanding user display preferences or checking which optional features are available. |
| `TOGGL_GET_USER_PROJECTS` | Get User Projects | Tool to retrieve all projects for the authenticated user. Use after authenticating to list available projects. |
| `TOGGL_GET_USER_TAGS` | Get User Tags | Tool to retrieve tags associated with the current user. Use when you need to list all tags visible to your account across all workspaces, or to get tags that have been created/modified/deleted since a specific date for incremental syncing. |
| `TOGGL_GET_USER_TASKS` | Get User Tasks | Retrieve all tasks across all workspaces accessible to the authenticated user. Returns tasks from projects the user can access, including task details like name, active status, estimated time, and tracked time. Use this to get a comprehensive list of tasks without needing to specify workspace or project IDs. |
| `TOGGL_GET_USER_WORKSPACES` | Get User Workspaces | Tool to retrieve all workspaces the authenticated user belongs to. Use when you need to list accessible workspaces before performing workspace-specific operations. Verify the correct workspace ID from the returned list before use — an incorrect workspace ID will misroute entries and skew reports. |
| `TOGGL_GET_WORKSPACE_DETAILS` | Get Workspace Details | Retrieves comprehensive details and settings for a specific Toggl workspace by ID. Returns workspace configuration including premium/business status, admin permissions, default settings for projects/billing, time tracking preferences, and organizational details. Use this when you need to inspect workspace properties or validate access before performing workspace-specific operations. |
| `TOGGL_GET_WORKSPACE_LOGO` | Get Workspace Logo | Tool to get workspace logo. Use when you need to retrieve the logo associated with a specific workspace. |
| `TOGGL_GET_WORKSPACE_PREFERENCES` | Get Workspace Preferences | Retrieves workspace preferences including the initial pricing plan and whether start/end times are hidden. Use this after obtaining a workspace ID to check workspace-level preference settings. |
| `TOGGL_GET_WORKSPACE_USERS` | Get Workspace Users | Retrieves all users who belong to a specific Toggl workspace. Returns user details including their name, email, admin status, and activity status. Use this to list workspace members, check user roles, or verify user access to a workspace. |
| `TOGGL_PATCH_STOP_TIME_ENTRY` | Stop Time Entry | Tool to stop a running time entry in a workspace. Use when a time entry needs to be ended. |
| `TOGGL_POST_ME_DISABLE_PRODUCT_EMAILS` | Disable Product Emails | Tool to disable product emails for the authenticated user using a disable code. Use when the user wants to unsubscribe from Toggl product emails using a code from an unsubscribe link. |
| `TOGGL_PUT_UPDATE_TAG` | Update Tag | Tool to update an existing tag in a specified workspace. Use after confirming the workspace_id and tag_id when renaming a tag. Example: rename tag 'urgent' to 'high_priority'. |
| `TOGGL_SEND_DEMO_EMAIL` | Send Demo Email | Tool to send a demo request email through Toggl's system. Use when someone wants to request a product demo. |
| `TOGGL_SEND_EMAIL_CONTACT` | Send Email to Contact | Tool to send an email to a contact via Toggl's smail service. Use when you need to send a message to a specific contact by providing their email, name, and message content. |
| `TOGGL_SEND_SMAIL_MEET` | Send Smail Meet | Tool to send an email for meet. Use when you need to send a meet invitation email to a specific recipient with a location. |
| `TOGGL_UPDATE_CLIENT` | Update Client | Updates an existing client in a Toggl workspace. Use this to modify a client's name or notes. Note: The Toggl API requires the 'name' field when updating any client property. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Toggl MCP server is an implementation of the Model Context Protocol that connects your AI agent to Toggl. It provides structured and secure access so your agent can perform Toggl operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A Toggl connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Toggl via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Toggl MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Toggl

**What's happening:**
- You create a Toggl only session through Composio
- Composio returns an MCP HTTP URL that exposes Toggl tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["toggl"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["toggl"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Toggl through Composio's Tool Router. The agent can perform Toggl operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Toggl MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/toggl/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/toggl/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/toggl/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/toggl/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/toggl/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/toggl/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/toggl/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/toggl/framework/cli)
- [Google ADK](https://composio.dev/toolkits/toggl/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/toggl/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/toggl/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/toggl/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/toggl/framework/llama-index)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.

## Frequently Asked Questions

### 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 CrewAI?

Yes, you can. CrewAI 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
