4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
SPTrans Olho Vivo MCP Server

Bring Public Transit
to CrewAI

Learn how to connect SPTrans Olho Vivo to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get All PositionsGet ForecastGet Forecast By LineGet Forecast By StopGet Positions By LineGet Positions In GarageList CompaniesList CorridorsSearch LinesSearch Lines By DirectionSearch StopsSearch Stops By CorridorSearch Stops By Line

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
SPTrans Olho Vivo

What is the SPTrans Olho Vivo MCP Server?

Connect to the SPTrans Olho Vivo API to bring real-time urban mobility intelligence to your AI agent. Monitor the entire São Paulo bus fleet and provide precise transit information through natural conversation.

What you can do

  • Line & Stop Discovery — Search for bus lines by name or number and find specific stops by address or corridor.
  • Real-time GPS Tracking — Fetch the exact coordinates of active buses on any given line or across the entire city fleet.
  • Arrival Forecasts — Get accurate predictions for when the next bus will arrive at a specific stop or for all stops along a route.
  • Corridor & Company Info — List intelligent bus corridors and operating companies to understand the city's transit infrastructure.
  • Garage Status — Monitor vehicles currently in the garage for specific companies and lines.

How it works

  1. Subscribe to this server
  2. Enter your SPTrans Olho Vivo API Token
  3. Start querying São Paulo's transit system from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Commuters & Residents — Get instant updates on bus arrivals and locations without switching between multiple transit apps.
  • Urban Planners & Researchers — Analyze real-time fleet distribution and corridor efficiency directly through AI-driven data extraction.
  • Developers — Integrate São Paulo's transit data into workflows or tools using simple natural language commands.

Built-in capabilities (13)

get_all_positions

Get real-time GPS positions for all active buses

get_forecast

Get arrival forecast for a specific stop and line

get_forecast_by_line

Get arrival forecast for all stops on a specific line

get_forecast_by_stop

Get arrival forecast for all lines arriving at a specific stop

get_positions_by_line

Get real-time GPS positions for buses on a specific line

get_positions_in_garage

Get real-time GPS positions for buses currently in the garage

list_companies

List bus operating companies by area

list_corridors

List all intelligent bus corridors in São Paulo

search_lines

Search for bus lines by number or name

search_lines_by_direction

Search for bus lines filtered by direction

search_stops

Search for bus stops by name or address

search_stops_by_corridor

Get all stops in a specific intelligent corridor

search_stops_by_line

Get all stops for a specific bus line

Why CrewAI?

When paired with CrewAI, SPTrans Olho Vivo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call SPTrans Olho Vivo tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

SPTrans Olho Vivo in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

SPTrans Olho Vivo and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect SPTrans Olho Vivo to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for SPTrans Olho Vivo in CrewAI

The SPTrans Olho Vivo MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

SPTrans Olho Vivo
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures SPTrans Olho Vivo for CrewAI

Every tool call from CrewAI to the SPTrans Olho Vivo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I find the specific code for a bus line?

Use the search_lines tool with the line number or name (e.g., '8000' or 'Lapa'). The agent will return the line code (cl), which is required for tracking positions or forecasts.

02

Can I see the arrival times for all buses at a particular stop?

Yes! Use the get_forecast_by_stop tool with the stop code (cp). It will list all upcoming bus arrivals for that location in real-time.

03

Is it possible to track the live location of buses on a map?

While the MCP returns raw coordinates, you can use get_positions_by_line to get the latitude and longitude of every active bus on a line, which your AI can then describe or plot.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →