Open Data Euskadi MCP for AI. Analyze Basque public records in conversation.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Open Data Euskadi connects your AI client directly to the official open data portal of the Basque Government. It lets you search through public grants, contracts, and news using advanced filters, or run raw SPARQL queries against structured regional data for deep analysis.
You get verifiable facts and localized context in one conversation.
What your AI can do
Execute sparql query
Runs a raw SPARQL query against the Open Data Euskadi GraphDB endpoint to extract highly precise, structured data points.
Search euskadi content
Searches the entire Euskadi.eus content catalog for news articles, grants, and administrative documentation using natural language queries.
Query the Euskadi content catalog for active grants, subsidies, or funding programs using specific filters.
Execute raw SPARQL queries against the Linked Open Data graph to retrieve highly structured and machine-readable triples of information.
Search and query public records related to administration and awarded contracts in real-time.
Narrow down search results using metadata filters for specific dates, languages, or administrative contexts.
Access specialized public data feeds, such as meteorological information from Euskalmet (if properly authorized).
Ask an AI about this
Waiting for input…
Open Data Euskadi MCP Server: 2 Tools for Regional Data
These two tools allow your AI agent to search unstructured content and execute complex structured queries against the Basque Government's public data.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Open Data Euskadi on VinkiusExecute Sparql Query
Runs a raw SPARQL query against the Open Data Euskadi GraphDB endpoint to extract highly precise, structured data points.
Search Euskadi Content
Searches the entire Euskadi.eus content catalog for news articles, grants, and...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Open Data Euskadi, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Open Data Euskadi. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Digging through official government websites is a nightmare of PDFs and manual filters.
Today, finding information on public grants or contracts means bouncing between dozens of departmental sites. You download a PDF here, cross-reference a spreadsheet there, and then copy-paste dates from an announcement page just to build a single timeline. It's slow, error-prone work.
With Open Data Euskadi MCP Server, you skip the clicking entirely. You tell your agent what records you need—say, 'All SME grants in 2023.' Your AI client finds the relevant metadata using `search_euskadi_content` and then pulls all structured details into a clean format.
Using Open Data Euskadi MCP Server: Precise data extraction with SPARQL.
Manual querying means writing complex, bespoke queries in specialized tools. If you miss one triple or forget a variable, the whole thing breaks, and you're back to square one.
Now, your agent handles the complexity. You just ask: 'List all contractors who received funding over €50k last quarter.' The server runs `execute_sparql_query` against the graph, giving you only the exact records that match, nothing more.
What your AI can actually do with this
You're connecting your AI client straight into the open data portal for the Basque Government. This server lets you bypass keyword searches and talk directly to public records—everything from grants and contracts to administrative news. You get verifiable, localized facts without having to navigate a dozen different government websites.
Your agent uses two core tools to handle everything: search_euskadi_content for narrative context, and execute_sparql_query for rock-solid data points. You'll use these to dig through the entire Euskadi.eus content catalog or query deep, structured datasets.
When you need to search public documents—like tracking government contracts or finding active grants and subsidies—you kick off a request using search_euskadi_content. This tool lets your agent look across news articles, administrative procedures, and published documentation within the Euskadi.eus ecosystem. You'll tell it exactly what you're looking for, and it handles filtering by context and date range automatically.
For instance, if you only care about grants awarded in 2023 related to technology, you filter those parameters directly into the search, narrowing down results using metadata filters for specific dates or languages.
If your job requires precision—like pulling a list of all vendors who received contracts over $X amount last quarter—you don't use a general search. You use execute_sparql_query. This tool runs raw SPARQL queries against the Open Data Euskadi GraphDB endpoint. That means you supply structured query language, and it returns highly precise, machine-readable triples of information.
It’s built for deep analysis where simple searching falls short; you're pulling relationships between data points, not just matching keywords.
Your agent can retrieve specialized public feeds using the graph database connection. You can access things like meteorological readings from Euskalmet (if your client is authorized) or other structured datasets that require a complex query to pull them out. The combination of these tools means you're never stuck with vague results; you get both the written context and the underlying, verifiable data points.
Think about it: You can use search_euskadi_content to find an article mentioning a specific contract award, and then immediately run execute_sparql_query using details from that article—like the contract ID or date range—to pull up the official, structured records proving exactly who was paid how much. This workflow lets you move beyond simple keyword searches and validate every single claim with verifiable public data.
You're not just getting a summary; you're executing complex operations against two different types of source material: unstructured text (via search_euskadi_content) and structured graph data (via execute_sparql_query). You can find information about funding programs, track the status of administrative documents, or pull deep historical records by specifying language requirements, date limitations, and administrative contexts across both tools.
The whole thing boils down to this: you're getting a single conversational interface that gives your AI client direct access to the full spectrum of Basque public data—the narratives, the rules, and the cold hard numbers.
019e38cc-74ad-7256-8e79-14998890c103 Here's how it actually works
The bottom line is: you talk naturally, and the server handles the complex combination of searching unstructured documents and executing precise graph queries for you.
First, subscribe to the Open Data Euskadi server and provide any necessary credentials, like your Euskalmet JWT.
Next, tell your AI client what you're looking for—for instance, 'Find all 2024 grants related to tech.'
The agent uses search_euskadi_content first. Then, if needed, it converts those parameters into a structured query and executes it with execute_sparql_query.
Who is this actually for?
Data analysts who are tired of manual API calls. Legal professionals needing to track government grants faster than a paralegal can copy-paste. Developers building internal tools that need official, verifiable Basque regional data streams.
Uses execute_sparql_query to map relationships between different public datasets (e.g., connecting environmental readings with demographic data).
Runs targeted searches using search_euskadi_content to pull the metadata and details of past government contracts or subsidies.
Integrates official data feeds, like news announcements or administrative procedures, directly into an application's backend logic using structured queries.
What Changes When You Connect
You stop manually exporting CSV files. By using the two tools together, your AI client performs complex data synthesis—it searches for context and then extracts the verifiable facts from the graph automatically.
Get precise results using execute_sparql_query. Instead of wading through paragraphs, you get machine-readable triples that define exactly what happened (e.g., 'Grant X awarded to Company Y on Date Z').
Track public grants and contracts instantly. Use search_euskadi_content to locate the relevant documentation metadata, saving hours of manual site browsing.
Filter everything down fast. You can use advanced filters within the search tool to narrow results by language, date range, or specific administrative context before running a query.
Cross-reference data types easily. Find a topic in news (via search_euskadi_content), and then immediately validate key metrics about that topic using a structured SPARQL query.
See it in action
Tracking Grant Eligibility
A legal professional needs to know if the requirements for 'Digital Transformation Subsidies 2024' changed this year. They ask their agent: 'What were the criteria, and are there any updates?' The agent uses search_euskadi_content to find the latest announcement articles, then runs a SPARQL query against those records to pull structured eligibility dates and required documentation types.
Mapping Environmental Trends
A researcher wants to correlate recent public announcements about 'sustainability' with actual recorded environmental data. They first use search_euskadi_content to find all articles tagged 'green energy,' then feed those results into a SPARQL query to retrieve the corresponding environmental sensor readings for that area.
Building an Automated News Feed
A developer needs to build a dashboard showing only high-priority governmental announcements. They use search_euskadi_content with filters for 'board notices' and the current date, then run a SPARQL query to ensure the returned data points include all necessary identifiers (ID, title, department) for database ingestion.
Verifying Contract Details
A team member needs confirmation on specific awarded contracts. They start by searching using search_euskadi_content to find the contract ID in the news feed, and then use that precise ID in an execute_sparql_query to pull the official amounts, signatories, and effective dates.
The honest tradeoffs
Searching for numbers only
Just asking 'What was the grant amount?' The agent can't answer because it doesn't know which grant you mean. It gives a vague list of potential grants.
First, use search_euskadi_content to locate the specific grant record or news article about the funding program. Then, reference that found information when executing your structured query with execute_sparql_query.
Assuming all data is searchable
Asking for a comparison of 'Environmental data vs. Legal notices' in one go. The system gets confused because the tools handle different kinds of information.
Break it up. Use search_euskadi_content to gather context from the legal side, then use execute_sparql_query specifically for the structured environmental datasets you want to compare.
Forgetting necessary credentials
Trying to pull real-time meteorological data without authorizing the connection. The query fails with a permission error.
Remember that specialized feeds require authentication. Check if Euskalmet data is needed, and ensure you've entered your JWT key before running any related queries.
When It Fits, When It Doesn't
Use this server when the answer requires both narrative context AND verifiable facts. Don’t use it if you just need a general web search—a standard search engine works fine for that. But, if you're dealing with official Basque government records (grants, contracts, public notices), this is your tool. Use search_euskadi_content when the user intent is 'What happened?' or 'Tell me about X.' Use execute_sparql_query when the user intent is 'Give me a list of all Y that fit criteria Z.' If you need to validate numbers, dates, or relationships found in the news, run SPARQL after searching. Don't try to combine them in one shot; guide your agent to use the context from search as input for the query.
Questions you might have
How do I use execute_sparql_query with Open Data Euskadi? +
You prompt your agent to write and run a SPARQL query. You don't need to know the syntax; just tell it what you want—like 'list all public transport schedules.' It handles the execution.
Can search_euskadi_content find data that execute_sparql_query can? +
No. search_euskadi_content finds unstructured text—like news articles or announcements. You run SPARQL when you need structured, quantifiable facts (triples) about those topics.
What if I only know the topic, not the data structure? +
Start with search_euskadi_content. Use it to gather all relevant documentation and context. This helps you figure out what parameters or IDs you need before attempting a structured query.
Do I need an account for Open Data Euskadi? +
You must subscribe to the server on Vinkius. If you are accessing specialized data like weather, you might also need to provide specific credentials, such as your Euskalmet JWT.
What happens if I need to authenticate when using execute_sparql_query? +
You must provide the necessary credentials or JWT token as defined by the tool schema. If a resource requires authorization, your AI client will prompt you for the required key before running the query.
Does search_euskadi_content handle complex metadata filtering like date ranges? +
Yes, it does. When calling search_euskadi_content, you can pass specific filters—like a publication date range or language code—to narrow the results precisely to what you need.
Are there rate limits I should know about when executing multiple queries with execute_sparql_query? +
The service manages standard request volume, but continuous, high-frequency querying may encounter throttling. If your agent hits a limit, it will receive a specific error code you can use to adjust your query pace.
What format does execute_sparql_query return the retrieved Linked Open Data in? +
The tool returns structured data, typically as a list of records or JSON object. This clean output structure allows your agent to process the information immediately without needing manual parsing.
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).
We've already built the connector for Open Data Euskadi. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.