MCP Tools

MindWiki advertises 27 tools for retrieval, capture, editing, context packs, proposals, and oversight. Clients choose which tools they expose; a listing is not permission to execute a tool.

Read, ask, and context tools work on every plan within the Free usage limits; the remaining tools (writes, proposals, index updates) require Pro or Power. OAuth scopes are mcp:read, mcp:capture, and mcp:write; legacy mcp grants all three. Write includes capture. API keys use read and write (capture requires write). Vault agent permissions also apply. Muse directory launch is pending.

search and fetch provide the retrieval names used by ChatGPT-compatible clients and can also be used by other MCP clients. Start with mindwiki_get_agent_operating_guide to learn the vault’s instructions, then retrieve only the context needed.

Tool catalog

Search a user's MindWiki vault and return compact page identifiers, titles, and URLs for assistant retrieval flows.

  • Access: read
  • Parameters and schema: search

fetch

Fetch one MindWiki page by an id or path returned from search, including its markdown content and page URL.

  • Access: read
  • Parameters and schema: fetch

Search across your vault using hybrid keyword + semantic search

mindwiki_read_page

Read a page from your vault by path

mindwiki_write_page

Create or update a page in your vault. Updating an existing path replaces its full content, so this is treated as a destructive (overwriting) write.

mindwiki_list_pages

List pages in your vault (path + title metadata only), optionally filtered by prefix. Results are capped; narrow with prefix or raise limit for more.

mindwiki_ask

Ask a question and get an answer synthesized from your vault knowledge

mindwiki_similar

Find pages similar to a given page

mindwiki_graph

Get the knowledge graph structure (nodes and edges) of your vault

mindwiki_capture

Quick capture a thought, note, or link into the vault inbox

mindwiki_lint

Run a health check on your vault — find orphan pages, broken links, etc.

mindwiki_update_index

Rebuild the vault's index page and re-embed pages whose semantic-search entry is missing or out of date. Each call processes one bounded batch and reports how many pages remain; call again until done is true.

mindwiki_get_relevant_context

Retrieve MindWiki pages relevant to a concrete goal, with optional constraints and a bounded result limit.

mindwiki_list_context_packs

List the user's saved context packs for recurring work.

mindwiki_get_context_pack

Load a named context pack and return its included MindWiki pages.

mindwiki_prepare_context

Build a bounded context plan for a vault task when the user wants MindWiki to choose between saved context packs and general vault retrieval. Returns a strategy, selected packs, supplemental page references, alternatives, rationale, and an optional proposed_pack candidate. Plan mode returns references only; response_mode 'inline' includes page content within the selected budget. Records one context-usage event.

mindwiki_search_context_packs

Search the user's context packs by intent across names, aliases, triggers, tasks, tags, profiles, and page titles. Returns ranked candidates with a rationale and does not load page content.

mindwiki_propose_context_pack

Create a pending safe-additive proposal for a new context pack without creating the pack itself. Validates every page path and normalizes the slug from the supplied name when omitted.

mindwiki_create_proposal

Create a pending proposal for a vault change instead of silently mutating important knowledge.

mindwiki_validate_proposal

Validate a proposal payload without saving it. Returns structured errors and warnings with path, code, message, and suggested correction.

mindwiki_dry_run_proposal

Re-run validation and dry-run against the CURRENT vault state for an existing proposal id. Useful when time has passed since the proposal was created — base hashes may have drifted, and the dry-run reflects the current vault. Persists nothing; the proposal row is unchanged.

mindwiki_request_proposal_apply

Relay an in-chat user approval to apply an apply_ready proposal. For safe_additive proposals the apply runs immediately and the user's words are recorded as audit evidence. For safe_structural and higher the response asks the user to approve in the MindWiki app — the AI initiated the request but the apply itself requires the user's own trusted surface. Always re-validates the proposal server-side; drift returns needs_refresh with zero writes.

mindwiki_request_proposal_reject

Relay an in-chat user rejection of a pending proposal. Always safe to delegate (rejecting destroys no vault content), so this only needs the create_proposals permission, not apply_proposals. Records the user's words in the activity log for audit.

mindwiki_list_proposals

List pending or historical agent proposals for review and approval workflows.

mindwiki_get_agent_activity

Return the recent MCP activity log so users and agents can see what AI clients read, wrote, proposed, or attempted.

mindwiki_list_agent_sessions

List recent AI client sessions connected through MCP, including client identity, auth method, and last activity.

mindwiki_get_agent_operating_guide

Read the user's optional Agent Operating Guide from _meta/agent/ when the user asks to view or use their guide. Returns the guide's markdown files and installation status without changing the vault.

Verify a connection

First retrieve a known note and check its source. Test saving separately with a harmless capture, then verify it in MindWiki. Inspect proposals and dry-run results before approving changes. A timeout after a write may mean the result was saved: check before retrying.