SB OGC MCP — Studio Bereikbaar Mobility Data for Claude
MCP server that gives Claude access to Dutch mobility data via Studio Bereikbaar's OGC API.
What you get
13 tools for Claude Desktop:
| Tool | What it does |
|---|---|
list_collections |
List 15 data collections (boundaries, NRM networks, demographics) |
describe_collection |
Get schema/properties of a collection |
list_processes |
List 7 analysis processes |
get_features |
Fetch GeoJSON features with filters |
search_boundaries |
Find gemeente/wijk/buurt/pc4 by name |
run_odin_query |
ODIN travel survey analysis (20 years, modal split, trends) |
run_odin_compare |
Compare two locations side-by-side |
run_modal_split |
Generate modal split chart (returns PNG image) |
run_odin_spider |
Origin-destination desire lines (GeoJSON) |
run_odin_profile |
7-cluster mobility profiling |
run_odin_spider_profile |
Demographics of travelers to/from a municipality |
run_accessibility_map |
BOP accessibility map (returns PNG image) |
Setup voor collega's
1. Installeer uv (eenmalig)
curl -LsSf https://astral.sh/uv/install.sh | sh
2. Configureer Claude Desktop
Open ~/Library/Application Support/Claude/claude_desktop_config.json en voeg toe:
{
"mcpServers": {
"sb-ogc-api": {
"command": "uvx",
"args": ["sb-ogc-mcp"]
}
}
}
3. Herstart Claude Desktop
De tools verschijnen automatisch. Probeer:
"Welke data collections heeft Studio Bereikbaar?"
"Laat de modal split zien voor Amsterdam"
"Vergelijk Rotterdam en Utrecht qua vervoerswijzen"
"Toon de bereikbaarheidskaart voor fietsen naar supermarkten in Den Haag"
Data
All data comes from tools.studiobereikbaar.nl/oapi (OGC API):
- ODIN — CBS travel survey, 20 years (2004–2023), ~3M trips, enriched by Roland Kager
- NRM — National traffic model networks (2022 + 4 future scenarios)
- CBS boundaries — gemeente, wijk, buurt, pc4, provincie
- BOP — accessibility maps (Move Mobility)
- V500 — 500m population + urbanization grids
Metadata
Release files for sb-ogc-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sb_ogc_mcp-0.1.1.tar.gz | 44.6 kB | Without provenance | Details for sb_ogc_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sb_ogc_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for sb_ogc_mcp-0.1.1-py3-none-any.whl |
Total release size: 52.7 kB
Release files / sb_ogc_mcp-0.1.1.tar.gz
| Download URL | sb_ogc_mcp-0.1.1.tar.gz |
|---|---|
| Size | 44.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55383c385a5a2301d70e9e10ae1bf293880663091d7711b00183da1711f43316
|
|
BLAKE2b-256 checksum How to use checksums |
251eba8b59a0626f97524c5453d4e2cd8bf5b95b041bfaf98296685e98cde33e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.14
|
Release files / sb_ogc_mcp-0.1.1-py3-none-any.whl
| Download URL | sb_ogc_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4da15cd147292d4c484ec5b45dbf44b92ec408b0d081b776f5f3b6a30c1c6da0
|
|
BLAKE2b-256 checksum How to use checksums |
16d37ef73632bce7a7110fe4c705d8050f06cde284fad69e9b39f86f9f4745b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.14
|
Security for sb-ogc-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.