# How to integrate Timely MCP with CrewAI ```json { "title": "How to integrate Timely MCP with CrewAI", "toolkit": "Timely", "toolkit_slug": "timely", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/timely/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/timely/framework/crew-ai.md", "updated_at": "2026-05-12T10:28:37.961Z" } ``` ## Introduction This guide walks you through connecting Timely to CrewAI using the Composio tool router. By the end, you'll have a working Timely agent that can get your timely account billing details, set up webhook for new time entries, retrieve account info for client project through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Timely account through Composio's Timely MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Timely with - [OpenAI Agents SDK](https://composio.dev/toolkits/timely/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timely/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timely/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timely/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timely/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timely/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timely/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timely/framework/cli) - [Google ADK](https://composio.dev/toolkits/timely/framework/google-adk) - [LangChain](https://composio.dev/toolkits/timely/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/timely/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/timely/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timely/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Timely connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Timely - Build a conversational loop where your agent can execute Timely 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 Timely MCP server, and what's possible with it? The Timely MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Timely account. It provides structured and secure access to your time-tracking data, so your agent can perform actions like retrieving account information, managing webhooks, and integrating time logs with other workflows on your behalf. - Account information retrieval: Instantly fetch up-to-date details about your Timely account, including billing, activity, and user info, for streamlined reporting or troubleshooting. - Automated webhook setup: Direct your agent to create new webhooks for your account, enabling real-time integration with external apps and automated event notifications. - Seamless workflow automation: Connect Timely events to other services or agents by configuring webhooks, so you can automate time-tracking updates or project triggers. - Centralized time management: Allow your agent to coordinate between Timely and your other productivity tools by securely accessing and sharing account data as needed. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TIMELY_CREATE_CLIENT` | Create Client | Tool to create a new client in the specified Timely account. Use when adding a new client to track time against. Client names must be unique within an account. | | `TIMELY_CREATE_DAY_LOCKING` | Create Day Locking | Tool to create a day locking entry that prevents editing of time entries for specific dates and users. Use when you need to lock time entries to prevent modifications after approval or billing. | | `TIMELY_CREATE_LABEL` | Create Label | Tool to create a new label in the specified Timely account. Use when you need to create a label for categorizing projects, time entries, or other resources. | | `TIMELY_CREATE_REPORT` | Create report | Tool to generate reports for a Timely account with optional filters. Use when you need to create reports for time tracking, billing analysis, or project summaries with date range or user/project filters. | | `TIMELY_CREATE_TEAM` | Create Team | Tool to create a new team in the specified Timely account. Use when organizing users into teams for better collaboration and project management. | | `TIMELY_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for the specified account. Use after specifying the target URL and event subscriptions. Call only once per configuration. | | `TIMELY_DELETE_LABEL` | Delete a label | Tool to delete a label by ID from a Timely account. Use when you need to remove an existing label. | | `TIMELY_DELETE_TEAM` | Delete a team | Tool to delete a team by its ID. Use when you need to remove a specific team from the account. This operation is destructive and cannot be undone. | | `TIMELY_DELETE_WEBHOOK` | Delete Webhook | Tool to delete an existing webhook by its ID. Use when you need to remove a webhook subscription from an account. | | `TIMELY_FILTER_REPORTS` | Filter reports | Tool to filter Timely reports based on date range, users, projects, labels, teams, and billing status. Use when you need to generate custom reports with specific criteria or analyze time tracking data for specific periods or resources. | | `TIMELY_GET_ACTIVITIES` | Get activities | Tool to retrieve all activities (audit trail) for a Timely account. Activities include logged hours, created reports, shared reports, project changes, and other account events. Use when you need to view the activity log or audit trail for an account. | | `TIMELY_GET_CLIENT` | Get Client | Tool to retrieve details of a specific client by its ID. Use when you need to fetch client information such as name, color, active status, or external references. | | `TIMELY_GET_CURRENT_PERMISSIONS` | Get current user's permissions | Tool to retrieve the current user's permissions for a specified account. Use when you need to check what actions the authenticated user can perform. | | `TIMELY_GET_CURRENT_USER` | Get current user | Tool to retrieve the currently authenticated user. Use when you need to get details of the logged-in user. | | `TIMELY_GET_LABEL` | Retrieve a label | Tool to retrieve a label by ID from a Timely account. Use when you need to fetch label details such as name, color, and parent relationship. | | `TIMELY_GET_PROJECT` | Get project | Tool to retrieve a single project by its ID. Use when you need detailed information about a specific project, such as its name, budget, billable status, or associated client. | | `TIMELY_GET_TEAM` | Retrieve a team | Tool to retrieve details of a specific team by its ID. Use when you need to fetch team information including name, color, and members. | | `TIMELY_GET_USER` | Retrieve a user | Tool to retrieve a user by ID from a Timely account. Use when you need to fetch user details such as name, email, and avatar. | | `TIMELY_GET_USER_CAPACITIES` | Get user capacities | Tool to retrieve capacity information for a specific user in a Timely account. Use when you need to check user work capacity or availability schedules. | | `TIMELY_GET_USER_PERMISSIONS` | Get user permissions | Tool to retrieve a user's permissions by their ID. Use when you need to check what permissions a specific user has in a Timely account. | | `TIMELY_GET_WEBHOOK` | Get Webhook | Tool to retrieve a specific webhook by its ID. Use when you need to check the configuration or status of an existing webhook. | | `TIMELY_LIST_ACCOUNTS` | List accounts | Retrieve all accessible Timely accounts for the authenticated user. Example: "List all Timely accounts" | | `TIMELY_LIST_CLIENTS` | List clients | Tool to list all clients in a Timely account with optional filtering and sorting. Use when you need to discover client IDs or names for project creation, reporting, or mapping external systems. | | `TIMELY_LIST_EVENTS` | List events | Tool to list all events (time entries) in a Timely account with optional filtering by date range, users, and projects. Use when you need to retrieve time entries for reporting, analysis, or synchronization with external systems. | | `TIMELY_LIST_FORECASTS` | List forecasts | Tool to list all forecasts (tasks) in a Timely account with optional date filtering. Use when you need to view planned tasks, retrieve forecast IDs, or analyze scheduled work. | | `TIMELY_LIST_LABELS` | List labels | Tool to list all labels in a Timely account. Use when you need to discover label IDs or names for organizing projects and time entries. Can optionally filter to show only child labels by providing a parent_id. | | `TIMELY_LIST_PROJECT_EVENTS` | List project events | Tool to list all events (time entries) for a specific project in Timely. Use when you need to retrieve all time logs associated with a project for reporting, analysis, or verification. | | `TIMELY_LIST_PROJECTS` | List projects | Tool to list all projects in a Timely account with optional filtering and sorting. Use when you need to discover project IDs or names for time entry creation, reporting, or mapping external systems. | | `TIMELY_LIST_ROLES` | List roles | Tool to list all available roles in a Timely account. Use when you need to discover role IDs or names for user assignment or permission management. | | `TIMELY_LIST_TEAMS` | List teams | Tool to list all teams in the specified Timely account. Use when you need to retrieve all teams for collaboration and project management purposes. | | `TIMELY_LIST_USER_EVENTS` | List user events | Tool to list all events (time entries) for a specific user in Timely. Use when you need to retrieve all time logs for a user for reporting, analysis, or verification. | | `TIMELY_LIST_USERS` | List users | Tool to list all users in a Timely account with optional filtering and pagination. Use when you need to discover user IDs, names, or emails for time entry creation, reporting, or user management. | | `TIMELY_LIST_WEBHOOKS` | List Webhooks | Tool to list all webhooks in the specified account. Use when you need to see existing webhook configurations or verify webhook setup. | | `TIMELY_PROCESS_BULK_EVENTS` | Process bulk events | Tool to create, update, or delete multiple events in a single bulk operation. Use when performing multiple event operations to improve efficiency. Supports up to 100 operations per request across create, update, and delete operations. | | `TIMELY_RETRIEVE_ACCOUNT` | Retrieve an account | Tool to retrieve details of a specific account by its ID. Use when you need to fetch fresh account info after confirming the ID. Example: "Retrieve account details for account ID 364" | | `TIMELY_UPDATE_CLIENT` | Update a client | Tool to update an existing client by ID in Timely. Use when you need to modify client details such as name, status, color, or external ID. | | `TIMELY_UPDATE_DAY_LOCKING` | Update day locking settings | Tool to update day locking settings for specified users and dates. Use when you need to lock or unlock specific days for time tracking. Locked days prevent users from editing time entries on those dates. | | `TIMELY_UPDATE_LABEL` | Update a label | Tool to update a label by ID in a Timely account. Use when you need to modify an existing label's name, color, or hierarchy. | | `TIMELY_UPDATE_PROJECT` | Update a project | Tool to update a project by ID in a Timely account. Use when you need to modify project details such as name, description, billing status, or archive a project. | | `TIMELY_UPDATE_USER` | Update a user | Tool to update a user by ID in a Timely account. Use when you need to modify user details such as email, name, role, or status. | | `TIMELY_UPDATE_WEBHOOK` | Update Webhook | Tool to update an existing webhook by ID. Use when you need to modify webhook settings such as URL, subscriptions, or active status. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Timely MCP server is an implementation of the Model Context Protocol that connects your AI agent to Timely. It provides structured and secure access so your agent can perform Timely 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 Timely 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 Timely 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 Timely 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 Timely **What's happening:** - You create a Timely only session through Composio - Composio returns an MCP HTTP URL that exposes Timely tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["timely"]) 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=["timely"], ) 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 Timely through Composio's Tool Router. The agent can perform Timely 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 Timely MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/timely/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timely/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timely/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timely/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timely/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timely/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timely/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timely/framework/cli) - [Google ADK](https://composio.dev/toolkits/timely/framework/google-adk) - [LangChain](https://composio.dev/toolkits/timely/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/timely/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/timely/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timely/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 Timely MCP? With a standalone Timely MCP server, the agents and LLMs can only access a fixed set of Timely tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Timely 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 Timely tools. ### Can I manage the permissions and scopes for Timely while using Tool Router? Yes, absolutely. You can configure which Timely 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 Timely data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)