A thin Model Context Protocol adapter that exposes your hosted iiRDS archives to Claude and any spec-compliant agent. Every tool call is proxied to the EnduraDocs Request API under the caller's own authorization — nothing is stored, nothing is reasoned about here.
The server holds no state and makes no decisions of its own. It forwards each tool call upstream under your token and streams iiRDS content straight back — the Request API decides what you may see.
One HTTPS endpoint. No SDK, no wrapper — just the server address.
It advertises OAuth 2.1 discovery metadata, so a spec-compliant client finds the authorization server and registers itself.
Your token is forwarded as-is. The Request API is the sole authority on access.
The agent reads real, versioned documentation — scoped to what you allow.
Add the endpoint to any spec-compliant client — no SDK to install. How the client proves who it is depends on how this deployment is configured.
If a client can't self-register, this deployment uses a pre-registered client instead — see the DEVELOPMENT.md walkthrough.
Authorization: Bearer, forwarded verbatim to the Request API.See the Request API info page for its full auth model: http://iirds.iirds.svc.cluster.local:3500.
No hallucinated manuals. The agent retrieves the exact iiRDS topic, revision and all, and cites it. The exchange below is an illustration.
Change the gear oil every 2,000 operating hours or 12 months, whichever comes first. Use ISO VG 220 mineral oil; capacity is 4.2 L.▋
Wire an agent to real iiRDS docs in one command. Standard MCP — no bespoke integration to maintain.
Your published iiRDS packages become answerable by AI — the content you authored, delivered verbatim with its revision.
AI answers stay scoped to what you authorize, versioned, and auditable. Nothing is copied or cached in the adapter.
Every tool this deployment registers is listed below. The auth model lives in the project documentation.
favoriteRun the health checkoauth + passthroughValidate the configured identity against the iiRDS Request API and list the archives (resource URIs) this identity is authorized to read.
Return the iiRDS core vocabulary (schema) as JSON-LD — the classes and properties of the iiRDS ontology. Use this to ground yourself in the terms returned by the other tools.
List the root directory nodes (top of the navigation tree) across the authorized archives, as JSON-LD. Use this to start browsing the structure of the documentation.
List documentation metadata facets (product and functional metadata) across the authorized archives, as JSON-LD.
List iiRDS information types and subjects (facets used to classify topics and documents) across the authorized archives, as JSON-LD.
Browse iiRDS information units (documents, topics, fragments, packages) across the authorized archives. Returns a compact summary ({ iri, type, title }) by default; set raw=true for the full JSON-LD. Tip: pass a concrete `type` (document/topic/fragment/package) — listing every information unit is significantly slower on large archives.
Run a structured, filtered query over the authorized iiRDS archives. Filter by rdf:type (e.g. "iirds:Topic") and/or property conditions (a path like "iirds:title" with an operator eq/neq/gt/lt and a value). Returns a compact { iri, type, title } summary by default; set raw=true for the full JSON-LD. Provide at least a type or one filter.
Fetch and read the body of an information unit's rendition. HTML/XHTML is returned as Markdown, PDF as extracted text, other text as-is — inlined for reading, with long documents paged via `offset`. Requires the unit IRI and the rendition MIME type (from the unit's iirds:has-rendition / iirds:format, e.g. application/xhtml+xml or application/pdf).
Get an iiRDS package (a container, not a readable document). Returns guidance for browsing the package plus a resource link to download the raw container ZIP on demand — the ZIP is never inlined. To read a package, list its information units and call get_rendition_content on a unit's rendition.
No. It's a stateless adapter. Every tool call is proxied upstream under your own authorization — nothing is persisted or reasoned about here.
Any spec-compliant MCP client — Claude Desktop, Claude Code, and mcp-inspector among them. It only needs the server URL.
Generate an Ed25519 keypair (did:jwk) yourself, then contact the deployment operator — they issue a one-time registration token naming which archives you may see. There is no self-serve DID registration.
The intelligent information Request and Delivery Standard — an open standard for packaging and delivering technical documentation with rich metadata. It's what EnduraDocs publishes and this server exposes.
One command and your agent is reading real, versioned iiRDS content.
Running a client locally over stdio instead? See the config-file quick-start.