opendata-ua-mcp
You can use this read-only MCP server to search, inspect, retrieve, filter, and monitor open data from Ukraine’s data.gov.ua portal.
Find datasets by topic/keywords with sorting, tags, format, category, organization, limit, and offset filters.
Explore catalog aggregates: counts by publisher, category, or format, optionally narrowed by query/category/organization.
Inspect a dataset’s metadata: description, publisher, license and URL, freshness, update frequency, and resources with format, size, and machine-readable flags.
Get actual data previews and column schemas, auto-selecting the best machine-readable resource; supports DataStore or local parsing of CSV/JSON/XLSX.
Filter or aggregate structured DataStore resources with exact column filters or read-only SQL SELECT, plus full-text search, field selection, and pagination.
Track recently updated datasets, filterable by topic or organization.
Enables Google Gemini to search and analyze Ukraine's open data portal using natural language queries.
Enables local AI models via Ollama to search and analyze Ukraine's open data portal using natural language queries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@opendata-ua-mcp Find ecology datasets from Lviv 2024"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
opendata-mcp — data.gov.ua MCP server
An open-source MCP server that lets any MCP-compatible AI agent search and analyze Ukraine's national open-data portal data.gov.ua in natural language.
It speaks the Model Context Protocol, so it works with any client that supports MCP — including Claude (Desktop / Code), ChatGPT (Developer Mode / custom connectors), Google Gemini, Cursor, Cline / Continue, VS Code Copilot, local models via Ollama / LM Studio, and your own agents built on the Python/TypeScript MCP SDKs. Not tied to any single vendor.
Phase 1: read-only, public endpoints — no API token, no auth required.
Design
Tools are jobs-to-be-done, not thin API wrappers. Each tool does a complete user task, composes several CKAN calls internally, hides portal quirks (UUID slugs, dirty formats, sparse DataStore, Unicode homoglyphs), and returns a token-efficient slim result (a search hit is ~150 B vs ~17 KB raw).
Tool | What it does |
| Find datasets by topic; ranked slim candidates + refine hints |
| Aggregate view (who publishes / how much) — counts only |
| Full dataset card: license, freshness, resources |
| Get the actual data — auto-picks best resource; DataStore or download+parse CSV/JSON/XLSX/XML, including files inside ZIP archives (ЄДР, debtors registries) |
| Filter rows / read-only SQL over a structured (DataStore) resource |
| Recently updated datasets, filterable by topic/org |
| Server deployments only. Find one record in a full top-demand registry — company by ЄДРПОУ/name, ФОП, vehicle by VIN, VAT payer, bankruptcy case, court hearing — from a local copy refreshed daily |
find_datasets also pins flagship registries asked for by name ("ЄДР", "реєстр ФОП", "авто"), retries zero-result queries with stemmed wildcards, and points searches for non-data services (Дія, court decisions search) to the right site.
Related MCP server: CKAN MCP Server
Install
The server runs over stdio, the transport every MCP client understands. The config below is the same everywhere — only the file/menu where you paste it differs per client.
Any MCP client (npm) — universal
{
"mcpServers": {
"opendata-ua": {
"command": "npx",
"args": ["-y", "@opendata-ua/mcp-server"]
}
}
}Where to put it:
Client | Location |
Claude Desktop | Settings → Developer → Edit Config ( |
Claude Code |
|
ChatGPT | Settings → Connectors → add MCP server (Developer Mode) |
Google Gemini | Gemini CLI / SDK |
Cursor | Settings → MCP → Add Server ( |
Cline / Continue / VS Code | the extension's MCP settings |
Custom agent | point your MCP SDK at |
Claude Desktop — one-click DXT
DXT is Claude Desktop's drag-and-drop bundle format:
Download
opendata-ua-mcp.dxtfrom Releases.Drag it into Claude Desktop → Settings → Extensions. Done. No config.
From source
npm install
npm run build
node dist/stdio.js # any MCP client can spawn thisRemote (Streamable HTTP)
For clients that connect over the network instead of spawning a process:
npm run build
MCP_HTTP_HOST=0.0.0.0 MCP_HTTP_PORT=3000 node dist/http.jsMCP endpoint:
POST http://<host>:3000/mcp(stateless;GET/DELETEreturn 405)Health check:
GET http://<host>:3000/health(returns 503 while the server drains onSIGTERM)
Production notes. There is no authentication by default: either restrict port 3000 with a firewall to your VPN subnet, or set MCP_AUTH_TOKEN (clients then send Authorization: Bearer <token>) and MCP_ALLOWED_HOSTS to pin the Host header. JSON-RPC batches are rejected (400), requests are rate-limited per client IP (MCP_RATE_LIMIT_PER_MINUTE, 429 with Retry-After), bodies are capped at 1 MB, and each tool call has a deadline and a concurrency cap (see the env table). Access logs record IP, status, method and tool name — never arguments. Note that lookup_record serves personal data (names, addresses, VINs) that the public registries publish; deploy it only where that is appropriate.
Registry mirror (lookup_record)
The most-wanted registries are 30 MB–4 GB files, too big to fetch per request. dist/sync.js downloads them in full, streams them (ZIP, XML, CSV in UTF-8 or Windows-1251) into one SQLite file per registry, and skips unchanged resources. Set MIRROR_DIR on the HTTP server to enable lookup_record. Only the columns an answer needs are stored. Needs Node.js 22.5+ (node:sqlite).
MIRROR_DIR=/var/lib/opendata-mcp node dist/sync.js # all registries
MIRROR_DIR=/var/lib/opendata-mcp node dist/sync.js edr-uo --force
MIRROR_DIR=/var/lib/opendata-mcp node dist/sync.js vehicles --inspect # print sample rowsReady-made systemd units (server, daily sync timer) are in deploy/systemd.
{
"mcpServers": {
"opendata-ua": { "type": "http", "url": "http://<host>:3000/mcp" }
}
}Try it
"Find ecology datasets from Lviv published in 2024" "Which organizations publish the most procurement data?" "Show me the first rows of the stolen-vehicles register"
Configuration (optional)
Env var | Default | Purpose |
|
| API base (mirror/dev portal) |
|
| LRU cache TTL for catalogs |
|
| Request timeout |
|
| Per-response context-budget ceiling |
|
| Cap for files downloaded + parsed locally |
|
|
|
|
| HTTP transport bind address ( |
|
| HTTP transport port |
| — | Registry mirror directory; enables |
|
| Deadline for one tool call (all upstream calls + parsing) |
|
| Tool calls running at once per process |
|
| Calls allowed to wait for a slot; beyond that: "busy" |
|
| Simultaneous requests to data.gov.ua |
|
| HTTP transport: requests per minute per client IP ( |
| — | HTTP transport: require |
| — | HTTP transport: accepted |
Develop
npm test # vitest
npm run typecheck
npm run lint
npm run smoke # live test against data.gov.ua
npm run build:dxt # build the .dxt packageThe portal runs CKAN 2.7.2. DataStore (queryable rows) covers only ~0.3 % of resources, so get_dataset_data downloads + parses files locally when needed; filter_data/SQL apply to the DataStore-active minority.
License
MIT © Open Data UA Community
Available Tools
6 toolsexplore_catalogA
Огляд каталогу data.gov.ua агрегатами (без видачі самих датасетів): скільки всього, хто публікує найбільше, розподіл за категоріями/форматами. Дешево за токенами. Використовуй для «хто публікує найбільше даних про X», «скільки датасетів про Y».
Inputs: query, group_by, category, organization, +1 more.
filter_dataA
Фільтрувати/агрегувати рядки структурованого ресурсу: точні фільтри (колонка=значення) або read-only SQL (SELECT). Працює ЛИШЕ для DataStore-активних ресурсів (≈0.3% на порталі — перевір has_datastore через inspect_dataset). Для решти спершу візьми дані через get_dataset_data.
Inputs: resource_id (required), filters, q, sql, +3 more.
find_datasetsA
Знайти датасети на data.gov.ua за темою. Повертає компактний ранжований список кандидатів (назва, розпорядник, формати, свіжість, посилання) + підказки для звуження пошуку (топ розпорядники/категорії/формати). Використовуй це для будь-якого «знайди дані про …».
Inputs: query, category, organization, format, +4 more.
get_dataset_dataA
Отримати самі дані (перші рядки + схема колонок) з датасету чи ресурсу. Автоматично обирає найкращий машиночитний ресурс. Якщо є DataStore — читає звідти; інакше завантажує файл і парсить локально (CSV/JSON/XLSX). Повертає прев'ю (обмежене), оцінку кількості рядків і посилання на повний файл. Це твій основний інструмент для «покажи дані».
Inputs: dataset, resource_id, columns, limit.
inspect_datasetA
Детальна картка одного датасету перед використанням: опис, розпорядник, ліцензія (+URL), свіжість, частота оновлення, і список ресурсів з форматом, розміром та ознакою machine_readable. Приймає ID/slug або назву (автопошук). Далі бери дані через get_dataset_data.
Inputs: dataset (required).
track_updatesA
Стрічка нещодавно оновлених датасетів на data.gov.ua (моніторинг). Можна звузити за темою або розпорядником. Повертає компактний список: назва, розпорядник, коли змінено, тип зміни, посилання.
Inputs: topic, organization, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: catalog overview, data filtering, dataset search, data retrieval, dataset inspection, and update tracking. No overlapping functionality.
All tool names follow a consistent snake_case verb_noun pattern (e.g., explore_catalog, find_datasets), making them predictable and easy to distinguish.
With 6 tools, the server is well-scoped for interacting with an open data portal. Each tool covers a essential operation without redundancy or excessive complexity.
The tool set covers major read operations: search, inspect, retrieve, filter, and monitor updates. Missing a direct 'list all datasets' function, but find_datasets with a broad query can approximate it.
Maintenance
Related MCP Connectors
Public Data Ukraine Mcp connects AI agents to real public APIs via MCP. Tools include
Search a Ukrainian catalog of 21,000+ AI tools — search tools, get details, list categories.
PL/UA public data for agents: tenders, companies, CEIDG, gazette, EV, cars, permits, land, health.
Related MCP Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to search, discover, and analyze thousands of datasets from Israel's national open data portal. It provides tools for querying government ministries, municipalities, and public bodies using the CKAN API.973 npm111MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.202,453 npm79MIT

mcp-data-lvofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, retrieve metadata, and query tabular resources from Latvia's Open Data portal (data.gov.lv) via CKAN.76 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables searching and querying Ukraine Open Data (data.gov.ua) datasets via CKAN API, allowing AI agents to retrieve dataset metadata and tabular data.82 npmMIT