# Zerowidth Workbench MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.zerowidth%2Fworkbench
Registry id: `mcp-registry/ai.zerowidth/workbench`
Status: live (checked 2026-10-27T00:37:34.384Z)

## Measurements (30 days)

- Uptime: 99.86%
- Checks: 3636
- Outages (90 days): 5

## Install

```json
{
  "mcpServers": {
    "zerowidth-workbench-mcp-server": {
      "type": "http",
      "url": "https://api.zerowidth.ai/mcp/x/workbench"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http zerowidth-workbench-mcp-server https://api.zerowidth.ai/mcp/x/workbench
```

## Tools (61)

- `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_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_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
- `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_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_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
- `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 `
- `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
- `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
- `workbench_executions_get`: The flow's stack traces: recent executions with per-node timelines — what each node received, produced, how long it took, and the exact error when one failed. U
- `workbench_flow_authoring_guide`: READ THIS FIRST before writing or editing any raw flow orchestration JSON. Covers the document shape, the settings-vs-input-ports rule (temperature, max_tokens,
- `workbench_flows_attach_knowledge_base`: Attaches a knowledge base to an AGENT flow's draft, the same way picking it in the agent editor does: a docs knowledge base becomes a search tool the model call
- `workbench_flows_delete`: Deletes a flow. Its schedules stop, guest share links die, and evals targeting it can no longer run (their binding shows flowOk: false) — check caliper_flow_per
- `workbench_flows_edit_text`: Applies ONE precise text replacement to a flow's DRAFT orchestration — Edit-tool semantics: `find` must be the EXACT current text, copied character-for-characte
- `workbench_flows_fork`: Copies a PUBLIC flow from another workspace (a template) into this one as a new draft the user owns. Identify it by its flowUuid (the id on Workbench's public t
- `workbench_flows_get`: One flow. Default `view: summary` lists its nodes and links so you can pick one; `view: node` with a nodeId returns that node's full settings and prompt — read 
- `workbench_flows_list`: Lists every flow in the active workspace the caller can see. Returns summaries (id, name, visibility, updatedAt) — fetch one with `workbench_flows_get` for the 
- `workbench_flows_publish`: Snapshots the flow's current DRAFT as a named published version — the version schedules (workbench_flows_schedule), guest share links (workbench_flows_share_cre
- `workbench_flows_revisions_list`: The flow's revision history, newest first: published versions carry a `version` label and note; entries with version null are draft autosaves. Use it to answer 
- `workbench_flows_run`: Execute a flow and return its outputs synchronously. Runs the draft by default; pass source:"published" (optionally a version) to run the live published version
- `workbench_flows_scaffold`: Creates a runnable first-draft flow from a spec you author: pick the simplest pattern that fits (classifier for read-and-bucket, structurer for transform/extrac
- `workbench_flows_scenarios_create`: Saves a named scenario: values for the flow's variables, e.g. one demo customer. It shows in the test pane's Scenarios menu, and Caliper evals can run as it. Us
- `workbench_flows_scenarios_delete`: Deletes one scenario. A design session running as it goes back to no scenario. May return `needs_confirmation`.
- `workbench_flows_scenarios_list`: A flow's variables (each {{token}} in an agent's prompt, with its type) and every saved scenario with its values. Read this before creating or updating a scenar
- `workbench_flows_scenarios_update`: Renames a scenario or changes its values. `values` MERGES into what's saved: pass only the variables that change, and null to clear one. Get the scenarioId from
- `workbench_flows_schedule`: Set a specific built flow to run automatically on a cadence — the deterministic counterpart to a routine. Each run executes the flow's latest PUBLISHED revision
- `workbench_flows_schedules_delete`: Removes a schedule for good. Prefer workbench_flows_schedules_update with enabled: false when the user might want it back. May return `needs_confirmation`.
- `workbench_flows_schedules_list`: Every schedule on one flow: cadence, whether it's paused (`enabled: false`), the next fire time, delivery, and the last run's status. Read this before workbench
- `workbench_flows_schedules_run_now`: Runs one iteration of a schedule immediately through the real scheduled pipeline (same input, same delivery — the email or channel it normally posts to) without
- `workbench_flows_schedules_update`: Changes one schedule: `enabled: false` pauses it (configuration kept), `enabled: true` resumes and recomputes the next fire time from now; `interval` / `schedul
- `workbench_flows_share_create`: Creates a no-account guest link where anyone can chat with the flow's latest PUBLISHED revision at workbench's /s/<token> page — the fastest way to put a workin
- `workbench_flows_shares_list`: Every guest link on one flow, newest first: label, whether it's still live, the shareUrl (live links only — dead ones have no URL), expiry, and how many guests 
- `workbench_flows_shares_revoke`: Kills one guest link immediately — anyone holding it gets a closed page from then on. Conversations already had stay in the flow's history. Get the shareId from
- `workbench_flows_update`: Changes a flow's name, description, visibility, tags, or archived state — the metadata around the flow, NOT its orchestration (prompts and nodes change through 
- `workbench_kb_add_documents`: Adds documents to a knowledge base and starts ingestion (chunk + embed; graph KBs also extract entities; tabular KBs load CSV as tables). Text goes inline (Mark
- `workbench_kb_create`: Creates an empty knowledge base. Recipe 'docs' (default) for reference material an agent searches at runtime; 'tabular' for spreadsheet-style data queried with 
- `workbench_kb_delete`: Deletes a knowledge base and everything in it. Flows that search it will find nothing — check which agents use it (the user knows; the KB page in Workbench list
- `workbench_kb_document_delete`: Removes one ingested document and all its chunks; searches stop returning it at once. Get the documentId from workbench_kb_documents_list. To replace a document
- `workbench_kb_documents_list`: Every document ingested into the KB's current content: id, name, type, size, chunk count. Empty for a KB with nothing ingested yet (or one whose ingestion is st
- `workbench_kb_get`: One knowledge base: name, recipe (docs / tabular / graph), status, document and chunk counts, embedding model, and ingestion settings. Read it to confirm a KB h
- `workbench_kb_ingestion_status`: The state of one ingestion run started by workbench_kb_add_documents: PENDING / RUNNING / DONE / FAILED, chunks written, and the error when it failed. Read it w
- `workbench_kb_list`: Lists every knowledge base in the active workspace the caller can see. Returns summaries (id, name, description, status, doc/chunk counts, embedding model). Use
- `workbench_kb_search`: Retrieves the most relevant chunks from one knowledge base — the core RAG primitive. `mode:"semantic"` (default) embeds the query and ranks by meaning (spends a
- `workbench_node_catalog_get`: The ground truth for what nodes exist and what their ports actually are — verify against this instead of recalling. Search by keyword/category for summaries; pa
- `workbench_shim_add_answer`: Adds one answer (a label and, optionally, when it applies). The shim needs three examples of it before it builds again with the new answer. May return `needs_co
- `workbench_shim_add_examples`: Adds example inputs to one answer. Write inputs a real person would actually type in the shim's setting — varied in length, register and specifics, each one cle
- `workbench_shim_create`: Creates a shim from a name, the question it answers, and its answers. Add examples afterwards with workbench_shim_add_examples — three or more per answer and it
- `workbench_shim_get`: One shim in full: the question, where its inputs come from, every answer with its description and examples, what the shim still needs before it can build, and t
- `workbench_shim_list`: Every shim the user can see: id, name, the question it answers, how many answers and examples it has, and the published version's held-out accuracy (null until 
- `workbench_tasks_act`: Records THIS user's verdict on a run that is waiting on them — the labels come from the gate (workbench_tasks_run_view shows them via the plan; a wrong label er
- `workbench_tasks_compile`: Runs the compiler over a sentence and returns the PROPOSED plan (or repair-grade problems — fix by refining the sentence with the user, not by guessing). Nothin
- `workbench_tasks_create`: Creates a DRAFT Task from a name + sentence. A Task is for work with people in the loop (someone approves, decides or acts on each item before anything else hap
- `workbench_tasks_delete`: Deletes a task. Runs still in flight are stopped (a gate waiting on someone is closed), and its schedule trigger stops firing; past runs stay in history. Check 
- `workbench_tasks_freeze`: Freezes a reviewed plan as the Task's next version and activates it. Pass the EXACT plan object a compile returned — never hand-edit it (change the sentence and
- `workbench_tasks_get`: One Task in full: its sentence, status, the latest saved plan (the clauses — which run flows, which the assistant handles, who decides at each gate) with the fl
- `workbench_tasks_list`: Lists the workspace's Tasks — sentence-orchestrated processes — with their sentence, status, and recent runs (id, status, who a waiting run is on). Use this to 
- `workbench_tasks_run_view`: The run's current state rendered as its sentence: what ran (with timings), which path each gate took, what's waiting on whom and for how long, what's coming up.
- `workbench_tasks_set_sites`: Sets the full list of sites a Task's machine may reach (example.com, or *.example.com for its subdomains; up to 20), for steps that have to use a site like a pe
- `workbench_tasks_start`: Kicks off a run of a Task and returns at once; the run carries on by itself and is live on the task's page. When the task expects an input document (its trigger
- `workbench_tasks_update`: Changes a task's name — the gallery label only. The sentence and plan are versioned and change through workbench_tasks_compile + workbench_tasks_freeze, never h

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.