Think inside your AI world.

GitBook through Unl

Published pages, read straight from the site GitBook already serves, then checked against the currency rule you actually ratified.

GitBook through Unl reads published-docs content against the currency criteria you have ratified, so 'is this page still accurate' comes back current, not confirmed, with the condition it hasn't met.

What GitBook holds

GitBook through Unl reads what the published site already serves:

  • Reads content directly from a published GitBook site's own MCP server, created automatically at publish time
  • Returns read-only access to pages, sections and spaces as they currently stand live
  • Answers a direct question against the published content, not a cached copy
  • Reflects updates as soon as the site is republished, with no separate sync step

What the naked read gives you

Ask GitBook's own published-docs MCP server what a page currently says and it reads the live site directly: the same content a visitor would see right now, no caching lag, no stale export. For a straight 'what does the page say' question, that's exactly the right answer.

The frame judges the data it is given; it does not verify the source’s accuracy.

What changes when GitBook is read measured

A docs lead ratified that a page only counts as current if it was republished after the feature's last shipped change, because a pricing page once sat two versions behind the product for a month before a customer caught it.

'Is this page still accurate?' returns, measured: current, not confirmed, because GitBook's own read shows the page live and unchanged, but the page content alone doesn't show a republish date after the feature's last shipped change, which the ratified rule requires. GitBook supplied the live page read; your ratified rule supplied the republish condition.

And back again

That gap stays visible rather than getting lost in a chat thread — Unl keeps the page read and the unmet republish condition side by side, so anyone asking about that page later inherits the same open item instead of starting the check over.

The answer comes back measured against what you already decided, and why.

The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Questions people ask

What confirms a page instead of leaving it current, not confirmed?

A republish timestamp logged after the feature's last shipped change. Once that timestamp exists and GitBook's live read shows it, the same question returns confirmed - the currency rule hasn't changed, the publish record has.

How do I connect GitBook to Claude?

Every published GitBook site exposes its own read-only MCP server automatically; add its endpoint as an MCP connector in Claude Code or Claude Desktop, or connect GitBook's own MCP server from your workspace for API-level access. Either way, its docs-reading tools become a source Unl can query.

Does Unl change anything in my GitBook site?

No. The published-docs connection is read-only by GitBook's own design - nothing is edited, republished or restructured as a result of a measured answer.

What this is

Think inside your AI world — you stay in command

Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.

It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.

Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:

Alpha is invite-only · free at launch.