kbrain

KBrain Concepts

How to connect a knowledge base to Claude via MCP

A step-by-step look at connecting an external knowledge source to Claude with MCP, and what changes once you do.

Connect your knowledge over MCP

Connect via MCP

To connect a knowledge base to Claude with MCP, you add the knowledge source as an MCP connector in Claude's settings, using the endpoint your provider gives you. Once connected, Claude can query that source directly during a conversation, with nothing to paste or upload.

What MCP actually does here

The Model Context Protocol is an open standard that lets AI assistants call external tools and data sources during a conversation. For a knowledge base, that means Claude can send a query to your connected source, a document set, a database, or a curated brain, and get back the relevant passage in real time as part of answering your question.

Without MCP, the alternatives are manual: paste the content, upload a file, or maintain a Claude Project. MCP replaces that manual step with a live connection.

The general setup

The exact screens change as Claude's interface evolves, but the shape of the process stays the same.

Setup - 01
From endpoint to grounded answer
A few steps to connect, then Claude retrieves on every relevant question.
🔗
Get the endpoint
Your provider issues an MCP URL.
⚙️
Add the connector
Paste it into Claude's settings.
🔓
Authorize
Grant access for private sources.
💬
Ask normally
A question the source covers.
Grounded answer
Retrieved, not inferred.
LIVE
Connect once, query always. After setup, Claude retrieves from the source on every question it covers, with no re-pasting and no re-uploading.
  • Get the MCP endpoint from your knowledge provider. With KBrain, the endpoint is generated automatically when you create or subscribe to a brain.
  • Add it as a connector in Claude's settings, under connected MCP servers or connectors.
  • Authorize the connection if the source requires it. Private brains usually do, marketplace brains may not.
  • Query normally. Ask something the connected knowledge covers, and Claude retrieves from the source while it answers instead of leaning on training data alone.

What changes once it is connected

  • No more re-pasting. The knowledge persists across every conversation, not just the one where you uploaded a file.
  • Retrieval, not context-stuffing. Claude pulls the specific relevant passage instead of you loading a whole document into the chat.
  • One connection, current knowledge. When the underlying source updates, a synced folder or a maintained brain, Claude sees it on the next query with nothing to re-upload.

Common issues

  • Claude does not seem to use the connected knowledge. Check that the connector is enabled for the conversation. Some Claude interfaces require you to toggle connectors on per chat, not just connect them globally.
  • The connection needs authorization you do not have. Private brains are scoped to whoever created them. To query someone else's private brain you have to be granted access first. That is by design.
  • Answers still read generic. Confirm the question falls within what the connected brain covers. MCP retrieval only helps where the source has an answer. Outside that scope, Claude falls back to its own reasoning.

A connected source only helps on questions it actually covers. Scope each brain to a clear domain so retrieval stays precise.

Connect your knowledge over MCP

Create or subscribe to a brain on KBrain, then connect its MCP endpoint to Claude, ChatGPT, or any MCP compatible assistant in a few minutes.

Connect via MCP

Frequently asked questions

Does connecting an MCP knowledge base slow Claude down?

There is a small latency cost for the retrieval step, like any tool call. In exchange you get an answer grounded in the connected source instead of an inferred one, which is worth it whenever accuracy matters.

Can I connect more than one knowledge source to Claude at once?

Yes. Claude can have multiple MCP connectors active and uses whichever is relevant to the query. Too many overlapping sources can make retrieval less precise, so scope each connector to a clear domain.

Is this the same setup in Claude Desktop and Claude web?

The protocol is the same, but where you configure connectors differs by client. Check the current settings menu in whichever Claude client you use, desktop, web, or mobile, since this has changed as MCP support matured.