# How to integrate Worksnaps MCP with CrewAI ```json { "title": "How to integrate Worksnaps MCP with CrewAI", "toolkit": "Worksnaps", "toolkit_slug": "worksnaps", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/worksnaps/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/worksnaps/framework/crew-ai.md", "updated_at": "2026-05-12T10:30:40.526Z" } ``` ## Introduction This guide walks you through connecting Worksnaps to CrewAI using the Composio tool router. By the end, you'll have a working Worksnaps agent that can show your total hours logged this week, list all tasks for project alpha, create a new project for client onboarding through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Worksnaps account through Composio's Worksnaps MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Worksnaps with - [OpenAI Agents SDK](https://composio.dev/toolkits/worksnaps/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/worksnaps/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/worksnaps/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/worksnaps/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/worksnaps/framework/codex) - [OpenClaw](https://composio.dev/toolkits/worksnaps/framework/openclaw) - [Hermes](https://composio.dev/toolkits/worksnaps/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/worksnaps/framework/cli) - [Google ADK](https://composio.dev/toolkits/worksnaps/framework/google-adk) - [LangChain](https://composio.dev/toolkits/worksnaps/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/worksnaps/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/worksnaps/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/worksnaps/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Worksnaps connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Worksnaps - Build a conversational loop where your agent can execute Worksnaps 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 Worksnaps MCP server, and what's possible with it? The Worksnaps MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Worksnaps account. It provides structured and secure access to your time tracking and project data, so your agent can perform actions like tracking project hours, managing tasks, retrieving detailed reports, and accessing user assignments on your behalf. - Project and task management: Direct your agent to create new projects, add tasks, or delete tasks from specific projects for streamlined workflow organization. - Comprehensive project reporting: Request detailed time tracking reports for individual projects, including daily summaries and custom date ranges. - Account and assignment insights: Let your agent fetch account details and list all user assignments to see which projects you're working on or managing. - Quick project overview retrieval: Ask the agent to list all accessible projects or view detailed information about any project with just a prompt. - Task detail and status checks: Retrieve details for any task within a project, so you can stay on top of progress and workload effortlessly. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `WORKSNAPS_CREATE_PROJECT` | Create Project | Creates a new project in Worksnaps for tracking time and tasks. Use this tool when you need to set up a new project for time tracking. Projects serve as containers for tasks and time entries. Each project must have a unique name within the account. Note: Account plan limits may restrict the number of projects that can be created. | | `WORKSNAPS_CREATE_TASK` | Create task | Tool to create a new task in a specified project. Use after confirming project ID exists. | | `WORKSNAPS_DELETE_TASK` | Delete Task | Permanently deletes a task from a Worksnaps project. This action is destructive and cannot be undone. Use GET_TASKS first to find the task_id, and GET_PROJECTS to find the project_id. Returns success=true if the task was deleted. Returns 404 error if project or task does not exist. | | `WORKSNAPS_GET_PROJECT_DETAILS` | Get Project Details | Tool to retrieve details of a specific project. Use when you have a project_id and need its details. | | `WORKSNAPS_GET_PROJECT_REPORT` | Get Project Report | Retrieves time entries for a specific project using the Worksnaps Time Entries API. Returns individual time tracking records showing when users worked on the project. Use this to get detailed time tracking data for a project within a timestamp range. Timestamps must be Unix timestamps at 10-minute interval boundaries. | | `WORKSNAPS_GET_PROJECTS` | Get Projects | Tool to retrieve a paginated list of projects. Use after authenticating to list accessible projects. | | `WORKSNAPS_GET_TASK_DETAILS` | Get Task Details | Tool to retrieve details of a specific task within a project. Use after confirming project_id and task_id. | | `WORKSNAPS_GET_TASKS` | Get Project Tasks | Tool to retrieve tasks for a specific project. Use when you have a project ID and need its tasks. Example: 'Get tasks for project 42'. | | `WORKSNAPS_GET_USER_ACCOUNT` | Get User Account | Tool to retrieve information about a specific user account. Use after confirming the user_id. | | `WORKSNAPS_GET_USER_ASSIGNMENTS` | Get User Assignments | Tool to retrieve a list of all user assignments for a specific project. Returns details about users assigned to the project including their roles, permissions, and contact information. | | `WORKSNAPS_GET_USERS` | Get Users | Retrieves a list of all users in the Worksnaps account. Returns user details including id, login, name, email, time zone, and active status. Use this to get user IDs for other user-related operations. | | `WORKSNAPS_PUT_UPDATE_PROJECT` | Update Project | Tool to update an existing project. Use when you have project_id and fields to modify. | | `WORKSNAPS_PUT_UPDATE_TASK` | Update Task | Tool to update details of an existing task. Use when you have project_id, task_id, and fields to update. | | `WORKSNAPS_PUT_UPDATE_USER_ACCOUNT` | Update User Account | Tool to update information for a specific user account. Use when modifying user details after confirming the user exists. Note: This can only be done by the user himself or by a trusted partner using partner's API token. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Worksnaps MCP server is an implementation of the Model Context Protocol that connects your AI agent to Worksnaps. It provides structured and secure access so your agent can perform Worksnaps 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 Worksnaps 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 Worksnaps 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 Worksnaps 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 Worksnaps **What's happening:** - You create a Worksnaps only session through Composio - Composio returns an MCP HTTP URL that exposes Worksnaps tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["worksnaps"]) 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=["worksnaps"], ) 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 Worksnaps through Composio's Tool Router. The agent can perform Worksnaps 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 Worksnaps MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/worksnaps/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/worksnaps/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/worksnaps/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/worksnaps/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/worksnaps/framework/codex) - [OpenClaw](https://composio.dev/toolkits/worksnaps/framework/openclaw) - [Hermes](https://composio.dev/toolkits/worksnaps/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/worksnaps/framework/cli) - [Google ADK](https://composio.dev/toolkits/worksnaps/framework/google-adk) - [LangChain](https://composio.dev/toolkits/worksnaps/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/worksnaps/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/worksnaps/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/worksnaps/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 Worksnaps MCP? With a standalone Worksnaps MCP server, the agents and LLMs can only access a fixed set of Worksnaps tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Worksnaps 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 Worksnaps tools. ### Can I manage the permissions and scopes for Worksnaps while using Tool Router? Yes, absolutely. You can configure which Worksnaps 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 Worksnaps data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)