The Lightbits Reader MCP Server is now live at documentation.lightbitslabs.com/mcp
Something has quietly changed about how our customers work. Open a terminal against a Lightbits cluster today and there is a good chance an AI assistant is open beside it – Claude, Cursor, GitHub Copilot, or an agent your platform team built in-house. It is helping draft your Ansible inventories, your StorageClass manifests, and your lbcli one-liners.
There has always been a catch. Your assistant knows Linux and Kubernetes extremely well. It does not know Lightbits – not the way our documentation knows Lightbits. So it does what language models do when a detail is missing: it produces something plausible. A flag that does not exist. A procedure from a release you are not running. You catch it, you open the documentation portal, you copy the right passage back into the chat, and you carry on.
We decided to close that gap at the source.
The Reader MCP Server is live
The Lightbits Documentation Library now exposes a Reader MCP Server at https://documentation.lightbitslabs.com/mcp. Any MCP-compatible AI agent can connect to it and search our published documentation directly – no API key, no account, no scraping, and nothing to install.
A one-minute primer on MCP
The Model Context Protocol (MCP) is an open standard for connecting AI agents to external systems. Before it existed, every tool that wanted to be usable by an assistant had to build a bespoke integration for every client. MCP replaces that with a single contract: a server advertises the tools it offers, and any compliant client can call them.
Our Reader server advertises one tool, search. Your agent sends a question in plain language. The server returns the most relevant passages from our documentation, each carrying its page title and a link back to the source. The agent then answers you from that material rather than from its own recollection.
That last part is the whole point. The difference between an assistant that guesses at Lightbits behavior and one that quotes our documentation – with a link you can click to verify – is the difference between a suggestion and an answer.
Connecting takes about a minute
Most MCP clients read a small JSON configuration file. Add one entry:
That is the entire setup. Restart your client and the Lightbits documentation becomes a tool your agent can reach whenever a question calls for it. The same entry works across Claude, Cursor, VS Code, Codex, and anything else that speaks MCP. Clients that ask you to choose a transport should be set to Streamable HTTP.
How it fits together
The flow is deliberately simple. Your agent stays in your environment. When a question needs product knowledge, it sends a search query over HTTPS to the /mcp endpoint on our documentation site. The endpoint runs that query across our published library – Private Cloud, CLI Reference, Plug-ins and CSI, Metrics and Events, Release Notes and Support Guides – and returns ranked excerpts with their source links. Nothing is installed, nothing is synchronized, and nothing goes stale: the moment we publish an update, your agent sees it.
What it looks like in practice
Questions our customers ask their assistants every week now have grounded answers:
- Which internal ports have to be open between cluster nodes?
- Show me the lbcli commands to create a QoS policy and attach it to an existing volume.
- How do I install the CSI plugin on OpenShift using Helm?
- A drive is showing Rebuilding. What is happening, and what should I do next?
Each answer arrives with the pages it was drawn from, so verification is one click rather than another search. For a platform engineer wiring Lightbits into Kubernetes, that means the manifest their assistant produces is anchored to our CSI documentation instead of to a plausible-looking guess.
What it deliberately does not do
- It is read-only. The server can search documentation. It cannot modify it, and it has no connection whatsoever to your cluster, your management API, or your data.
- It covers published documentation only – the same content available on our public documentation site. Nothing internal is exposed.
- It requires no credentials, which also means it holds none of yours.
One practical note: the text of your query is sent to our documentation site to be answered, exactly as a search box query would. Treat it accordingly, and keep cluster identifiers, addresses, and customer data out of the questions you send.
Why we enabled it
Documentation is only valuable when someone needs it. For years that moment meant opening a browser tab and searching. Increasingly it means asking the assistant that is already open.
We would rather our documentation be present when that happens. Making the library reachable by agents is a small change in mechanics and a large change in outcome: fewer invented flags, fewer procedures from the wrong release, less time spent shuttling text between a browser and a chat window – and better questions arriving at our support desk, because the person asking has already been pointed at the right page.
It also reflects how we think about documentation generally. The Lightbits Documentation Library is not a PDF archive. It is a maintained, structured product surface, and opening an interface onto it was the natural next step. The Reader MCP capability itself comes from DeveloperHub, the platform our documentation runs on; we enabled it for the Lightbits Documentation Library and shaped what it covers.
Try it, and tell us how it goes
Add the entry, restart your client, and ask your assistant something you would normally look up by hand. If an answer comes back thin or points at the wrong page, that is useful signal – it usually means a page needs clearer structure, and we want to know.
| If you bookmark one address, make it documentation.lightbitslabs.com – and now, for your agent, documentation.lightbitslabs.com/mcp |
Questions, or a gap you would like closed? Reach us through the Lightbits support portal, or send feedback straight to the documentation team. We read all of it.