Architecture

One MCP endpoint for your entire organization

With KBrain, a Knowledge Manager shares a brain org-wide and every member reaches it through their own personal MCP connection. No connector setup per user, compatible with any MCP client.

Give your whole org one MCP endpoint

Connect via MCP

The usual way to give a whole team access to a tool is painful: every person sets up their own connector, pastes their own credentials, and configures it themselves. KBrain works differently. A Knowledge Manager shares a brain across the organisation once, and every member reaches it through the single MCP connection they already have. One endpoint, org-wide knowledge, zero per-user setup.

The per-user setup problem

When knowledge access is configured per person, every new hire repeats the same setup, every change has to be rolled out to everyone, and no one is sure who has access to what. It does not scale, and it is exactly the friction that stops teams from adopting AI knowledge tools.

The difference - 01

Per-user connectors vs. one org endpoint

Same knowledge, very different amount of setup.

🧩Per-user connector setup

· Every member configures their own connection

· Every new hire repeats the setup

· Changes must be rolled out to everyone

· No clear picture of who has access

setups for
N people

📡One org endpoint

→ A Knowledge Manager shares a brain org-wide

→ Members reach it through their own MCP key

→ Update once, everyone sees the change

→ Access follows org membership

share, seen
by everyone

Share once, reach everyone. Org-shared brains appear in each member’s existing MCP connection - there is nothing new for them to install.

How org-wide sharing works

On Business and Enterprise plans, a company is defined by its verified email domains. Anyone who signs in with a matching address joins the organisation automatically. A Knowledge Manager can then set a brain’s visibility to organization, and it becomes available to every member through the personal MCP connection they already use - no new endpoint, no new credentials.

How it works - 02

One key, every brain you are entitled to

A member’s single MCP connection resolves personal, org-shared, and subscribed brains together.

🔑

One MCP key

Each member has a single personal connection to KBrain.

→

🧠

list_brains

The assistant sees every brain the member is entitled to.

→

🏢

Org-shared brains

Brains a Knowledge Manager shared org-wide appear automatically.

KBRAIN

→

✅

Grounded answer

The assistant queries the right brain and answers.

The endpoint never changes. Share a brain org-wide and it simply shows up for everyone - the same connection, more knowledge behind it.

Compatible with any MCP client

Because it is standard MCP, the org endpoint works in Claude, ChatGPT, and any other MCP-compatible assistant or agent. A member picks the tool they prefer, connects once, and the organisation’s shared knowledge is there - the same brains, whichever client they use.

Give your whole org one MCP endpoint

On Business and Enterprise, a Knowledge Manager shares a brain org-wide and every member reaches it through their own MCP connection - no per-user setup.

Connect via MCP

Frequently asked questions

Does every team member need to set up their own connector?

No. That is the point. A Knowledge Manager shares a brain org-wide once, and every member reaches it through the single personal MCP connection they already have. There is no per-user connector setup and nothing new to install when a brain is shared.

How does KBrain know who is in my organization?

On Business and Enterprise plans, an organisation is keyed on one or more verified email domains. Anyone who signs in with a matching email address joins automatically, so membership - and therefore access to org-shared brains - follows your company domain.

Who can share a brain across the organization?

Owners and Knowledge Managers can set a brain’s visibility to organization. On Business plans there is a set number of Knowledge Manager seats; on Enterprise every member is a Knowledge Manager by default. Plain members can query org-shared brains but keep their own brains private.

Does the org endpoint work in both Claude and ChatGPT?

Yes. It is standard MCP, so the same connection works in Claude, ChatGPT, and any other MCP-compatible client. Members use whichever assistant they prefer and see the same org-shared brains.