Two tools cover the whole surface — ask, and search — but the second half of the value points the other way: every question that arrives is recorded, so you can see what people are asking your docs and where the answers run out. The only real decision is deployment: managed, self-hosted from a template, or added to a server you already operate.
Inkeep's MCP server puts your knowledge base behind two tools — one that answers a question from it, one that searches it — and any MCP client can call them.
- A question-answering tool that returns a direct answer drawn from your knowledge base
- A search tool that returns the relevant passages when you would rather read the source
- Tool names generated from your product, so a client with several servers connected can tell them apart
- Every interaction logged to your analytics, with a session-level breakdown of what was asked and how it was answered
- Three ways to run it: the managed server, an open-source template you deploy yourself, or the same tool implementations folded into a server you already run
An Inkeep project with a knowledge base, and an MCP Assistant created in the dashboard to get the server URL. Clients that do not speak Streamable HTTP connect through the mcp-remote bridge.
One command plus a key — uvx inkeep-mcp-server, then supply credentials