Station (c)
rete-demo.mcpb is a packaged
Model Context Protocol
extension. Installing it puts the whole engine — the same WebAssembly build
the console runs — inside an MCP-capable assistant, with eighteen tools over the
published catalogue, the three graphs of this demonstration among it. Enabling it is one toggle; after that a
question in plain language is answered from the graph.
Nothing is uploaded and nothing is downloaded whole: the assistant reads the same byte ranges over HTTP that everything else here reads, on your machine.
Four steps, no configuration.
The button above saves rete-demo.mcpb. A
.mcpb is a signed-shaped zip carrying one server file and
the WebAssembly engine — nothing is fetched at install time.
In Claude Desktop: Settings → Extensions → Advanced settings → Install extension…, then pick the downloaded file.
It then appears wherever your host lists connectors, as rete — knowledge graphs. Leave Graph folders empty: the published graphs need no local files.
Try “Use rete to list the datasets you can reach”, then “Which organizations relate to the sdsc-ordes/gimie repository?”
sdsc-ordes/gimie, it resolves ownership
(org:unitOf → Swiss Data Science Center, ROR
02hdt9m26) and the affiliations of nine contributors —
flagging the identifier inconsistencies it meets on the way.
Run SPARQL calls against the remote file, each one visible.
The agent reads the card first to learn the vocabulary — which is what
stops a model inventing predicate names.
Its published catalogue holds 104 graphs, the three the paper names among
them, and it opens any other published .rete URL it is given.
| Key | Triples | File | Licence |
|---|---|---|---|
| crossref | 8,271,040,725 | 66.4 GB | CC0-1.0 |
| zenodo-records | 215,396,999 | 2.09 GB | CC-BY-4.0 |
| open-pulse | 3,697,829 | 50.2 MB | GitHub metadata · ontology © SDSC-ORDES |
It also reads every .rete in folders you grant it. This is the
extension each release of
github.com/caviri/rete ships.
Every graph is read lazily, and every query result reports the bytes and requests it actually spent.
list_datasetsReachable graphs: your local files and the published cataloguedataset_cardA graph's embedded self-description: what it is, licence, provenance, identity, countsdataset_schemaClasses and relations with counts, from the file's baked schema pyramidexample_queriesRunnable SPARQL the dataset ships withsparql_querySPARQL 1.1, optionally with OWL 2 QL reasoning; a slow query comes back as a job instead of timing outstart_queryStart a slow SPARQL query in the background and get its job idquery_statusWait for a query job and see its progress; the first rows once donequery_resultPage through a query's rows, or save them all to a CSV/TSV/JSON filecancel_queryStop a running query jobfind_entitiesResolve a name to entity IRIs by label prefix and full textdescribe_entityEvery statement about one IRI, in both directionsvalidate_shaclValidate SHACL Core shapes against a graphbuild_reteBuild a new .rete from RDF text, offline (needs a granted folder)load_rdfQuery RDF shared in the chat: its text becomes a graph held in memorygraph_viewShow query results or an entity's neighbourhood as an interactive graph and table in the chatgraph_view_updateChange an open graph view: add results, expand, highlight, labels, layers, layoutgraph_view_stateWhat the user selected and set in a graph viewaboutThe extension's version and build, credits, how to cite it, and links
A .mcpb is a zip. If your MCP host takes a plain stdio command
instead of a bundle, unpack it and point at the server directly.
unzip rete-demo.mcpb -d rete-demo node rete-demo/server/index.mjs # speaks MCP over stdio # or wire it into any MCP client config: # "command": "node", # "args": ["/abs/path/rete-demo/server/index.mjs"]
The server is a bundled ESM file and its query worker plus a 6.3 MB
.wasm; no
node_modules, no network access at start-up.