vnbdigital-mcp
MCP server for accessing the vnbdigital.de database of German distribution grid operators (Verteilnetzbetreiber, VNB).
Built on top of the vnbdigital-client library, which also ships a standalone CLI and can be used directly as a Python library in your own code. This repository adds an MCP interface on top, making the data available to AI assistants and agents via the Model Context Protocol (MCP).
Looking for the Python library or CLI? Head over to vnbdigital-client.
Tools
vnbdigital.de lookups
| Tool | Description |
|---|---|
get_operator |
Basic master data for an operator by BDEW code or vnbdigital ID |
get_operator_details |
Full details including services, documents and logo |
get_operators |
Batch lookup for up to 50 IDs in a single call |
search |
Free-text search (postcode, name, city, region) |
search_by_coordinates |
Find responsible operators for a GPS coordinate (lat/lon) |
search_by_postcode |
Find responsible operators for a German postcode |
get_nsp_operator |
Low-voltage (Niederspannung) operator for a postcode or coordinate |
get_msp_operator |
Medium-voltage (Mittelspannung) operator for a postcode or coordinate |
BDEW register lookups (bdew-codes.de)
| Tool | Description |
|---|---|
bdew_lookup_by_company_code |
Look up a company by its 6–7 digit BDEW CompanyUId |
bdew_lookup_by_market_code |
Look up a company by a 13-digit BDEW market function code |
bdew_get_market_function_detail |
Fetch address and contact details for a market function entry |
Note: Company names in the BDEW register do not always match those on vnbdigital.de. Use both sources together for cross-referencing.
Installation
Prerequisites
- Python ≥ 3.12
- uv
Install dependencies
uv sync
Start the server (development)
uv run vnbdigital-mcp
# or
uv run python -m vnbdigital_mcp.server
Test with MCP Inspector
uv run mcp dev src/vnbdigital_mcp/server.py
Configuration in VS Code / Claude Desktop
Add the server to your MCP configuration (.vscode/mcp.json or claude_desktop_config.json):
Install from PyPI (recommended):
{
"servers": {
"vnbdigital": {
"command": "bash",
"args": [
"-l",
"-c",
"uvx vnbdigital-mcp"
]
}
}
}
Install from GitHub (latest unreleased):
{
"servers": {
"vnbdigital": {
"command": "bash",
"args": [
"-l",
"-c",
"uvx --from git+https://github.com/the78mole/vnbdigital-mcp.git vnbdigital-mcp"
]
}
}
}
Local development (workspace checkout):
{
"servers": {
"vnbdigital": {
"command": "bash",
"args": [
"-l",
"-c",
"uv --directory ${workspaceFolder} run vnbdigital-mcp"
]
}
}
}
Note:
bash -lloads the login shell profile, which ensuresuvx/uvare found in~/.local/binwithout any additionalenvconfiguration.
Environment Variables
| Variable | Default | Description |
|---|---|---|
VNBDIGITAL_API_URL |
https://www.vnbdigital.de/gateway/graphql |
GraphQL endpoint |
VNBDIGITAL_TIMEOUT |
30 |
HTTP timeout in seconds |
BDEW_LOOKUP_URL |
https://bdew-codes.de |
Base URL for BDEW lookups |
Example Queries
Operator by ID
Known example IDs:
- 179 → ESTW - Erlanger Stadtwerke AG
- 180 → Stadtwerke Eschwege GmbH
- 99 → Stadtwerke Bramsche GmbH
Operators for a location
get_nsp_operator and get_msp_operator accept either a 5-digit postcode
or a "lat,lon" coordinate string:
get_nsp_operator("97816") # by postcode
get_nsp_operator("49.998037,9.58033") # by coordinates
BDEW lookup
bdew_lookup_by_company_code(660188) # → A&A Stromallianz GmbH
bdew_lookup_by_market_code("9903445000000") # → same company, one market function
bdew_get_market_function_detail(141) # → address/contact for that market function
Local Development
# Set up project environment
uv sync
# Linting & formatting
uv run ruff format .
uv run ruff check --fix .
# Tests
uv run pytest
Related Projects
| Project | Description |
|---|---|
| vnbdigital-client | Python client library this MCP server is built on. Provides typed access to the vnbdigital.de GraphQL API and the BDEW register. |
| vnbdigital.de | Official database of German distribution grid operators. |
| bdew-codes.de | BDEW market participant register with company and market function codes. |
License
MIT
Metadata
Release files for vnbdigital-mcp 0.8.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vnbdigital_mcp-0.8.6.tar.gz | 94.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vnbdigital_mcp-0.8.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.6 kB
Release files / vnbdigital_mcp-0.8.6.tar.gz
| Download URL | vnbdigital_mcp-0.8.6.tar.gz |
|---|---|
| Size | 94.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbd8ea560f7b4cc4ab82c896aafdfd396b1bbc40a65dcf239b72a745068d0bf6
|
|
BLAKE2b-256 checksum How to use checksums |
5fbdeedcdda7ab261f7355bcd44349e71f60ea5979577dcc9d69f9ee62ad26bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / vnbdigital_mcp-0.8.6-py3-none-any.whl
| Download URL | vnbdigital_mcp-0.8.6-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
858cf56397644f6186c4eeaad89284093b35071fcde14dc894799156f162a5ad
|
|
BLAKE2b-256 checksum How to use checksums |
452ae0259a28285786dec18ff5afe85bee9fa1adb47783527c06993b2f152090
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log