EnduraDocs iiRDS MCP Server

cableModel Context Protocol · Streamable HTTP

Bring your iiRDS documentation to AI agents

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.

terminal claude mcp add --transport http enduradocs-iirds https://mcp.iirds.enduradocs.dev

descriptionRead the docs

verified_userOAuth 2.1 swap_horizPassthrough auth descriptioniiRDS content lockNothing stored

mcp.iirds.enduradocs.dev

smart_toy

Agent

hub

MCP

dns

Request API

Auth mode

oauth + passthrough

Health

GET /health

bolttools/call → iirds.search

How it works

One endpoint between your agent and your docs

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.

smart_toy

Claude / agent

MCP client

OAuth 2.1

hub

iiRDS MCP Server

stateless adapter

forwarded token

dns

Request API

+ iiRDS archives

Point your client at the URL

One HTTPS endpoint. No SDK, no wrapper — just the server address.

It authenticates the caller

It advertises OAuth 2.1 discovery metadata, so a spec-compliant client finds the authorization server and registers itself.

Calls proxy under your auth

Your token is forwarded as-is. The Request API is the sole authority on access.

iiRDS topics returned

The agent reads real, versioned documentation — scoped to what you allow.

Connect

Point any MCP client at one URL

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.

Claude Code

$ claude mcp add --transport http enduradocs-iirds https://mcp.iirds.enduradocs.dev

✓ Added MCP server "iirds" (transport: http)

discovering OAuth 2.1 metadata … ok

client registered · authorized ▋

Works with any spec-compliant client

terminalClaude Code desktop_windowsClaude Desktop travel_exploremcp-inspector

Authorization server

https://auth.enduradocs.dev/realms/request-api

If a client can't self-register, this deployment uses a pre-registered client instead — see the DEVELOPMENT.md walkthrough.

Bearer token

Each request carries 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.

In the agent

Answers grounded in your real documentation

No hallucinated manuals. The agent retrieves the exact iiRDS topic, revision and all, and cites it. The exchange below is an illustration.

smart_toyClaude · connected to iirds example exchange

What's the gear-oil change interval for the Series 400 gearbox?

bolttools/call · iirds.search "Series 400 gearbox oil change interval"

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.▋

descriptioniiRDS topic · Series 400 → Maintenance → Lubrication · rev v3.2

Authorization

Three ways in — you stay in control

The iiRDS Request API is the sole authority on what each caller may see. This deployment accepts the paths shown below.

Auto

verified_user

OAuth 2.1

Zero-config for spec-compliant clients. The endpoint advertises discovery metadata; the client obtains and carries its own token. Tokens are validated against the authorization server before being forwarded.

key

Bearer token

Send Authorization: Bearer and it's forwarded as-is. The Request API accepts its own API tokens here — see its info page.

Invite

fingerprint

DID proof-JWT

A self-generated Ed25519 keypair (did:jwk). Sign each request fresh — but the operator must first authorize which archives you may see; there is no self-serve registration.

Who it's for

One adapter, three teams served

code

Developers

Wire an agent to real iiRDS docs in one command. Standard MCP — no bespoke integration to maintain.

edit_document

Technical writers

Your published iiRDS packages become answerable by AI — the content you authored, delivered verbatim with its revision.

admin_panel_settings

Documentation managers

AI answers stay scoped to what you authorize, versioned, and auditable. Nothing is copied or cached in the adapter.

Reference

Everything a client needs

The full tool catalogue and auth model live in the project documentation.

favoriteRun the health check

MCP endpointhttps://mcp.iirds.enduradocs.dev

TransportStreamable HTTP

Auth modeoauth + passthrough

Health checkGET /health

UpstreamiiRDS Request API

FAQ

Common questions

helpIs anything stored on this server?expand_more

No. It's a stateless adapter. Every tool call is proxied upstream under your own authorization — nothing is persisted or reasoned about here.

helpWhich clients work?expand_more

Any spec-compliant MCP client — Claude Desktop, Claude Code, and mcp-inspector among them. It only needs the server URL.

helpHow do I get a DID authorized?expand_more

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.

helpWhat is iiRDS?expand_more

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.

Ready to connect your documentation?

One command and your agent is reading real, versioned iiRDS content.

open_in_newProject documentation

Running a client locally over stdio instead? See the config-file quick-start.