Add the KnowMan connector in the desktop app
In the Grok Bot desktop app, open Connect apps and choose Add a custom connector at the bottom of the list (xAI docs). Enter a Name such as KnowMan, then pick a Type (xAI docs).
Pick Remote HTTPS. This type takes a Server URL with optional HTTP headers (xAI docs). Enter https://api.knowman.io/mcp, the hosted KnowMan MCP server on Streamable HTTP (knowman-mcp).
For authentication, add the header Authorization: Bearer <key>, where <key> is a KnowMan API key. Create the key in the web app under Settings > Connections > Connect an AI agent; keys look like km_... (knowman-mcp). You can also sign in with OAuth; the hosted server accepts both (knowman-mcp).
Ask a Bot to add the server by URL
You can skip the form. A Bot can add an MCP server that is not in the catalog, by URL or by a command that runs on its computer (xAI docs). If an app is not in the catalog, you can ask a Bot to connect the app's MCP server (xAI docs).
To try this, ask your Bot to connect the KnowMan server at https://api.knowman.io/mcp (knowman-mcp). A server added by a command is available to your other Bots too (xAI docs).
Use the local stdio server with the Command type
The desktop app also offers a Command type. It takes a Command and its Arguments, and you save it with Add plugin (xAI docs). A command-added MCP server runs on the Bot's computer (xAI docs).
KnowMan also runs as a local stdio server, started with npx -y @knowman/mcp on Node 22 or newer (knowman-mcp). You can enter npx as the Command and -y @knowman/mcp as the Arguments (xAI docs).
In the local config shown for Claude Desktop, the key is passed through a KNOWMAN_API_KEY env var (knowman-mcp). For the local stdio server you can instead run npx -p @knowman/mcp knowman login once; the browser sign-in saves a credential shared by the CLI and the MCP server, so the env block can be dropped (knowman-mcp).
Check the connection and use it in chat
For connected apps, confirm the app appears under Installed (xAI docs). Added means the app is installed, not that you are signed in (xAI docs). If sign-in does not finish, choose Reconnect on the app (xAI docs).
In chat, type @ to attach the app to the task (xAI docs). Then ask for a search. The kb_search tool returns titles, URLs and metadata for saved items (knowman-mcp).
If the connector does not save or connect
Adding a server on a private network, or one that uses a private certificate authority, asks for your approval first (xAI docs). If your team admin's MCP policy blocks the server, it cannot be saved (xAI docs). A blocked app shows Disabled by team admin; ask your admin to enable it (xAI docs).
The six KnowMan tools
Connected apps are account-wide: a connected app is available to every Bot you run, and app logins stay off the computer (xAI docs).
KnowMan exposes six tools (knowman-mcp). kb_search searches saved items by keyword or meaning and returns titles, URLs and metadata. kb_ask answers a question with citations. kb_get_item returns the readable content of one item. kb_save saves a URL to the Inbox or the Knowledge Base with an optional note. kb_recent lists recent items. kb_memories lists saved claims, decisions and playbooks, and is read-only (knowman-mcp).
New to MCP? Read what an MCP server is, or see how a Grok Bot knowledge base fits together.
Questions people ask
How do I add an MCP server to Grok Bot?
In the desktop app, choose Add a custom connector at the bottom of Connect apps, enter a Name, then pick a Type (xAI docs). For the Command type, choose Add plugin to save it (xAI docs). A Bot can also add an MCP server by URL or by a command that runs on its computer (xAI docs).
Which Server URL does KnowMan use?
Use https://api.knowman.io/mcp, the hosted KnowMan MCP server on Streamable HTTP (knowman-mcp). It accepts an API key sent as Authorization: Bearer, or OAuth sign-in (knowman-mcp).
Why can't I save my custom connector?
If your team admin's MCP policy blocks the server, it cannot be saved (xAI docs). A blocked app shows Disabled by team admin, and you can ask your admin to enable it (xAI docs).
Do I need knowman login for the remote form?
No. The remote form authenticates with the Authorization header or the OAuth approval, so no local sign-in step is needed (knowman-mcp). For the local stdio server, one run of npx -p @knowman/mcp knowman login saves a credential shared by the CLI and the MCP server (knowman-mcp).