Here is how the ten minutes actually splits: two to upload your documents and let them index into a knowledge base, two to import your website alongside them if you want it, a minute to decide who gets access, a minute to publish, and the rest to connect the result in Claude and ask it the questions your team answers by hand every week. No code at any point. What you end up with is an MCP server — a live endpoint any MCP client can query — built from files that were sitting in a shared folder this morning.
Documents are the densest company knowledge you have and the least reachable. The procedures, the rate cards, the spec sheets — they answer real questions precisely, and nobody can find them. Turning them into an MCP server changes how they are consumed without changing a word of them.
Gather the right documents first
The build is fast enough that preparation is the actual work. Pull together the documents that answer questions people actually ask:
- Standard operating procedures and runbooks
- Policies — cancellation, refunds, leave, security, anything with rules in it
- Price lists and rate cards
- Product specs and data sheets
- Onboarding guides and internal FAQs
Skip the aspirational material. A vision deck makes a poor knowledge base. The best candidates are the documents somebody gets asked about weekly.
The ten minutes
Upload the documents
They are indexed into a knowledge base where every answer traces back to the document it came from. Citations are not a nice-to-have; they are how you audit the thing later.
Add your website, optionally
The same knowledge base can hold your crawled site next to your uploads — the crawl takes about two minutes and keeps its own citations. Documents cover what the site does not say; the site covers what the documents assume.
Choose private or public
Private means an internal brain your team signs into and nobody else can reach. Public means anyone with an MCP client can connect — and you can charge per seat if the content warrants it.
Publish
You get an MCP endpoint with OAuth 2.1 authentication already implemented — sign-in, issuer validation, workspace isolation, none of it yours to build or maintain.
Connect it in Claude
Add the server, sign in, and ask it the question you got asked yesterday. Check that the citation points at the right document.
Why this beats pasting files into chats
Pasting a PDF into a conversation works once, for one person, for one chat. A published server is one source everyone queries: the same documents, the same versions, the same cited answers, with access controlled by sign-in rather than by who happens to have the file. And the identical build gives you a chat agent too, if you want a web-facing surface reading from the same knowledge.
The illustrative version
Take a 40-person accounting firm. Engagement procedures, filing calendars, internal review checklists — currently living in a document tree three partners can navigate. Uploaded and published as a private MCP server, the same material answers a junior's question inside Claude in seconds, with a citation to the exact procedure. The office manager stops being the search engine. Nothing was rewritten; it was republished.
Keeping it honest
Documents change. When they do, replace the file and the knowledge base moves with you. Website sources go further: they re-sync on a schedule, as often as every fifteen minutes, so the crawled half of your knowledge tracks the site automatically. And because every answer is cited, stale content is findable instead of invisible — a wrong answer points at the exact document that needs updating.
Plans are in EUR with a seven-day trial. The ten minutes is real, but budget an extra five: the first thing everyone does after connecting is try to catch it out with the trickiest internal question they know, and it is worth watching where the citations land.