What the KnowMan MCP server is
The KnowMan MCP server connects an AI client to KnowMan over the Model Context Protocol, so you can ask an assistant to 'search my KnowMan for ...' or 'save this URL' (repository). The project is open source under the MIT license. Code, README, and the documented client configurations live in one place. Related reading: MCP server knowledge base and connect any AI to your notes.
The GitHub repository and the npm package
The repository is Essatt/knowman-mcp on GitHub, MIT-licensed. The npm package is @knowman/mcp, version 0.3.0, also MIT, and it requires Node 22 or later (repository). There is no global install step. npx -y @knowman/mcp fetches and runs the local server on demand (repository).
The official MCP Registry entry
The official MCP Registry entry is io.github.Essatt/knowman-mcp, version 0.3.0. The entry lists both the npm package and the hosted server (repository). You can look it up on the MCP Registry by searching for io.github.Essatt/knowman-mcp.
Local stdio server and hosted remote server
The server runs in two ways. Locally, npx -y @knowman/mcp starts a stdio server (repository). Remotely, the hosted server at https://api.knowman.io/mcp speaks Streamable HTTP. For clients with MCP OAuth, the easiest path is to add that URL, sign in, and approve the consent page (repository). You can also send an API key as Authorization: Bearer <key>; keys are created in KnowMan settings, and a key cannot create other keys. The full OAuth flow against the live hosted server, from registration through consent, token, tools, and refresh, was verified with the official MCP SDK client.
The six tools
The server exposes six tools: kb_search, kb_ask, kb_get_item, kb_save, kb_recent, and kb_memories (repository). kb_search searches saved items by keyword or meaning, returning titles, URLs, and metadata. kb_ask answers with citations. kb_get_item returns the readable content of one item, and kb_save saves a URL with an optional note. kb_memories is read-only and returns saved claims, decisions, and playbooks.
OAuth scopes, tokens, and disconnecting an app
The consent page requests two scopes: knowman.read, which covers search, read, and ask, and knowman.write, which covers saving links (repository). Access tokens last one hour and refresh automatically. To disconnect an app, delete its 'OAuth: <app name>' entry in your KnowMan API-keys list. Changing your KnowMan password disconnects every connected app.
Documented client setups
Setup needs one KnowMan account at https://app.knowman.io (repository). For key-based auth, the repository documents three clients (repository). Claude Code adds the hosted server with the claude mcp add command, http transport, and an Authorization Bearer header holding the API key. Cursor stores the hosted server URL and a Bearer API key header in mcp.json. Claude Desktop runs the local server, npx -y @knowman/mcp, with a KNOWMAN_API_KEY environment variable in claude_desktop_config.json. The Claude Code knowledge base guide covers that client in depth.
Where KnowMan fits
KnowMan saves articles and links, reads and tags them, answers questions with citations, and keeps memories such as claims, decisions, and playbooks. The MCP server is the access layer: an assistant can search the library, ask questions, save links, and read memories. KnowMan is built for one person's library today; team plans are not available yet. To weigh approaches, see knowledge base for AI agents and persistent memory for AI agents.
Questions people ask
Is the KnowMan MCP server open source?
Yes. The project is MIT-licensed and lives at github.com/Essatt/knowman-mcp. The npm package @knowman/mcp is MIT-licensed as well.
How do I run the KnowMan MCP server locally?
Run npx -y @knowman/mcp (repository). You need Node 22 or later, and the package runs as a local stdio server.
How do I connect to the hosted MCP server?
Add the server URL https://api.knowman.io/mcp and sign in with OAuth, or send an API key as Authorization: Bearer <key>. Keys are created in KnowMan settings, and a key cannot create other keys.
What OAuth scopes does the server request?
The consent page requests knowman.read for search, read, and ask, and knowman.write for saving links (repository). Access tokens last one hour and refresh automatically.