Choose the Kilo Code config file
For a global setup, open ~/.config/kilo/kilo.jsonc. It applies to every project. For one project, use kilo.jsonc in the project root, or .kilo/kilo.jsonc for a cleaner setup. Project-level settings take precedence over global settings. See Kilo Code MCP documentation.
Add the KnowMan server
Open the chosen kilo.jsonc file. Add the knowman entry under the top-level mcp key using the configuration on this page. Kilo Code uses "type": "local" for a local stdio server, and its command value is an array. See Kilo Code MCP documentation.
Create and insert an API key
In KnowMan, open app.knowman.io, then go to Settings > Connections > Connect an AI agent. Create an agent key, copy it, and replace km_... in the KNOWMAN_API_KEY field. Keys look like km_.... See the KnowMan MCP guide.
Sign in once with knowman login
Run npx -p @knowman/mcp knowman login and approve access in the browser. The CLI and MCP server share the saved credential, so you can then remove the env block from the Kilo Code configuration. See the KnowMan MCP guide.
Verify the connection
Open Settings > Agent Behaviour > MCP Servers and review the KnowMan server status. Kilo Code automatically detects available tools and resources after configuration. If the status failed, check the CLI output for error details and confirm that commands and paths are correct. See Kilo Code MCP documentation.
KnowMan tools available in Kilo Code
KnowMan exposes kb_search for searching saved items by keyword or meaning, kb_ask for answers with citations, kb_get_item for one item's readable content, and kb_save for saving a URL with an optional note. It also exposes kb_recent for recent items and kb_memories for saved claims, decisions, and playbooks. See the KnowMan MCP guide.
Add the server through the Kilo Code settings
In the VS Code extension, open Settings > MCP, choose Add Server, and select Local (stdio). Enter the command, arguments, and optional environment variables. Kilo Code writes changes to the appropriate config file, where you can also add, edit, enable, disable, or delete MCP servers. See Kilo Code MCP documentation.
Questions people ask
Can Kilo Code run the KnowMan MCP server locally?
Yes. Kilo Code supports local stdio servers that run as child processes and communicate through stdin and stdout. KnowMan uses this local transport. See Kilo Code MCP documentation and the KnowMan MCP guide.
Where should the KnowMan MCP configuration go?
Use ~/.config/kilo/kilo.jsonc for all projects, or put kilo.jsonc in a project root. You can also use .kilo/kilo.jsonc. Project-level configuration takes precedence over global configuration. See Kilo Code MCP documentation.
Do I need KNOWMAN_API_KEY after running knowman login?
No, after a successful knowman login, the CLI and MCP server can share the saved credential, so you can remove the env block. KnowMan also supports the KNOWMAN_API_KEY environment variable. See the KnowMan MCP guide.
What should I check if Kilo Code reports a failed connection?
Check the CLI output for error details, then confirm that commands and paths are correct. KnowMan requires Node 22 or newer. See Kilo Code MCP documentation and the KnowMan MCP guide.