Connect to the Knowledge Substrate.

Paste this into your assistant

Add Corvair Knowledge Substrate to your assistant with one address. "Connector", "app", "plugin" and "MCP server" all mean the same thing here: the Model Context Protocol (MCP) is the open standard AI assistants use to reach outside services.

Choose your assistant

"Tested by Corvair" means Corvair has connected that assistant and used it. Other guides follow the vendor's own instructions, which can change.

Claude

1. In Claude, open Settings, then Connectors, and choose Add custom connector.
2. Name it Corvair Knowledge Substrate and paste the address above. Leave the advanced settings empty.
3. Choose Connect. A Knowledge Substrate sign-in page opens: sign in and choose the permissions to grant.
4. In a chat, turn the connector on from the tools menu.

In Claude Code, add it from a terminal:

claude mcp add --transport http corvair-cks https://cks.corvair.ai/mcp

Codex

Not yet tested Corvair has not connected Codex to the Knowledge Substrate. These steps follow Codex's own public instructions, which can change: Codex documentation.

The command line, the desktop app and the IDE extension share one list of servers, so add it once. From a terminal:

1. Add the server: run the first command below.
2. Sign in: run the second command. A Knowledge Substrate sign-in page opens in your browser: sign in and choose the permissions to grant. On a machine with no browser, add --no-browser, open the address it prints, sign in, and paste the full address you land on back into the terminal.
3. Check it: run codex mcp list, or type /mcp in the codex terminal screen.

codex mcp add corvair-cks --url https://cks.corvair.ai/mcp
codex mcp login corvair-cks

In the desktop app, open Settings, then MCP servers, and choose Add server. In the IDE extension, open the gear menu, then MCP servers, and choose Add server. In either, enter the name corvair-cks, choose Streamable HTTP, enter the address above, save, and restart. Then choose Authenticate in the server list.

ChatGPT

Not yet tested Corvair has not connected ChatGPT to the Knowledge Substrate. These steps follow ChatGPT's own public instructions, which can change: ChatGPT documentation. The ChatGPT instructions have been reorganised more than once, so the menu names may differ from what you see. Which plans and workspaces can add a custom server is set by OpenAI and, in a workspace, by its administrator.

1. In ChatGPT, open the Plugins page (chatgpt.com/plugins), choose the plus button, and choose Add custom MCP server.
2. Name it Corvair Knowledge Substrate, paste the address above, and choose OAuth as the sign-in. Leave the client ID and secret empty.
3. Read the warning ChatGPT shows for servers it has not reviewed, choose I understand and want to continue, then Create as a plugin.
4. Install the plugin. A Knowledge Substrate sign-in page opens: sign in and choose the permissions to grant.
5. Try it in a chat.

Grok

Not yet tested Corvair has not connected Grok to the Knowledge Substrate. These steps follow Grok's own public instructions, which can change: Grok documentation.

xAI's documentation describes adding a remote server to Grok Build, its terminal tool. It does not describe adding a custom MCP server in the Grok chat app, so there is no guide for chat here.

1. In a terminal, add the server with the command below.
2. The first time it is used, Grok Build opens a browser: sign in to the Knowledge Substrate and choose the permissions to grant.
3. Inside a Grok Build session, type /mcps to see the server, sign in again, or turn it on and off. Outside a session, grok mcp list shows it.

grok mcp add --transport http corvair-cks https://cks.corvair.ai/mcp

Sign-in and permissions

Sign-in happens on the Knowledge Substrate's own page, with the same account you use in its screens. You then choose what the assistant may do.

• The assistant never sees your password.
• Every request sees only what you are allowed to see, in the knowledge bases you belong to.
• Anything that deletes or erases returns a preview first. You confirm it in the Knowledge Substrate's screens, not in the chat.
• The connection renews on its own. Connecting again with the same permissions does not ask again.

Your first session

Try these in your assistant once it is connected.

Search my company library for our warranty terms. Show each answer
with the passage it came from and its source.

What do we know about Halvorsen Foods? List the account's memories
and learnings. Read only.

List the files in my Vault that are on hold, with the reason for each.

Settings for any MCP client

Smaller connectors, for clients with a tool limit

Each of these addresses carries one part of the tools. Add only the ones you need.

Each tool calls the same API route a program would, so the same permissions apply everywhere. The full list of tools is in the API reference.

Access keys

For a client or a script that cannot sign in through a browser: in the Knowledge Substrate's screens, open Account, choose Keys, then Make a key. Name it, choose its permissions and when it expires: after 30, 90 or 365 days, or never. The key is shown once. Send it as a header:

Authorization: Bearer cks_live_…

A key cannot change administrator settings. Those need a person signed in.

Use the API from your own software

Everything an assistant can do, your own software can do through the HTTP API. All routes are versioned and answer in JSON.

curl -X POST -H "Authorization: Bearer $CKS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question": "What does the warranty exclude?", "top_k": 5}' \
  https://cks.corvair.ai/query/$KB_ID/search

Good to know

• Costs. Research, and anything that calls an AI model, draws on the knowledge base's budget. Each tool says whether it does.
• Long work. Research, crawls and exports carry on after the chat is closed.
• One record. Your assistants, your applications and the screens all use the same knowledge bases, memory and Vault.
• Activity. The history records which tool was called and when, not what was said.
• Disconnect. In the screens, open Account, then Connected apps, and choose Remove. It takes effect within a minute. Keys are listed there too.

Troubleshooting