Reference
MCP Tools
Knowit exposes nine tools over MCP. Retrieval is tiered: search and resolve return summaries, get_knowledge fetches full content.
Retrieval
| Tool | Purpose |
|---|---|
resolve_context | Resolve 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_knowledge | Search knowledge across one or more sources by query. Like resolve_context, returns title, summary, and metadata only. |
get_knowledge | Fetch 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
| Tool | Purpose |
|---|---|
store_knowledge | Store 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_learnings | Batch-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
| Tool | Purpose |
|---|---|
resolve_source_action | Determine 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_source | Connect a first-class source provider such as local or notion. The preferred product-facing source onboarding flow. |
register_mcp_source | Register 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_sources | List configured Knowit sources, including local and external MCP-backed sources. |
Recommended agent flow
- Call
resolve_contextbefore planning or editing code. - Call
get_knowledgefor the entries whose summaries look relevant. - Call
store_knowledgefor anything important decided mid-session. - Call
capture_session_learningsonce at the end of the session.
See How It Works for the full loop and Notion Integration for provider routing.