Reference

MCP Tools

Knowit exposes nine tools over MCP. Retrieval is tiered: search and resolve return summaries, get_knowledge fetches full content.

Retrieval

ToolPurpose
resolve_contextResolve implementation context for a task across one or more sources. Accepts a task description plus optional repo, domain, and files. Returns title, summary, and metadata — not full content.
search_knowledgeSearch knowledge across one or more sources by query. Like resolve_context, returns title, summary, and metadata only.
get_knowledgeFetch full content for one or more entries by ID (up to 20). Phase 2 of tiered retrieval — call it after search_knowledge or resolve_context with the IDs that look relevant.

Storage

ToolPurpose
store_knowledgeStore one knowledge entry in the selected source — the local store or an external MCP-backed source. Takes type, title, content, and optional body blocks, scope, repo, domain, tags, confidence, URL, and metadata.
capture_session_learningsBatch-store up to 20 knowledge items from a coding session. Existing entries with the same title, type, scope, repo, and domain are updated rather than duplicated. Meant to be called at the end of a session.

Sources and routing

ToolPurpose
resolve_source_actionDetermine whether Knowit should handle a read/write directly or route the agent to an external provider MCP next. Use when the user mentions Knowit but not the downstream provider.
connect_sourceConnect a first-class source provider such as local or notion. The preferred product-facing source onboarding flow.
register_mcp_sourceRegister an arbitrary external MCP server as a Knowit source using explicit tool mappings — a command to launch it plus a toolMap naming its store, search, and resolve tools. The advanced counterpart to connect_source.
list_sourcesList configured Knowit sources, including local and external MCP-backed sources.

Recommended agent flow

  1. Call resolve_context before planning or editing code.
  2. Call get_knowledge for the entries whose summaries look relevant.
  3. Call store_knowledge for anything important decided mid-session.
  4. Call capture_session_learnings once at the end of the session.

See How It Works for the full loop and Notion Integration for provider routing.