Skip to main content

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.
Find a page with search_wiki, check where it came from with list_wiki_mentions, then follow the linked concepts with get_wiki_graph. If you use several workspaces, check each workspace’s guid and whether wiki is enabled with list_workspaces, then pass a workspaceGuid.
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.
  1. Eligible plan — the workspace’s subscription is Pro, Max, Team, or Enterprise. Free and Lite are not eligible.
  2. Activated — a workspace admin has turned wiki on for the workspace.
When a call is gated, the tool returns an error envelope (HTTP 402) with a machine-readable error_code: Envelope shape (relayed verbatim from the backend):
  • current_plan — the workspace’s current plan display name, or null when there is no subscription.
  • required_plans — upgrade targets for WIKI_PLAN_REQUIRED; null for WIKI_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, or null when the caller cannot act themselves (team member, or activation by an admin).
Workspace selection. By default the wiki tools resolve the workspace implicitly from your API Key — a workspace-bound or team key resolves directly; a personal or OAuth token resolves to your default workspace — the same way the note tools scope.If your account belongs to multiple workspaces, call list_workspaces to enumerate them (each with its guid and whether wiki is enabled), then pass the chosen workspaceGuid to any wiki tool to target that workspace explicitly. Omitting workspaceGuid keeps the default-workspace behavior. The backend verifies you are a member of the workspace you pass.

list_workspaces

List the workspaces your API Key can access, each with its guid, name, and whether wiki is enabled. Use it to pick a workspaceGuid for the wiki tools when your account belongs to more than one workspace. This tool takes no parameters. It returns:
  • A personal/OAuth token lists every workspace you are a member of; a workspace-bound or team key lists just that one.
  • isWikiEnabled reflects whether wiki is both plan-eligible and activated for that workspace — pick a workspace where it is true, then pass its guid as workspaceGuid.

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.
  • Pick a workspace first (multiple workspaces): list_workspaces → pass the chosen workspaceGuid to any tool below.
  • Find what the wiki knows about a topic: search_wikiget_wiki_page.
  • Find where a page is grounded in your notes: search_wikilist_wiki_mentions.
  • Explore how concepts connect: search_wikiget_wiki_graph (mode: "around", pageGuid).