Name: ZeroWidth Compass
Author: ai.zerowidth

Tools observed via MCP handshake

search_docs — Search ZeroWidth product documentation. Returns matching pages with title, slug, public URL, and a query-relevant snippet. Use this when the user asks about a Z
get_doc — Fetch the full Markdown body of a specific docs page by its slug. Use this after `search_docs` when the user needs the complete content of a page. No authentica
list_docs — Enumerate all available docs pages, optionally filtered by product (e.g. 'compass', 'legal', 'overview'). Use this to discover what slugs exist before calling `
compass_pages_list — Lists pages in the active workspace's Compass compendium. Optional `type` filter narrows to one node type (WORKFLOW, PERSON, ROLE, SYSTEM, PAIN_POINT, DOCUMENT,
compass_pages_search — Keyword search over page titles, bodies, and tags (case-insensitive substring match), paginated. The fast way to check whether a subject already has a page befo
compass_pages_get — Fetches one Compass page by id, including its full Markdown body, header fields, and any attached Napkin sketches — view an attached sketch's actual drawing wit
compass_pages_create — Creates a typed page in the workspace's Compass compendium. Check `compass_pages_list` first — don't create a page for a subject the map already has; link to it
compass_pages_update — Edits an existing page's title, description, body, tags, header fields, or visibility — use this to FIX what you (or an extraction) got wrong instead of creatin
compass_links_create — Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON or ROLE owns WORKFLOW/SYSTEM/PRIORITY,
compass_process_diagram_ensure — Returns the Napkin diagram that holds a WORKFLOW page's steps, creating it when the page has none. If the page body has a ```mermaid block, it moves into the di
compass_page_links_list — All typed edges touching one page, both directions, each hydrated with the other endpoint's page summary. Use this to understand a subject's neighborhood before
compass_interviews_create — Mints a stakeholder-interview invite: a no-account guest link where the person talks to an interviewer agent briefed by your focusPrompt, and the transcript flo
compass_interview_targets — Ranks the PEOPLE the map says know about a page (workflow, system, pain point): `owns` links first, then `involved_in`, then weaker edges. Each target carries c
compass_interview_invite — Emails the guest link for an existing interview, framed as coming from the REQUESTING USER (their name signs it; replies go to them). Author `message` in their
compass_gaps_list — Lists the workspace's open questions — the gap registry: what the map doesn't know yet. Defaults to OPEN gaps. This is where you keep your head — check it befor
compass_gaps_create — Records something you don't yet know — the gap registry is your working memory, so use it liberally while mapping or interviewing. Give one clear question, WHY
compass_gaps_resolve — Closes a gap once you've learned the answer (ANSWERED, with the resolution) or decided it doesn't matter (DISMISSED). Keep the registry honest — resolve gaps as
compass_opportunities_list — The workspace's changes — fixes, chores, new steps, experiments. Each carries `statusName` (the workspace's own word for where it is) and `statusCategory` (TRIA
compass_opportunities_propose — File an AI-PROPOSED opportunity into the workspace's review queue — the scouting verb (the opportunity-scout routine's main move). Unlike compass_opportunities_
compass_opportunities_create — Record a change — a fix, a chore, a new step, or an experiment worth trying. Anchor it to a workflow page when one fits (compass_pages_list); leave unanchored o
compass_opportunities_register_expectation — The honesty mechanism: write what the experiment is expected to change BEFORE evidence exists. Creates a Ledger decision entry and links it to the opportunity —
compass_opportunities_mark_implemented — The measurement window's boundary: when the user says the experiment's change actually shipped / went live / rolled out, record the landing date. Readings befor
compass_map_view — Renders the workspace's visual map to an image and returns it so you can SEE it the way the user does when they open Map: a transit-style map seen from above. E
compass_pages_delete — Moves a page to the trash (soft delete — its connections and anchored opportunities go with it, and compass_pages_restore brings the whole set back). Use this t
compass_pages_restore — Puts a trashed page back on the map, together with exactly the connections and opportunities its delete took. Use when the user wants a deleted page back (the p
compass_links_update — Edits an existing edge between two pages: its `kind` (how the two relate), its `note`, and/or when it was true (`validFrom` / `validTo`). Use kind to CORRECT a
compass_links_delete — Deletes one edge from the graph (the pages stay). Use only when a connection was never true — the system isn't used by that workflow, it was recorded by mistake
compass_opportunities_update — Corrects an opportunity's content: label, description, priority, what done means, the 1–5 value / feasibility / risk scores, the owner (a PERSON page), notes, t
compass_opportunities_delete — Removes an opportunity from the pipeline (soft delete). For an AI proposal the user doesn't want, this is the dismiss verb; for a captured experiment that was a
compass_opportunities_accept — The review verb for the Inbox: promotes an AI-PROPOSED opportunity (from compass_opportunities_propose or the opportunity scout) into the workspace's own pipeli
compass_interviews_list — Every stakeholder interview in the workspace, newest first: who was invited, status (INVITED / IN_PROGRESS / COMPLETED), focus, message count, whether the trans
compass_interviews_get — One interview in full — metadata plus the transcript of what the guest actually said. Read this before summarizing an interview or drafting pages from it: the t
compass_interviews_revoke — Kills an interview's invite link — the guest's next visit sees that the link is no longer active. Use when an invite went to the wrong person, the user changed
compass_inbox_list — The Compass Inbox in one read: finished interviews awaiting review (transcript in, not yet turned into pages), AI-proposed opportunities awaiting accept / dismi
compass_gaps_update — Edits an open question's wording, rationale, or suggested resolution — for sharpening a vague question or fixing one you phrased badly. Closing a gap is compass
compass_statuses_list — The statuses this workspace's changes move through, in board order — the names people use. Each sits in a group: Undecided (TRIAGE), Not started (BACKLOG), In p
compass_opportunities_set_status — Move a change to one of the workspace's statuses, by name (compass_statuses_list has them — e.g. "In review"). The old lane keys (NEW / QUALIFYING / BACKLOG / E
compass_workflow_steps — Every step in a WORKFLOW page's steps diagram, in diagram order, with its phase, whether it is itself a workflow (subWorkflowPageId), and who the map says owns,
compass_step_claims_list — Every claim about a WORKFLOW's steps, oldest first: the step (nodeId; null = the workflow as a whole), the role or person (subject), the relation, who says so (
compass_step_claims_propose — Propose claims about who does what in a WORKFLOW, and what each step is done in, from what someone said. Each claim names a step (nodeId from compass_workflow_s
compass_workflow_rollup — Per run and per month: hands-on minutes, waiting minutes, labor cost (hands-on time priced through each role's hourly rate), and hard costs, each as a low–high
compass_workflow_learning — Newest first: steps added to or dropped from the diagram (and by whom), and claims about who does what or what a step takes — said, corrected (with what they re
compass_step_measures_propose — Propose estimates from what someone said, as ranges — people know "20 minutes to an hour", not "37 minutes"; when they give one number, use it for both ends. Ea
compass_scenario_changes — Changes whose effects reach a WORKFLOW's steps — or any nested workflow's — plus changes anchored to it with no effects yet, each with what it does per step. Pa
compass_change_effects_set — Replace a change's effects: for each step it reaches (workflowPageId + nodeId from compass_workflow_steps — a sub-workflow's steps included), one of eliminate,
compass_transformations_get — What the workflows behind a PRIORITY could become, at five levels (Assist, Automate, Re-form, Invert, Dissolve): for each, whether it fits, is already reached,
compass_priority_steps_find — Reads every mapped workflow against one PRIORITY (or VALUE) and proposes the steps that move it (or where the business lives the value), one marked as what hold
compass_transformations_read — Starts reading the five levels for a PRIORITY in the background (a minute or two). Needs at least one kept step that impacts the priority. A read under way is l
compass_transformations_respond — Records what someone told you about one level of a PRIORITY's current transformations, in their words or a faithful summary: that they already do it, what rules
compass_transformations_make_change — Creates a Change from one level of a priority's transformations, with its step effects and the priority it serves, and starts drafting in Workbench up to three
compass_step_suggestions_list — Your earlier read of a WORKFLOW's steps: for each suggestion, the steps it covers (nodeIds, labels), what could do them (proposal.doer: a flow and its mode, a s
compass_step_suggestions_build — Builds a step suggestion the way Compass's Build button does: makes its change if it isn't one yet, then the thing in Workbench — a flow drafted from the step i
compass_changes_upsert — Create or update up to 100 changes in one call, each matched by `url` — the GitHub issue, Linear or Jira ticket, PR or doc it mirrors. A url already linked to a
compass_role_story — One ROLE page's story: hands-on hours a month by kind of work (rote, judgment, relationship, sign-off) before its first change or Task landed and now; what land
compass_roles_overview — Every role in the workspace in one row each, changed or not: hours documented against its working month, hours a month saved, saved hours by stage (looking into
comments_list — Lists the comment threads on one workspace entity (open first, then resolved) with authors and timestamps. Read this before weighing in on contested work — the
comments_create — Posts a comment on a workspace entity — a new thread, or a reply when rootId is given. Use it to leave findings where the discussion already lives (an eval resu
comments_resolve — Sets a comment thread's resolved state (rootId = the thread's root comment id). Resolve ONLY when the human asked or the thread's question is demonstrably settl
search_workspace — Finds anything in the workspace in one call — uploaded files (searching the text inside them), folders, Workbench flows, shims, knowledge bases and tasks, Compa
entity_tags_get — Returns the tags on a batch of entities of one kind — the labels galleries organize by. Ids come from the kind's list/get tool or from search_workspace. Use it
entity_tags_browse — Without a tag: every tag in use across the workspace with how many entities carry it, most-used first — the vocabulary the team already organizes by. With a tag
entity_tags_set — Replaces the FULL tag set on one entity (an empty list clears it). Read the current tags with entity_tags_get first and pass the merged list — this is not addit

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	226 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 62 tools
13 h ago	mcp initialize	ok	200	396 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 62 tools
20 h ago	mcp initialize	ok	200	247 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 62 tools
27 h ago	mcp initialize	ok	200	349 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
34 h ago	mcp initialize	ok	200	204 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
2 d ago	mcp initialize	ok	200	1195 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
2 d ago	mcp initialize	ok	200	1267 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
2 d ago	mcp initialize	ok	200	416 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
3 d ago	mcp initialize	ok	200	374 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools
3 d ago	mcp initialize	ok	200	406 ms	server zerowidth-mcp 1.0.0 · protocol 2025-06-18 · 60 tools

ZeroWidth Compass

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from