data-bs-mcp
# data-bs-mcp
MCP server for any Huwise/Opendatasoft data portal.
## Installation
```bash
uv sync
```
## Usage
```bash
uv run main.py
```
## Debug
```bash
npx @modelcontextprotocol/inspector uv run main.py
```
### Install with uvx
```bash
uvx --from git+https://github.com/DCC-BS/mcp-data-bs data-bs-mcp
```
## Selecting a catalog
The catalog is chosen by whoever deploys the server via the `.env` file next to
`main.py`. All Huwise/Opendatasoft portals share the same API
path, so you only set the domain:
```
# .env
DATA_PORTAL_DOMAIN=data.bl.ch
```
The full API base URL is built as
`https://<domain>/api/explore/v2.1`.
The `.env` file is committed, so a fork carries its
catalog choice through `uvx` installs as well.
## Configuration
### OpenCode
Add to your OpenCode config:
```json
{
"mcpServers": {
"data-bs": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/data-bs-mcp",
"run",
"main.py"
]
}
}
}
```
### Cursor
Add to your Cursor config (`~/.cursor/mcp.json`):
```json
{
"mcpServers": {
"data-bs": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/data-bs-mcp",
"run",
"main.py"
]
}
}
}
```
## Tools
### `get_datasets`
Search and list available datasets.
Two search modes:
- `semantic` (default): ranks the catalog by meaning using the `vector_similarity` explore endpoint from Huwise. Best for natural-language / conceptual queries. Matches synonyms and other languages.
- `lexical`: classic full-text match on the exact terms.
```
# semantic (default) — natural language, ranked by relevance
get_datasets(search="air quality measurements")
# lexical — exact full-text match
get_datasets(search="luft", search_mode="lexical")
# combine with facet filters
get_datasets(search="bevölkerung", refine="publisher:Statistisches Amt")
```
### `get_dataset`
Get detailed metadata for a specific dataset.
```
get_dataset(dataset_id="100113")
```
### `get_records`
Query records from a dataset with ODSQL filtering.
```
get_records(dataset_id="100113", where="pm25 > 10", limit=100, order_by="time DESC")
```
### `get_facets`
Get available facet values for filtering.
```
get_facets(facet="publisher") # Options: publisher, keyword, theme, features, modified, language
```
### `export_dataset_url`
Get download URL for dataset export.
```
export_dataset_url(dataset_id="100113", format="csv", where="sensornr=240")
```
Formats: `csv`, `json`, `geojson`, `xlsx`, `shp`, `parquet`, `gpx`, `kml`, `rdfxml`, `jsonld`, `turtle`
TDQS
Scored across 5 tools
Each tool targets a distinct stage: search (get_datasets), metadata (get_dataset), facets (get_facets), records (get_records), and export (export_dataset_url). Minor potential confusion exists between get_datasets and get_facets for discovery, but descriptions clarify their different purposes.
All tools follow a verb_noun pattern, with four using 'get_' and one using 'export_', both being clear verbs. The naming is consistent and predictable across the set.
Five tools is well-scoped for a data portal: search, metadata, facets, records, and export cover the core read workflows without unnecessary bloat.
The set covers the full read lifecycle: discover datasets, understand their structure, query records, and export data. No obvious missing operations for a public read-only open data portal.