# How to integrate Desktime MCP with CrewAI ```json { "title": "How to integrate Desktime MCP with CrewAI", "toolkit": "Desktime", "toolkit_slug": "desktime", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/desktime/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/desktime/framework/crew-ai.md", "updated_at": "2026-05-12T10:08:32.821Z" } ``` ## Introduction This guide walks you through connecting Desktime to CrewAI using the Composio tool router. By the end, you'll have a working Desktime agent that can list all active projects with tasks, get today's time tracked for each employee, start timing work on 'client website redesign' through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Desktime account through Composio's Desktime MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Desktime with - [OpenAI Agents SDK](https://composio.dev/toolkits/desktime/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/desktime/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/desktime/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/desktime/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/desktime/framework/codex) - [OpenClaw](https://composio.dev/toolkits/desktime/framework/openclaw) - [Hermes](https://composio.dev/toolkits/desktime/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/desktime/framework/cli) - [Google ADK](https://composio.dev/toolkits/desktime/framework/google-adk) - [LangChain](https://composio.dev/toolkits/desktime/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/desktime/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/desktime/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/desktime/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Desktime connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Desktime - Build a conversational loop where your agent can execute Desktime 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 Desktime MCP server, and what's possible with it? The Desktime MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Desktime account. It provides structured and secure access to your time tracking, project management, and productivity data, so your agent can perform actions like tracking work hours, managing projects, analyzing employee productivity, and reporting on team activities on your behalf. - Automated project and task management: Create new projects, assign optional starter tasks, and retrieve a comprehensive list of active company projects for streamlined organization. - Employee and company insights: Instantly fetch detailed company account info, list all employees with their roles and statuses, and access individual employee data for better workforce visibility. - Time tracking control: Start or stop tracking work on specific projects and tasks, enabling hands-free, accurate logging of work sessions and project contributions. - Productivity and app usage analysis: Retrieve employee project assignments and application usage data to monitor work habits and identify productivity trends across your team. - API health and connectivity checks: Use built-in API ping tools to verify Desktime API availability and ensure uninterrupted agent operations. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DESKTIME_CREATE_PROJECT_WITH_TASK` | Create Project with Optional Task | Tool to create a new project with an optional initial task. Use when you need to set up a new DeskTime project programmatically. | | `DESKTIME_GET_ACCOUNT_DETAILS` | Get Account Details | Retrieves company account configuration including work schedule and timezone settings. This action fetches company-level information such as company name, work hours (start/end times), work duration, working days configuration, time tracking hours, and timezone. No parameters are required. This is useful for understanding the company's work schedule configuration and timezone settings. | | `DESKTIME_GET_ALL_COMPANY_EMPLOYEES` | Get All Company Employees | Tool to list all employees in the company, including their roles and statuses. Use after confirming valid credentials to fetch the organization’s roster. | | `DESKTIME_GET_EMPLOYEE` | Get Employee | Tool to retrieve information about a single employee including user info, work settings, and tracking data for a specific date. Use when you need detailed information for one employee. Returns data for the currently logged-in user if no employee ID is specified. | | `DESKTIME_GET_EMPLOYEE_APPS` | Get Employee Apps | Retrieves employee tracking data including tracked apps for a specific date. Returns data for the currently logged-in user if no employee ID is specified. Use this action to view detailed application usage and productivity data for an employee. | | `DESKTIME_GET_EMPLOYEE_PROJECTS` | Get Employee Projects | Retrieves comprehensive employee project tracking data including project assignments, time tracking metrics, work hours, and productivity statistics for a specific employee and date. Returns detailed information about: - Employee profile (ID, name, email, group) - Time tracking metrics (online time, productive time, efficiency) - Work schedule (work start/end times, timezone) - Active project details (current project and task being worked on) - Projects list (all projects tracked on the specified date with durations) - Employee status indicators (online, arrived, left, late) Use this action when you need to: - View an employee's project assignments and tracking data - Check time spent on specific projects by an employee - Monitor employee productivity and work hours - Retrieve historical project tracking data for a specific date Both parameters are optional - defaults to current API-key user and today's date. | | `DESKTIME_GET_EMPLOYEE_PROJECTS_AND_APPS` | Get Employee Basic Data | Retrieve an employee's basic information and daily tracking statistics from DeskTime. Returns employee profile data, work hours, productivity metrics, attendance status, and currently active project. Use this when you need employee time tracking data for a specific date (defaults to today). Note: For detailed project/app usage breakdowns, use the dedicated Get Employee Projects action. | | `DESKTIME_GET_PROJECTS_LIST` | Get Projects List | Tool to retrieve all active projects for the company, including related tasks. Use when you need projects overview after authentication. | | `DESKTIME_PING_REQUEST` | Ping DeskTime API | Tool to check the API's availability and confirm the service is operational. Use when you need to verify that the DeskTime API is reachable and responsive. | | `DESKTIME_START_PROJECT_TASK` | Start Project Task | Starts time tracking for a specified project and optional task in DeskTime. This action begins recording time against the specified project. If a task name is provided, time is also tracked at the task level within that project. Both projects and tasks are created automatically if they don't already exist in the DeskTime account. Use this action when a user wants to: - Begin working on a project and track time - Start a specific task within a project - Switch time tracking to a different project or task Note: Only one project/task can be tracked at a time per user. Starting a new project automatically stops tracking on any previously active project. | | `DESKTIME_STOP_PROJECT_TASK` | Stop Project Task | Tool to stop tracking time for a specified project and optional task. Use when you have finished work and need to record end time. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Desktime MCP server is an implementation of the Model Context Protocol that connects your AI agent to Desktime. It provides structured and secure access so your agent can perform Desktime 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 Desktime 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 Desktime 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 Desktime 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 Desktime **What's happening:** - You create a Desktime only session through Composio - Composio returns an MCP HTTP URL that exposes Desktime tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["desktime"]) 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=["desktime"], ) 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 Desktime through Composio's Tool Router. The agent can perform Desktime 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 Desktime MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/desktime/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/desktime/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/desktime/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/desktime/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/desktime/framework/codex) - [OpenClaw](https://composio.dev/toolkits/desktime/framework/openclaw) - [Hermes](https://composio.dev/toolkits/desktime/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/desktime/framework/cli) - [Google ADK](https://composio.dev/toolkits/desktime/framework/google-adk) - [LangChain](https://composio.dev/toolkits/desktime/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/desktime/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/desktime/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/desktime/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 Desktime MCP? With a standalone Desktime MCP server, the agents and LLMs can only access a fixed set of Desktime tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Desktime 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 Desktime tools. ### Can I manage the permissions and scopes for Desktime while using Tool Router? Yes, absolutely. You can configure which Desktime 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 Desktime data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)