How to Use the MotionTools MCP in CrewAI

Q: How do I give my CrewAI agents access to MotionTools?

Pass your Vinkius endpoint URL directly into the mcps array when defining your agent. The framework automatically parses the available logistics tools and makes them ready for use.

Q: Can multiple CrewAI agents share MotionTools data?

Yes. If your research agent pulls an address using getbooking, it stores that in shared memory. Your action agent reads that memory and uses it to run getservicearea without making redundant API calls.

Q: How do I restrict which MotionTools endpoints a CrewAI agent can use?

Use MCPServerHTTP from crewai.mcp and apply a toolfilter. You can give your support agent access to listcustomers while restricting createbooking strictly to your dispatch agent.

Deploy autonomous dispatch teams. Let CrewAI agents manage your MotionTools logistics entirely on their own.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MotionTools MCP to CrewAI

Create your Vinkius account to connect MotionTools to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup MotionTools with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous routing with CrewAI

One agent cannot run a delivery network. You need a crew. Your intake agent monitors incoming orders and runs `create_booking`. It passes the confirmation to the routing agent, which immediately calls `list_service_areas` to determine the best drop-off zone. They share memory. When the routing agent finds the zone, the dispatch agent takes over. It queries `list_drivers` to find the closest worker. The entire sequence happens autonomously. You just watch the logs while the crew handles the logistics.

Delegate fleet tracking to an MCP Server

Trucks break down and drivers get delayed. A dedicated monitoring agent constantly hits `list_vehicles` and `get_vehicle`. It builds a real-time picture of your fleet's health in its working memory. If a vehicle throws a maintenance flag, the monitor alerts the reassignment agent. That agent pulls the active load via `get_booking`, finds a new truck, and updates the system. Nobody in your office lifts a finger. The crew resolves the bottleneck before the customer even notices.

Self-healing delivery queries

When customers flood your inbox asking where their packages are, assign a support agent to handle it. A ticket comes in, and the agent runs `list_customers` to verify the account, then hits `get_booking` to find the exact package coordinates. The agent drafts a response using the live data. If the package is delayed, it asks the dispatch agent for context via `get_driver`. The crew collaborates to give the customer a precise, accurate update based on raw MCP tool data.

Setup guide

Set up MotionTools MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke MotionTools tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="MotionTools Analyst",
    goal="Access and analyze MotionTools data via MCP.",
    backstory="Expert analyst with direct MotionTools access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent MotionTools transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="MotionTools Analyst",
        goal="Access and analyze MotionTools data via MCP.",
        backstory="Expert analyst with direct MotionTools access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent MotionTools transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MotionTools. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect MotionTools now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about MotionTools MCP in CrewAI

Pass your Vinkius endpoint URL directly into the `mcps` array when defining your agent. The framework automatically parses the available logistics tools and makes them ready for use.

Yes. If your research agent pulls an address using `get_booking`, it stores that in shared memory. Your action agent reads that memory and uses it to run `get_service_area` without making redundant API calls.

Use `MCPServerHTTP` from `crewai.mcp` and apply a `tool_filter`. You can give your support agent access to `list_customers` while restricting `create_booking` strictly to your dispatch agent.

Yes. You can configure a monitor agent to run sequentially, polling `list_bookings` at set intervals to watch for stalled deliveries.

Yes. When your agents pull VINs and registration details via `list_vehicles`, the data passes through a Vinkius zero-trust boundary. The execution context is completely ephemeral, meaning sensitive fleet records never persist on the middleware layer.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript