Compatible with every major AI agent and IDE
What is the Open Data Euskadi MCP Server?
Connect to the Open Data Euskadi ecosystem and interact with the Basque Government's official public data through natural conversation. This server provides direct access to a vast catalog of administrative and semantic information.
What you can do
- Content Search — Query the Euskadi.eus catalog for grants, public contracts, news, and administrative procedures using advanced filters.
- Linked Open Data (LOD) — Execute raw SPARQL queries against the GraphDB endpoint to retrieve structured RDF data for deep analysis.
- Administrative Transparency — Access real-time information on public announcements, board notices, and governmental publications.
- Meteorological Data — Retrieve specialized datasets, including weather information from Euskalmet when authorized.
- Metadata Filtering — Narrow down results by language, date ranges, and specific portal contexts to find exactly what you need.
How it works
- Subscribe to this server
- Enter your Euskalmet JWT (optional for public data)
- Start querying Basque public data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Data Analysts & Researchers — perform complex semantic queries across public datasets without manual exports
- Legal & Administrative Professionals — track public grants, subsidies, and government contracts in real-time
- Developers — integrate official Basque government data and news feeds directly into your AI-driven workflows
Built-in capabilities (2)
Execute a SPARQL query against Open Data Euskadi
Search the Euskadi.eus content catalog
Why CrewAI?
When paired with CrewAI, Open Data Euskadi becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Open Data Euskadi 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
Open Data Euskadi in CrewAI
Open Data Euskadi and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Open Data Euskadi 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 Open Data Euskadi in CrewAI
The Open Data Euskadi 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 2 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
Open Data Euskadi for CrewAI
Every tool call from CrewAI to the Open Data Euskadi 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 filter content by a specific language or date range?
You can use the metadata_filters parameter in the search_euskadi_content tool. For example, use documentLanguage.EQ.es for Spanish or procedureStartDate.BETWEEN.01/01/2023,31/12/2023 for dates.
Can I perform advanced semantic analysis on the data?
Yes! Use the execute_sparql_query tool to run raw SPARQL queries against the Linked Open Data (LOD) endpoint. This allows you to traverse relationships in the RDF graph directly.
What types of administrative content can I search for?
The search_euskadi_content tool allows you to filter by content_type. Common types include ayuda_subvencion (grants), contratacion (contracts), noticia (news), and anuncio_tablon (board notices).
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 →
Podchaser Podcast API
4 toolsSearch global podcasts — audit episodes, hosts, and ratings via AI.

Gumlet
12 toolsOptimize images and stream video with automatic format conversion, lazy loading, and CDN delivery that loads pages faster.

Plecto
11 toolsAutomate KPI dashboards and data tracking via Plecto — manage registrations, dashboards, and teams directly from any AI agent.

Fleetio
12 toolsManage vehicles, track maintenance, and monitor fuel entries via AI agents with Fleetio.
