cimmcp: an MCP server that lets an LLM chat look up, validate and query ENTSO-E CGMES and NC models
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cimoxide-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# cimoxide-mcp `cimmcp` is a [Model Context Protocol](https://modelcontextprotocol.io) server for ENTSO-E **CGMES** and **Network Code** RDF/XML, built on [cimoxide](https://github.com/m-mirz/cimoxide). It lets an LLM chat answer questions about a model: which generators a model has and their set points, why an object fails validation, what a CIM class or attribute means. Its tools read; `export` and `edit` write a file, inside the workspace, over an existing one only when told to and never over a model set's own files: | Tool | | |---|---| | `list_model_sets` | directories holding CIM files, with each file's profiles | | `summary` | a model set's files, model headers and object counts by class | | `find_objects` | search by class (abstract classes included), name/mRID text and attribute value | | `get_object` | one object's fields, references resolved, what references it, and the files that define or describe it | | `validate` | the ENTSO-E SHACL and SPARQL rules, as `cimcli validate` runs them | | `conflicts` | objects more than one file defines, and objects the files type with unrelated classes | | `sparql` | a SPARQL query over the merged CGMES data | | `export` | one profile (CGMES or NC) or the whole set as RDF/XML, as `to_xml_for_profile` / `to_xml` write it; or every decoded object as JSON | | `edit` | update, copy, create and delete objects, and write the result as `export` does | | `describe_class` | definitions of classes, attributes and enumerations from the ENTSO-E vocabulary | A model set is every CIM XML file in one directory (`path`), or the files and directories listed in `files`, for a model whose files lie apart (an IGM with its boundary and common data). `--dir <path>` (else `CIMOXIDE_MODEL_DIR`, else the working directory) is where relative paths resolve. ## Install With [uv](https://docs.astral.sh/uv/), nothing needs installing first; clients start it as ``` uvx --from cimoxide-mcp cimmcp --dir /path/to/models ``` or install it once wi…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.