mcp-server

List workspace use cases and their operating guides, linked workflows, agents, routines, AgentFiles, knowledge refs, data sources, config, validation, and metadata. Use this before building or changing a multi-workflow business goal so you can reuse the existing WorkspaceUseCase instead of hand-rolling disconnected workflows. Read operatingGuides/agentGuidance first; missing operating-guide warnings mean the agent context is incomplete. This tool is read-only and does not run workflows, spend credits, trigger routines, or write to providers.

List all workflows in the workspace. Returns compact workflow summaries plus small metadataSummary fields (analytics, workflowGraph, revision, imports, builder preflight state). Use get_workflow for full steps, context, raw metadata, full builder contract/compiler preview, and update history.

List workspace-created skills. These are draft/published/archived skill records backed by AgentFile content. Use import_workspace_skill for a one-step Markdown/SKILL.md/JSON import. Use create_workspace_skill only when you already have the backing AgentFile ID. Workspace skill allowedApps/allowedActions are recommended tools only; they do not grant app/action scope, runtime bundles, workspace connections, write access, or approval bypasses.

List saved workspace views and their source/action guidance. Use this before designing a new view so you can reuse or update an existing operating surface. This is read-only and does not run workflows, read provider data, mutate KG rows, make approval decisions, or spend credits.

Add, remove, or replace the workflows assigned to an agent without passing the full agent config. - operation 'add': append workflowIds to the existing list (no-op for IDs already present) - operation 'remove': remove specific workflowIds from the list - operation 'set': replace the entire list with the given workflowIds Use 'set' with an empty array to clear all assigned workflows. Requires write access when connected with OAuth.

Move a step to a new position in the workflow's steps array. Provide exactly one target: - `insertAfter`: place the step immediately after the given step ID. - `position: "first"`: place the step at index 0. Use this to put a trigger back in first position after a remove + add cycle (the only way to recover trigger order via MCP — `add_step` always appends at the end). - `position: "last"`: place the step at the end of the array. Only the array order changes — NO next pointers or step config are modified. This is a pure cosmetic reorder that fixes the "orchestrator-issue" validator warning caused by steps being stored out of execution-chain order. Use this when the validator reports: "Step X appears after Step Y but executes before it. Reorder the steps array..." Works for both live workflows (via draft snapshot) and draft workflows. Requires write access when connected with OAuth.

Surgically edit a PipelineExecution's metadata, currentStepId, or status without re-running the workflow. EXCEPTION-ONLY tool. Primary use case: relabeling a stuck, completed, or test run's executionName so it's distinguishable in the executions list, without spending credits on a rerun. Other use cases: - Update metadata.debugNote during incident investigation - Update metadata.pendingReasonTag for UI annotation - Advance currentStepId for stuck-state recovery (only when status is waiting or failed) - Force status transitions: waiting/failed/credits_missing → running, or started → stopped/canceled DO NOT use for routine work. If you find yourself reaching for this tool repeatedly, the underlying workflow is misconfigured and the right fix is to update the workflow definition or the execution input. Required: - API key with admin:patch scope (Stage 2) - reason, expectedUpdatedAt — same as patch_timeline_fields Allowed paths: - metadata.debugNote - metadata.pendingReasonTag - metadata.executionName (relabel run; orchestrator may recompute via executionNameTemplate) - currentStepId (only when status is waiting or failed) - status (only waiting → running, failed → running, credits_missing → running, started → stopped/canceled) Terminal execution exception: - completed/canceled/approved/stopped executions may patch only metadata.executionName - terminal writes to metadata.debugNote, metadata.pendingReasonTag, currentStepId, status, or mixed batches are rejected Forbidden: - Wholesale metadata replacement (must use sub-paths) - Analytics totals (totalCreditsUsed, creditsUsed, analyticsExtracted, etc. — anything not in the allowlist) - Identity fields, executionContent, completedAt, terminal-status writes outside the metadata.executionName exception Audit: each patch appends an entry to metadata.adminPatchLog with { actor, apiKeyId, reason, diffs, timestamp }. This is the §8.1 short-term storage location — sufficient for the exception-only use case. Returns: { patched, dryRun, auditId, diff, record } Requires write access when connected with OAuth.

Surgically edit a timeline's eventSummary, pending approval eventContent, or metadata fields without rerunning the upstream step. Terminal eventSummary-only relabels do not require confirmTimelineId; other terminal repairs require exact-ID confirmation. EXCEPTION-ONLY tool. Use cases: - Repair a malformed legacy/non-preview pending timeline that the regular approval editor cannot handle - Relabel a terminal timeline's eventSummary so the timeline row matches confirmed outcome, similar to metadata.executionName relabels on executions - Update metadata.pendingReasonTag for UI annotation - Recover a failed timeline back to pending (status transition: failed → pending) - Repair corrupted eventContent on a completed/approved/rejected terminal timeline after an incident, only when rerun/retry would duplicate side effects or lose canonical output DO NOT use for normal pending approval changes. Edit a healthy _previewApproval draft in place through the approval card or run-side agent; do not rerun it merely to change copy, recipients, dates, links, or media. This admin tool exists for incident response outside that regular contract. Required: - API key with admin:patch scope (Stage 2 — without it returns 403 FORBIDDEN_SCOPE) - reason: non-empty string (≤500 chars), persisted in the audit row - expectedUpdatedAt: timeline.updatedAt from a fresh read — guards against lost-update races - confirmTimelineId: required for terminal records except eventSummary-only relabels; must be the exact timeline ID being patched Allowed paths (any non-terminal status): - eventSummary - metadata.pendingReasonTag Allowed paths (status === 'pending'): - eventSummary - eventContent (wholesale replace; reserved keys _* rejected) - eventContent.email.subject | body | bodyType | to | cc | bcc - eventContent.<any> (any AI-output field, except _*-prefixed reserved keys) - metadata.pendingReasonTag - status (pending → completed) Allowed paths (failed status): - status (failed → pending) Allowed paths (terminal without confirmTimelineId): - eventSummary only Allowed paths (terminal + confirmTimelineId exact timeline id): - eventSummary - eventContent and eventContent.<any>, except reserved keys and provider send-result fields - eventContent.email.subject | body | bodyType | to | cc | bcc - metadata.pendingReasonTag Forbidden: - Any path containing an underscore-prefixed segment (_timelineId, _metadata, _pointer, _continuation, etc. — runtime-internal markers) - Terminal timeline writes except eventSummary-only relabels, unless confirmTimelineId exactly matches the target timeline id - Identity fields, provider send results (sendResult/messageId/threadId/sentAt/postId/postUrl/commentId/mediaId/permalink), audit fields Returns: { patched, dryRun, auditId, diff: [{path, before, after}], record } On error: { error, code, path? } — codes: FORBIDDEN_SCOPE | FORBIDDEN_PATH | FORBIDDEN_TRANSITION | INVALID_VALUE | NOT_FOUND | CONCURRENCY_CONFLICT | STATUS_MISMATCH | PRECONDITION_FAILED Requires write access when connected with OAuth.

Pause an active agent. Routines attached to the agent stop running until the agent is resumed via activate_agent. Requires write access when connected with OAuth.

Pause a routine (status → paused). The routine will not run until resumed. Requires write access when connected with OAuth.

Preview a deterministic n8n import from JSON. Returns: - normalized import hash and IR - mapped step graph - unsupported nodes + remediation - warnings/risks - draft workflow build contract and compiler readiness summary This is a read-only preview and does not create any workflow.

Preview the shared paused-package plan for a Source -> KG -> Process WorkspaceUseCase kit. Use this before creating multiple related workflows for sourcing, intake, monitoring, business intros, or other shared-tail use cases. The server compiles the typed kit into a workspace-local compatibility package and returns its exact signed preview. Review and preserve that preview for provision_use_case_kit. This is read-only: it does not create records, workflows, KG rows, sends, provider writes, routine runs, or spend credits.

Produce the exact signed, non-mutating install plan for a registered workspace package. Eligible existing assets can be reviewed with fingerprint-bound adopt or preserve resolutions. Adoption is additive: the existing identity and workspace-owned settings are preserved. Preview never applies or changes the workspace. The preview is bound to the workspace, designation, package version, manifest, authoritative snapshot, resolutions, operations, and approval reference. Review it before any apply.

Promote the draft snapshot to live. This overwrites the live pipeline config with the draft contents, then deletes the draft snapshot. A pre-promote snapshot is saved automatically so the previous live config can be restored if needed. Requires write access when connected with OAuth.

Deprecated compatibility alias for applying a previously reviewed Source -> KG -> Process WorkspaceUseCase package. Use preview_use_case_kit first, review the deterministic plan, and pass back its exact signed preview only after the user approves those writes. The server recompiles the typed kit and rejects any changed payload, stale preview, collision, or mismatched binding. This delegates to the shared paused package lifecycle; it does not run workflows, insert KG rows, send messages, write to external providers, trigger routines, make approval decisions, or spend credits. Requires confirmToken exactly "PROVISION_USE_CASE_KIT" and the exact preview object. Requires write access when connected with OAuth.

Change the status of a workflow (publish, pause, or archive). Valid transitions: created/draft -> live, live -> paused, paused -> live, any -> archived. Use "live" to publish a draft workflow so it can be executed. Requires write access when connected with OAuth.

Publish a draft workspace-created skill. Requires write access when connected with OAuth.

Traverse Knowledge Graph edges by entity name and/or relationship type. Returns edges with source/target node IDs, relations, scores, and metadata. Use this to explore deal relationships, investor-startup connections, and scoring edges. Gracefully returns empty results if the Knowledge Graph is not configured. The `source_node_id` and `target_node_id` values correspond to knowledge row IDs. Use `get_knowledge_rows_by_ids` as the follow-up call to fetch full row data for those IDs. Example: `query_kg_edges({ entityName: "Teresa Abecasis", relationshipType: "SCORED" })` → collect `targetNodeIds` → `get_knowledge_rows_by_ids({ rowIds: targetNodeIds })`.

Read the full output from a previous workflow step. Use this tool when a step output was deferred as a tool reference in a prompt — you will see a block like: [Tool Reference: stepName] Size: 24.3KB | Fields: name, emails, organizations, ... To read full data: call read_step_output(executionId="...", stepId="...") Pass the executionId and stepId shown in that block. Optionally narrow the response with 'field' (dot-notation path) or 'select' (list of top-level fields to include).

Recall a specific memory by key. Returns the stored value if found. Use this to retrieve previously stored facts, insights, preferences, or outcomes. **KG-First:** Call this BEFORE generating AI-step prompts that reference workspace-specific strategy (ICP, thesis, rubric). If the content exists as a memory, reference it at runtime via the workspace_memory builtin tool rather than pasting it into the prompt template.

Resume only the pending assets from an incomplete package installation using a fresh exact signed preview and confirmation. Recovery uses the same paused lifecycle and requires workspace:packages:apply plus workspace owner or ADMIN authority. Requires write access when connected with OAuth.

Terminally reject one pending AgentApprovalRequest in the current workspace. Requires the exact approval request ID, a non-empty operator comment, and confirm=true. This never approves, sends, executes, retries, continues, or invokes a provider. A prior terminal decision is preserved and cannot be overwritten. Requires write access when connected with OAuth.

Remove a step from a workflow with optional next-pointer rewiring. When rewireNext is true (default): steps that pointed to the removed step are rewired to the removed step's next target. Entry condition criteria referencing the removed step are also cleaned up. Respects draft snapshot routing for live workflows. Requires write access when connected with OAuth.

Remove one item from a step array path by `index` or exact `match` value. Provide exactly one of `index` or `match`. Prefer this over sending a hand-built shorter array via raw `update_step` when you only need to drop one entry. Returns the same shape as `update_step`. Requires write access when connected with OAuth.

Preferred for dictionary-shaped step fields where keys are user data. Merges the provided object keys into the existing dictionary at `path` without dropping sibling keys. Internally: `get_step` → merge → `update_step` with a safe top-level `replace`. Canonical paths: - `stepInputData.fieldUpdates` - `pipelineStepPrompt.responseStructure` - `knowledgeSync.fieldMapping` Use raw `update_step` only when you intentionally want a wholesale dictionary rewrite or a multi-path batch edit. Returns the same shape as `update_step` (merged step, diff, warnings, validation, draft metadata). Requires write access when connected with OAuth.

Set one nested step path to `value` while preserving sibling fields. Preferred for nested config edits such as `renderer.config.layout` where a naive `update_step` patch would wipe sibling config keys. Internally reads the step, clones the owning top-level field, applies the path write, then calls `update_step` with `replace` on that top-level field. For dictionary key merges (`fieldUpdates`, `responseStructure`, `fieldMapping`), prefer `replace_step_dictionary` instead. Returns the same shape as `update_step`. Requires write access when connected with OAuth.

Rerun or retry any step in a workflow execution. Pass the timelineId — the backend derives everything else (workflowId, executionId, stepId) automatically from the timeline record. Works for both retrying failed steps and rerunning any step regardless of status. Bypasses cache by default (forceWithoutCache: true). To find the timelineId: use list_timelines to browse step execution records for an execution, or get_execution which includes recent timeline IDs. Requires write access when connected with OAuth.

[Deprecated — use rerun instead] Rerun a specific step in a workflow execution, regardless of step status (pending, completed, failed, skipped). Works on any step and uses the current live pipeline config. Bypasses cache by default (forceWithoutCache: true). If no timelineId is provided, the most recent timeline for that step is automatically detected and rerun. Requires write access when connected with OAuth.

Check whether a workspace already exists for a firm, slug, domain, owner email, or idempotency key. This is read-only. Agents should call this before create_workspace so existing firm workspaces are reused instead of accidentally creating duplicates.

Restore rows from a snapshot into a Knowledge Data list without wiping computed fields. Modes (computed fields like scores and enrichment are always preserved): - "merge-restore" (default) — for rows that already exist: shallow-merges snapshot fields back in (existing computed fields survive; snapshot fields win on conflict). New rows are inserted. Use this as the rollback path — it undoes a bad migration without destroying downstream work. - "append" — inserts only rows not already present; never touches existing rows. Use this when restoring into a new list or when you want to add missing rows without altering anything. The target listKey may differ from the snapshot's source listKey — this enables cross-list cloning. If the target list doesn't exist it will be auto-created using the snapshot's schema. Returns: { restored (new rows inserted), merged (existing rows updated), skipped, errors[] }. Requires write access when connected with OAuth.

Restore a workflow to a previous config snapshot. Use list_snapshots first to find the snapshot ID. This will revert the workflow's steps, context, name, description, goal, and style to the state captured in the snapshot. Requires write access when connected with OAuth.

Resume a paused routine (status → active). Routines are paid autonomous features; free-tier workspaces cannot resume them. nextRunAt is reset to the next occurrence of the routine's interval from now. Requires write access when connected with OAuth.

[Deprecated — use rerun instead] Retry a failed step in a workflow execution. If no timelineId is provided, the most recent failed timeline is automatically detected and retried. This re-runs the failed step and continues the workflow from that point. Requires write access when connected with OAuth.

Review submitted builder work as a business agent; set accepted, needs_changes, or closed and optionally attach thumbs-up/down quality signal. Requires write access when connected with OAuth.

Revoke/delete share by share id. Requires write access when connected with OAuth.

Search memories by natural language query and/or category. Returns matching memories sorted by confidence. Use to find relevant stored knowledge. **KG-First:** Call this BEFORE generating AI-step prompts with business-specific content to check whether workspace strategy (ICP, thesis, rubric) is already stored. Reference found memories at runtime instead of inlining them in prompt strings.

Assign the agent that handles inbound conversations on a default-routed channel. Slack, WhatsApp, Signal, and Telegram use defaultAgentId routing. Email does not: email routes by per-agent address and agent responses include the derived address in their channels array. Use list_channels to inspect current assignments and list_agents to find valid agent IDs. Use configure_channel for more granular updates (enable/disable, allowedSenders, outbound email approval, etc.). Requires write access when connected with OAuth.

Update workspace-wide channel defaults (rate limits, timeouts, tool mode). These settings apply across all enabled channels: - maxSessionsPerDay: Cap on inbound chat sessions per day (default 100) - sessionTimeoutMinutes: Auto-close sessions after inactivity (default 60) - toolMode: 'all' (all tools available) or 'mcp' (MCP-only tools) Requires write access when connected with OAuth.

Pin or unpin a workflow output page on the workspace home/sidebar. The API validates that the workflow belongs to this workspace and that the output page pathname exists on the workflow. Pin sparingly: only use workspace-level pins for recurring reports, dashboards, canonical results lists, or other pages users should reach directly from the workspace home/sidebar. Requires write access when connected with OAuth.

Set the Knowledge Text key that contains the durable goal brief for one use case. This changes only the typed pointer. It does not edit Knowledge Text content, run workflows or routines, call providers, spend credits, decide approvals, or perform external writes. The server reuses the UI validator and writes an actor-attributed audit row. Requires write access when connected with OAuth.

Set the default finish line to one milestone already declared by the onboarding-goal contract. This changes desired goal configuration only. It cannot mutate runtime milestone evidence or mark work complete, and it does not run workflows, trigger routines, call providers, spend credits, make approval decisions, or perform external writes. Requires write access when connected with OAuth.

Set one typed desired approval policy on an existing onboarding-goal requirement. This changes desired policy only; it does not change live workflow, agent, channel, or routine enforcement and does not approve or execute any action. Weakening a send, write, or delete safeguard requires confirm=true. The server reuses the UI validator and writes an actor-attributed audit row. Requires write access when connected with OAuth.

Set the primary CRM reference used by one onboarding goal. This changes only the typed CRM reference. It does not connect the app, change credentials, write CRM data, run workflows or routines, call providers, spend credits, or decide approvals. The server reuses the UI validator and writes an actor-attributed audit row. Requires write access when connected with OAuth.

Set a Good fit, Not a fit, or Needs review assessment only after an explicit user instruction. This stores structured use-case memory for the exact record. It does not run workflows, trigger routines, call AI/providers, approve or reject pending work, write CRM data, mutate the source record, or spend credits. Free-form comments are untrusted evidence and are never promoted into prompts or scoring policy by this tool. Requires write access when connected with OAuth.

Create or get a share URL for an execution. Requires write access when connected with OAuth.

Capture a full point-in-time backup of a Knowledge Data list. Returns all rows with their IDs, rowData, status, createdAt, and updatedAt as inline JSON. Also includes the list schema (fields, userKeyField) so the snapshot is self-contained. Use before any risky migration, canonical-key reshuffle, or schema change. The returned snapshot object can be passed directly to `restore_knowledge_list_snapshot` to roll back. Supports lists up to 5 000 rows (inline JSON). Larger lists are not yet supported. Requires write access when connected with OAuth.

Start a workflow execution. Optionally provide input data that maps to the workflow's input page fields. For example, if the workflow expects "company_url", pass: { input: { company_url: "https://..." } } Returns executionInputId for the submitted input/run record. It may also return executionId when the async PipelineExecution row is already available. Use only executionId with get_execution/list_timelines/get_timeline. If executionId is absent, call list_executions and match pipelineExecutionInputId to the returned executionInputId; the matching row's id is the executionId. Mock control: by default, steps that have mock data configured (`step.mock.enabledByDefault`) will return that mock data and consume zero credits. Pass `useMocks: false` to force a real run that ignores mocks for every step. Pass `useMocks: true` (or omit) to keep the workflow's default mock behavior. Requires write access when connected with OAuth.

Stop an active workflow execution. Works on executions with status "running", "pending", or "started"; requires a human-readable reason persisted in execution metadata. Requires write access when connected with OAuth.

Store a persistent memory. Memories survive across workflow executions and can be recalled later. Categories: fact (known truth), insight (pattern/learning), preference (user preference), outcome (result to track). **KG-First:** Use this to seed workspace-specific strategy content (ICP criteria, scoring rubric definitions, investment thesis, brand voice) BEFORE building the workflow steps that need it. Once stored, the AI step references it at runtime via the workspace_memory builtin tool — never hardcoded in the prompt template. Requires write access when connected with OAuth.

Submit completed builder output refs and a summary. The work item moves to submitted for business-agent review. Requires write access when connected with OAuth.