Compatible with every major AI agent and IDE
What is the OpenDataSUS MCP Server?
Connect to the OpenDataSUS portal to explore and analyze Brazilian public health information through natural language. This server interfaces with the CKAN-based API of the Ministry of Health.
What you can do
- Dataset Discovery — List all available datasets, search for specific health topics (like COVID-19 or vaccination), and browse by tags or categories.
- Metadata Inspection — Retrieve detailed metadata for packages and individual resources to understand data provenance and structure.
- Deep Data Querying — Use the DataStore search to filter and retrieve actual rows from CSV and Excel resources directly into your conversation.
- Organizational Browsing — List data providers and organizations to find specific departmental records.
How it works
- Subscribe to this server
- (Optional) Enter your OpenDataSUS API Key for higher rate limits
- Start querying Brazilian health data from Claude, Cursor, or any MCP client
Who is this for?
- Data Scientists & Researchers — quickly find and sample epidemiological data without manual downloads
- Public Health Analysts — monitor health indicators and dataset updates through simple queries
- Developers — integrate official Brazilian health data into applications and dashboards with ease
Built-in capabilities (8)
Search and filter data within a resource
List all groups (categories)
List all organizations (data providers)
List all dataset names in the OpenDataSUS portal
Search for datasets matching specific criteria
Get full metadata of a specific dataset
Get metadata for a specific resource
List all tags used across datasets
Why CrewAI?
When paired with CrewAI, OpenDataSUS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenDataSUS 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
mcpsparameter 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
OpenDataSUS in CrewAI
OpenDataSUS and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenDataSUS 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OpenDataSUS in CrewAI
The OpenDataSUS 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 8 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.

* 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
How Vinkius secures
OpenDataSUS for CrewAI
Every tool call from CrewAI to the OpenDataSUS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I search for specific rows inside a large CSV dataset?
You can use the datastore_search tool. Provide the resource_id and use the q parameter for full-text search or the filters parameter to target specific columns.
Can I find which organizations provide the most datasets?
Yes! Use the organization_list tool to see all data providers registered in the OpenDataSUS portal.
How do I get the download link for a specific data file?
Use the resource_show tool with the Resource UUID. It will return the metadata including the URL where the file is hosted.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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 →
FOIA.gov (Freedom of Information)
4 toolsAccess US government FOIA data — list agency components, retrieve request forms, and fetch annual reports directly from FOIA.gov.

Shovels
7 toolsConstruction and permit data platform — search contractors and building permits via AI.

Dripcel
10 toolsEquip your AI agent to manage WhatsApp instances, track contacts, and monitor messaging automation via the Dripcel API.

BallDontLie
8 toolsNBA data platform — access player stats, team info, and game results via AI.
