KnowMan MCP server for GitHub Copilot CLI

Add the server from the terminal

Copilot CLI adds a local stdio MCP server with copilot mcp add SERVER-NAME -- COMMAND [ARGS...], and the docs show an npx example in exactly this shape (GitHub Docs). For KnowMan, name the entry knowman and use npx -y @knowman/mcp as the command, which starts the local stdio server and needs Node 22 or newer (knowman-mcp).

The --env KEY=VALUE flag sets environment variables for the server and can be repeated (GitHub Docs). This matters here: PATH is inherited automatically, but all other environment variables must be configured explicitly (GitHub Docs). The local KnowMan server reads its API key from the KNOWMAN_API_KEY environment variable (knowman-mcp).

You can also write the entry directly into the user-level configuration file, which is useful for adding multiple servers at once (GitHub Docs). The config block above shows the entry in that form.

Or use the /mcp add form

In an interactive session, type /mcp add. A configuration form opens, and you use Tab to move between fields (GitHub Docs). For a stdio server, the Command field takes the command to start the server, including any arguments (GitHub Docs).

Enter npx -y @knowman/mcp as the command (knowman-mcp). Only PATH is inherited automatically, so set KNOWMAN_API_KEY in the form's environment settings as well (GitHub Docs). Press Ctrl+S to save; the MCP server is added and available immediately, without restarting the CLI (GitHub Docs).

Run against the hosted remote server

KnowMan runs a hosted remote MCP server at https://api.knowman.io/mcp using Streamable HTTP. It accepts OAuth sign-in or an API key sent as Authorization: Bearer <key> (knowman-mcp).

On the client side, Copilot CLI supports remote transports over Streamable HTTP, while SSE is the legacy transport, deprecated in the MCP specification but still supported for backwards compatibility (GitHub Docs). For remote servers, copilot mcp add accepts --header "HEADER: VALUE", repeatable for multiple headers (GitHub Docs). That is the documented way to pass the Authorization header the hosted KnowMan server expects.

Where the configuration lives

The user-level MCP configuration file is ~/.copilot/mcp-config.json, useful for sharing configurations or adding multiple servers at once. It uses a top-level "mcpServers" object, and a local server entry is declared with "type": "local", with launch arguments in the "args" array (GitHub Docs).

Per-repository configuration can live in .mcp.json in any directory from the working directory up to the repository root, and .github/mcp.json holds shared configuration committed to the repository (GitHub Docs). .mcp.json takes precedence over .github/mcp.json, and on name conflicts, definitions closer to the working directory win (GitHub Docs).

Check the server with /mcp

Type /mcp in an interactive session to open the MCP server dashboard (GitHub Docs). Then ask your assistant to search or save, for example "search my KnowMan for ..." or "save this URL" (knowman-mcp).

Separately, the GitHub MCP server is built into Copilot CLI and is already available without any additional configuration (GitHub Docs). Any other MCP servers you want, including KnowMan, are added with the methods above.

The six KnowMan tools

KnowMan's MCP server 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 Knowledge Base with an optional note. kb_recent lists recent items. kb_memories lists saved claims, decisions, and playbooks (knowman-mcp). For more on putting a knowledge base behind MCP, see the MCP server guide.

If something does not work

If your organization or enterprise configures an allowlist policy, only servers permitted by the allowlist policy can run in Copilot CLI (GitHub Docs). Copilot connectors are in public preview and subject to change (GitHub Docs).

Check Node first: the local server needs Node 22 or newer (knowman-mcp). Then check the environment: Copilot CLI inherits only PATH automatically, so every other variable, including KNOWMAN_API_KEY, must be set explicitly (GitHub Docs).