Documentation

Tools

Connect MCP clients to the portal's research through the knowledge box connector.

The knowledge box MCP connector#

Tools hosts the portal's MCP connector. It gives any MCP-capable client - an agent framework, an IDE assistant, a desktop research tool - read-only access to this portal's knowledge. A connected client can:

  • Search the corpus - the same retrieval the portal itself uses.
  • Ask for cited answers - grounded answers that carry their sources.
  • Fetch a document - pull a specific resource's content.
  • Browse the catalogue - list what the portal holds.

Access stays inside the portal boundary: a key reaches only this portal, never the knowledge box behind it.

Connect a client#

  1. On Tools, enter a label naming the client or workflow that will use the key (for example, analyst desktop) and choose Create key. Creating and revoking keys needs a signed-in administrator.
  2. The new key appears once, inside a ready-to-paste client configuration. Copy the configuration straight away - the key is not shown again after you leave or refresh the page.
  3. Paste the configuration into any client that accepts JSON MCP server configuration. The portal's tools then appear in that client.

Connecting manually#

For a client configured field by field rather than by pasting JSON, use Streamable HTTP against the portal's MCP endpoint and send the key as a bearer token on every request:

Endpoint URL   https://<portal domain>/api/t/<portal>/mcp
Header         Authorization: Bearer <your key>

The same connection in JSON form:

{
  "mcpServers": {
    "<portal>-knowledge": {
      "type": "streamable-http",
      "url": "https://<portal domain>/api/t/<portal>/mcp",
      "headers": { "Authorization": "Bearer <your key>" }
    }
  }
}

Keys and security#

  • The connector is read-only - no client can change the corpus through it.
  • Each key is limited to this portal and can be revoked at any time from Tools; clients using it stop working immediately, and nothing else changes.
  • The knowledge box credential stays private: the connector issues its own separate, revocable CorpusKit keys and never reveals the service credential CorpusKit uses to reach the knowledge box.