How to Use the CTA MCP in CrewAI

Q: Can I filter tools for a specific CrewAI agent?

Yes, use the toolfilter option to limit which CTA functions an agent can access. This ensures your research agent only sees the discovery tools while the monitor agent handles tracking.

Deploy autonomous transit monitoring crews in CrewAI with this CTA MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CTA MCP to CrewAI

Create your Vinkius account to connect CTA 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 CTA with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinated transit crews for CrewAI

Assign one agent to watch `get_train_positions` while another manages passenger alerts using `get_service_alerts`. This division of labor keeps your monitoring crew efficient. Sharing memory between agents allows your team to maintain a global view of the L system. They act as a cohesive unit to track and report on network health.

Automated transit reporting using CrewAI

Task your agents with generating daily commute summaries by querying `get_bus_routes` and `get_route_directions`. The crew aggregates this data into a structured report for the end user. This removes the manual effort of gathering transit info. Your specialized agents handle the research and synthesis automatically.

Fleet visualization via CrewAI

Use the output of `get_bus_vehicles` to let your agents visualize the entire Chicago bus fleet. The crew processes these coordinates to identify bottlenecks or service gaps. This turns raw tracking data into actionable intelligence. Your agents provide the analysis needed to understand fleet distribution across the city.

Setup guide

Set up CTA 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 CTA tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent CTA 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="CTA Analyst",
        goal="Access and analyze CTA data via MCP.",
        backstory="Expert analyst with direct CTA access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent CTA 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 CTA. 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 CTA 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 CTA MCP in CrewAI

Pass the server URL directly into your agent's mcp configuration list. This grants the crew access to all transit tools without any complex setup.

Yes, use the tool_filter option to limit which CTA functions an agent can access. This ensures your research agent only sees the discovery tools while the monitor agent handles tracking.

It supports SSE and HTTP transports, making it easy to link the server to your agents. Just define the endpoint and the crew will initialize the connection.

Your agents can run periodic checks using the status tools to keep the crew informed. This allows for proactive rather than reactive management of transit queries.

The server operates in a sandboxed environment, ensuring that your transit data requests remain isolated. No historical data regarding your queries is kept on our systems.

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