Overview
The wiki tools are read-only tools for searching and reading the entities, concepts, and relationships extracted from your meeting notes:search_wiki— Keyword search over wiki pages. The entry point: returns ranked pages (pageGuid,name,pageType, relevance) that you pass to the other three tools.get_wiki_page— A single page’s body (description + generation state) plus metadata and its structured mentions, aliases, and links.list_wiki_mentions— The note paragraphs that reference a page (where, across your notes, the page is mentioned).get_wiki_graph— A node+edge slice of the knowledge graph, for traversing how pages connect.
search_wiki, check where it came from with list_wiki_mentions, then follow the linked concepts with get_wiki_graph.
Pass every wiki tool a workspaceGuid from list_workspaces.
Always pass an explicit
workspaceGuid in new calls. The server schema allows omission for compatibility with existing clients. When omitted, the server selects a workspace only if the credential’s workspace binding or accessible candidates narrow the target to one workspace.With multiple candidates, the server returns error JSON with status_code: 409 and each candidate’s guid and name in detail.workspaces. Choose one and retry. Valid credentials with no accessible workspace return status_code: 404.The server returns these errors in an MCP HTTP 200 response with result.isError: true. The error JSON is in the text content.Read-only (v1). Creating, renaming, merging, and deleting wiki pages are not supported. For note content, use
search_notes or get_note.Access & the plan gate
Wiki is a paid feature that a workspace must turn on. The tools are always listed, but the plan and the enabled state are checked when you call them. A workspace can use wiki only when both of these are true.- Eligible plan — the workspace’s subscription is Pro, Max, Team, or Enterprise. Free and Lite are not eligible.
- Activated — a workspace admin has turned wiki on for the workspace.
error_code and status_code: 402. The MCP response is HTTP 200 with result.isError: true.
Envelope shape (relayed verbatim from the backend):
current_plan— the workspace’s current plan display name, ornullwhen there is no subscription.required_plans— upgrade targets forWIKI_PLAN_REQUIRED;nullforWIKI_NOT_ACTIVATED. (Team Free Trial is intentionally excluded — it is an already-held trial, not an upgrade target.)action_url— a web link to act on, ornullwhen the caller cannot act themselves (team member, or activation by an admin).
search_wiki
Search the wiki for pages by keyword. Use this first; pass the returned pageGuid to the other tools.
Returns ranked page results, each with
pageGuid, name, pageType (e.g. CONCEPT, ENTITY), and a relevance score.
get_wiki_page
Get one wiki page by its pageGuid (from search_wiki).
Returns the page body (description + generation state) and metadata (title, type, mention/alias/link counts, timestamps) plus the page’s structured
mentions, aliases, and links. Follow up with list_wiki_mentions to see where the page is referenced across notes.
list_wiki_mentions
List the note paragraphs that mention a wiki page.
Returns mention records (source note, paragraph, extracted text, kind) plus a pagination cursor.
get_wiki_graph
Get a node+edge slice of the wiki knowledge graph. Returns { nodes, edges }, where each edge carries a typed relationship between two pages.
Result cap.
get_wiki_graph returns at most limit nodes (default 50, max 200) and only the edges between those returned nodes (dangling edges are dropped, so every edge’s endpoints are present in nodes). When the underlying graph was larger than the cap, the response sets truncated: true — narrow with mode / q / type or a smaller radius / depth to get a focused slice. This keeps a hub page’s neighborhood from returning an unbounded payload.Cluster-based exploration is not yet exposed. The web app’s newer graph-exploration views (overview/context/cluster) are internal-only; the MCP
get_wiki_graph tool exposes the seed / expand / around / links modes. Exposing cluster exploration externally is on the roadmap.Recommended chains
- Pick a workspace first:
list_workspaces→ pass the chosenworkspaceGuidto every tool below. - Find what the wiki knows about a topic:
search_wiki→get_wiki_page. - Find where a page is grounded in your notes:
search_wiki→list_wiki_mentions. - Explore how concepts connect:
search_wiki→get_wiki_graph(mode: "around",pageGuid).