Add the server in Warp
Warp supports MCP servers for its local agents, including local stdio servers launched with a CLI command (Warp docs). KnowMan's MCP server is a standalone stdio server, so this is the form to use.
The global config file is ~/.warp/.mcp.json; a project-scoped file sits at .warp/.mcp.json at the project root (Warp docs). Warp configures servers with a JSON snippet: each entry sits under mcpServers with a unique name, and a CLI server needs command and args (Warp docs).
The snippet above follows that format: command npx, args ["-y", "@knowman/mcp"], and KNOWMAN_API_KEY in env. Warp lets a CLI server specify env and working_directory (Warp docs). You can click + Add in Warp settings and paste the snippet, since Warp accepts configurations copied from most MCP clients (Warp docs). KnowMan needs Node 22 or newer.
Sign in once with knowman login
You can skip pasting a key into the config. Run npx -p @knowman/mcp knowman login once. It opens your browser to sign in, and the saved credential is shared by the CLI and the MCP server, so the env block can be dropped.
Prefer a key in the file? Create one at Settings > Connections > Connect an AI agent in the KnowMan web app. Keys look like km_....
Start the server in Warp
Warp launches a CLI server's command when starting up and shuts it down on exit (Warp docs). Once registered, you can Start or Stop the server from the MCP servers page (Warp docs). If you close Warp with the server running, it runs again on the next start. Servers that are stopped stay stopped (Warp docs).
Project-scoped servers need approval
A server defined in .warp/.mcp.json at a project root requires explicit approval and must be toggled on individually (Warp docs). These servers are session-scoped: after restarting Warp, toggle them on again if you still trust the repo (Warp docs).
Verify the six tools
Each running server in Warp shows its available tools and resources (Warp docs). Start the knowman server from the MCP servers page, then confirm you see six kb_ tools: kb_search, kb_ask, kb_get_item, kb_save, kb_recent, and kb_memories. If the list is empty or the server will not start, see the section below.
What the tools do
kb_search searches saved items by keyword or meaning and returns titles, URLs, and metadata. kb_ask answers a question about your Knowledge Base 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 recently saved items. kb_memories lists saved claims, decisions, and playbooks. For the wider setup story, see the MCP server knowledge base guide.
If the server does not work
For connection problems, click the View Logs button on the server from the MCP servers page (Warp docs). Before sharing logs, remove sensitive information: Warp notes they may contain API keys (Warp docs).
Warp advises setting working_directory explicitly when a command or args include relative paths (Warp docs). The KnowMan snippet uses none, so you do not need it here.
Questions people ask
Where does the Warp MCP config file live?
Global servers go in ~/.warp/.mcp.json. A project-scoped server goes in .warp/.mcp.json at the project root. See Warp docs.
Can I use knowman login instead of an API key?
Yes. Run npx -p @knowman/mcp knowman login once, which opens your browser to sign in, and the saved credential is shared by the CLI and the MCP server, so the env block can be dropped from the config.
Why does the server not start in Warp?
Open the MCP servers page and press Start. Warp launches CLI server commands at startup, and a server that was running when you closed Warp runs again on the next start (Warp docs). For errors, click View Logs on the server (Warp docs).
Is it safe to share Warp MCP server logs?
Only after editing them. Warp states that logs may contain API keys, so remove sensitive information before sharing (Warp docs).