How to integrate Motion MCP with CrewAI

This guide walks you through connecting Motion to CrewAI using the Composio tool router. By the end, you'll have a working Motion agent that can list motion tasks due today, create project for product launch, reschedule overdue tasks for tomorrow through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Motion account through Composio's Motion MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Motion logoMotion
Api Key

Motion is an intelligent calendar and project management tool for planning work, meetings, tasks, and team projects. It helps you automatically prioritize your day and keep schedules realistic as plans change.

27 Tools

Introduction

This guide walks you through connecting Motion to CrewAI using the Composio tool router. By the end, you'll have a working Motion agent that can list motion tasks due today, create project for product launch, reschedule overdue tasks for tomorrow through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Motion account through Composio's Motion MCP server.

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

Also integrate Motion with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Motion connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Motion
  • Build a conversational loop where your agent can execute Motion 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 Motion MCP server, and what's possible with it?

The Motion MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Motion account. It provides structured and secure access to your tasks, projects, schedules, recurring tasks, and custom fields, so your agent can create tasks, review projects, update assignments, manage recurring work, and clean up completed items on your behalf.

  • Task creation and planning: Have your agent create new Motion tasks and review existing tasks based on your chosen filters.
  • Task updates and cleanup: Direct your agent to update tasks, remove task assignments, or delete tasks you no longer need.
  • Project visibility: Let the agent list your Motion projects and retrieve the details of a specific project.
  • Recurring work management: Instruct your agent to review recurring tasks and delete recurring work that is no longer relevant.
  • Schedules and workspace details: Have your agent review your schedules, check your Motion user information, list workspace custom fields, or remove custom field data.

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

What is Composio SDK?

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

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step08 STEPS
1

Prerequisites

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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
5

Import dependencies

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")
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 Motion MCP URL
6

Create a Composio Tool Router session for Motion

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["motion"])

url = session.mcp.url
What's happening:
  • You create a Motion only session through Composio
  • Composio returns an MCP HTTP URL that exposes Motion tools
7

Initialize the MCP Server

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,
    )
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.
8

Create a CLI Chatloop and define the Crew

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")
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.

Complete Code

Here's the complete code to get you started with Motion and CrewAI:

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=["motion"],
)
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 Motion through Composio's Tool Router. The agent can perform Motion 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
TOOLS

Supported Tools

Every Motion action and event your agent gets out of the box.

Add Custom Field to Project

Tool to add a custom field value to a project in Motion.

Add Custom Field to Task

Tool to add a custom field value to a task in Motion.

Create Comment

Tool to create a new comment on a Motion task.

Create Custom Field

Tool to create a new custom field in a Motion workspace.

Create Project

Tool to create a new project in Motion.

Create Recurring Task

Tool to create a new recurring task in Motion.

Create Task

Tool to create a new task in Motion.

Delete Custom Field

Tool to delete a custom field from Motion workspace.

Delete Custom Field From Project

Tool to delete a custom field value from a project in Motion.

Delete Custom Field From Task

Tool to delete a custom field value from a task in Motion.

Delete Recurring Task

Tool to delete a recurring task from Motion based on the ID supplied.

Delete Task

Tool to delete a task from Motion based on task ID.

Get My User Information

Tool to get information on the owner of the API key.

Get Project

Tool to retrieve a single project by its ID.

Get Task by ID

Tool to retrieve a task by its ID from Motion.

List comments on task

Tool to get all comments on a specific task.

List Custom Fields

Tool to retrieve all custom fields for a given Motion workspace.

List Projects

Tool to get all projects for a workspace.

List Recurring Tasks

Tool to get all recurring tasks for a workspace.

List Schedules

Tool to get a list of schedules for your user.

List Statuses

Tool to get a list of statuses for a Motion workspace.

List Tasks

Tool to get all tasks for a given query with optional filtering.

List users

Tool to get a list of users for a given workspace or team.

List Workspaces

Tool to retrieve all workspaces a user has access to.

Move Task to Workspace

Tool to move a task to a different workspace in Motion.

Unassign Task

Tool to unassign a task from its current assignee.

Update Task

Tool to update an existing task in Motion.

FRAMEWORKS

How to build Motion MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Motion MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Motion MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Motion MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Motion MCP with Claude Cowork

Codex logo

Codex

Use Motion MCP with Codex

OpenClaw logo

OpenClaw

Use Motion MCP with OpenClaw

Hermes logo

Hermes

Use Motion MCP with Hermes

CLI logo

CLI

Use Motion MCP with CLI

Google ADK logo

Google ADK

Use Motion MCP with Google ADK

LangChain logo

LangChain

Use Motion MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Motion MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Motion MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Motion MCP with LlamaIndex

FAQ

Frequently asked questions

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

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 Motion tools.

Yes, absolutely. You can configure which Motion 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.

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 Motion data and credentials are handled as safely as possible.

Start with Motion.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Motion tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies