mcp-server

Read the status and latest Agentled response for a submitted feedbackId in the current workspace. A null response means the team has not posted a reply yet.

Read and conservatively classify only the exact inbound body behind one already-correlated canonical IMAP replied tracking event. This is not a mailbox browser: the server derives the workspace, mailbox, and Message-ID from the canonical event, reads no attachments or remote content, enforces byte/message caps, suppresses no-reply follow-ups, and never sends a response. The external tool is read-only and does not persist the inspection.

Fetch rows from a knowledge list (paginated, up to 200 per call). Use this to inspect actual data or scan a small list end-to-end. Returns rows with their full rowData, count, totalCount for unfiltered list reads, and nextToken. Pass nextToken from the previous response to fetch the next page. nextToken is null when there are no more rows. When you mention this list back to a human, include the human-readable list name and stable list key when known, not only the key. For targeted lookups by ID use `get_knowledge_rows_by_ids` — it fetches specific rows in a single call (max 200) without scanning the whole list. For entity-relationship queries (e.g. "all deals scored by this investor") start with `query_kg_edges`, then pass the returned node IDs to `get_knowledge_rows_by_ids`.

Fetch specific knowledge rows by their IDs. Returns full row data for each requested ID (max 200 per call). Use this after `query_kg_edges` to load full row data for node IDs returned by the Knowledge Graph. The canonical chain for entity-scoped queries (e.g. "best deals for Teresa Abecasis") is: 1. `query_kg_edges({ entityName: "Teresa Abecasis", relationshipType: "SCORED" })` 2. `get_knowledge_rows_by_ids({ rowIds: <targetNodeIds from step 1> })` This is O(edges for that entity) — independent of total list size — and scales to 10k+ rows without paginating. Note: `source_node_id` and `target_node_id` values from `query_kg_edges` correspond directly to knowledge row IDs for investor/deal entity nodes. Rows not belonging to the workspace are silently excluded from results.

Fetch a text-type knowledge entry by key. Use this to access text-based knowledge like feedback files, notes, or configuration text stored in the workspace. When you mention this text entry back to a human, include the human-readable title/name and stable text key. If no stored title exists, derive a short readable title from the key and still include the key. **KG-First:** Call this BEFORE generating any AI-step prompt that references workspace-specific content (investment thesis, brand voice, ICP description, scoring rubric, etc.) to check whether it already exists. If found, pass it via a runtime read step rather than hardcoding the text inline in the prompt template.

Get one public form link by token/id.

Read one exact durable routine run and a bounded page of its ordered events. This is read-only and does not run, retry, resume, pause, approve, or send anything.

Fetch global scoring history for entities from the Knowledge Graph. Returns past scoring decisions (PROCEED_TO_IC, HOLD_FOR_REVIEW, REPOSITION, SCORED) with DMF scores and dates. Use this for manual exploration and legacy calibration. Workflow scoring prompts should prefer row-level scoring_profile fields or the kg.retrieve-scoring-memory app action when bounded target IDs are available. Returns both structured records and a compact text format for prompt injection.

Get share metadata by share id.

Read the full content of a config snapshot WITHOUT restoring it. Returns the captured `steps`, `context`, `name`, `description`, `goal`, `style`, and `analyticsConfig` under a `config` field, plus snapshot metadata (createdAt, source, label, updatedFields). Use this to inspect or compare an old snapshot against the live workflow without the destructive create + restore + restore dance. No quota cost.

Read a single step from a workflow by step ID. Cheap alternative to `get_workflow` (typically ~1KB vs 50-200KB for a full workflow). This returns the configured step definition only. To debug the actual prompt used in a specific execution, use `list_timelines` then `get_timeline` for that step invocation and inspect `metadata.computedPrompt`. **Use this before editing dictionary-shaped fields** (`stepInputData.fieldUpdates`, `responseStructure`, `knowledgeSync.fieldMapping`, `agent.workers`) when you need the current value for a complex local edit. For common single-key dictionary merges and nested path sets, prefer `replace_step_dictionary` / `replace_step_path` instead of hand-rolling `update_step` + `replace[]`. ## Source resolution - `source: "auto"` (default) — returns the draft step if a draft exists, else live. Matches `update_step`'s routing for live workflows. - `source: "live"` — always reads from the live pipeline, ignoring any draft. - `source: "draft"` — returns the draft step or 404 if no draft exists. Never creates a draft. The response includes the resolved `source: "live" | "draft"` so you know which one you got. ## Response shape ``` { workflowId, stepId, source, step: <PipelineStep>, contextRefs: { inputPagesUsed: ["company_url", ...], // {{input.X}} references found in the step stepRefs: ["fetch", "analyze", ...] // {{steps.X.*}} references found in the step }, draft?: { // present when a draft snapshot exists exists: true, draftCreatedAt, liveUpdatedAt, stale: boolean, // live advanced past draft.createdAt modifiedStepIds: [...], // step IDs differing between draft and live modifiedFields: ["steps", "context", ...] // top-level keys differing } } ``` `contextRefs` tells you which upstream fields the step depends on — useful when you're about to break a downstream chain by editing inputs. `draft.stale === true` means the live workflow has been touched since the draft was created. Promoting will land older values for fields the agent didn't touch in this draft. Recovery: `discard_draft` and re-apply, or `get_draft` to inspect what's pending.

Get allowed fields and minimal JSON examples for pipeline steps. Unknown fields are automatically stripped on save — only fields listed here are persisted. ## Params - `stepType` (optional): filter to one of `trigger`, `aiAction`, `aiActionWithTools`, `appAction`, `agentOrchestrator`, `code`, `knowledgeSync`, `share`, `return`, `milestone`, etc. Omit for the full schema. - `shape` (optional): minimal JSON example for a specific shape. Requires `stepType`. Examples: - `aiAction` shapes: `standard`, `report` (with Config renderer), `email` (composed email with approval). - `aiActionWithTools` shapes: `standard`, `agentic-search` (web_search + workspace_memory). - `agentOrchestrator` shapes: `supervisor` (Agent Team preset). - `share` shapes: `public` (public URL for a report step). - `knowledgeSync` shapes: `standard` (deterministic KG field mapping). - `outputPage` shapes: `standard` — workflow-level output page schema for `context.outputPages` (NOT a pipeline step; edit via `update_workflow_context`). - `inputPage` shapes: `standard` — workflow-level configuration input page schema for `context.inputPages`. ## Response shape ``` { "description": "...", // schema description "fieldCount": <number>, // total fields (scoped to stepType when provided) "groups": [<field groups>], // schema groups (scoped to stepType when provided) "shapes": [<shape examples>] // only when stepType is set } ``` Top-level keys are backward-compatible with pre-v0.11 callers that read `description`/`groups` directly. ## When to call - **Before adding a report step**: `get_step_schema({ stepType: "aiAction", shape: "report" })`. - **Before adding a composed-email step**: `get_step_schema({ stepType: "aiAction", shape: "email" })` — remember to also add an `outreachProfile` input page. - **Before adding an Agent Team**: `get_step_schema({ stepType: "agentOrchestrator", shape: "supervisor" })`. - **Before adding an aiActionWithTools step**: `get_step_schema({ stepType: "aiActionWithTools" })`, then `agentled tools builtins` for the closed `builtinType` list. - **Before adding a code step**: `get_step_schema({ stepType: "code", shape: "standard" })`. Note: only JavaScript is supported — Python will fail at runtime. - **Before writing to `context.outputPages`**: `get_step_schema({ stepType: "outputPage", shape: "standard" })`. Required fields: `id`, `title`, `pathname`, `outputSteps[]` — missing any crashes the workflow detail UI on load. - **Output page selection rule**: keep workflow outputs compact. Select only the 1-3 user-facing result surfaces that match the workflow, such as LinkedIn publishing, X/Twitter publishing, scheduled email/outreach, a report, or a canonical results list. Do not create pages for approval placeholders, "mark sent/published" status steps, or internal plumbing. - **Before writing to `context.inputPages`**: `get_step_schema({ stepType: "inputPage", shape: "standard" })`. Saved values land at sibling `context.<contextKey>`. ## Trigger type guidance Prefer `schedule` (polling) for email intake, document processing, and any workflow where sub-minute latency is not required. Use `app_event` or `webhook` only when the user explicitly requires real-time delivery (e.g. "as soon as", "within 30 seconds"). When in doubt, schedule wins — it is idempotent, supports backfill, and needs no event infrastructure.

Get a single timeline (step execution record) by ID. Returns the full timeline including eventContent (step output), status, metadata, and context. Use this to inspect a specific step's result in detail. To debug the actual prompt used for this step invocation, inspect metadata.computedPrompt. get_step only shows the configured prompt template, not the resolved execution prompt.

Get one workspace use case by stored id, key, or workflowGraphId. Use this as the first inspection step for a specific business goal such as business-intro or front-desk. Read operatingGuides before answering workflow-specific questions or changing linked workflows. The normalized onboardingGoal field is stable desired configuration only; never infer live approval enforcement from it. If agentGuidance.warnings includes MISSING_USE_CASE_OPERATING_GUIDE, state that the operating README is missing and create/update the linked knowledge text before treating the context as complete. This tool is read-only; create/update/provisioning operations remain intentionally separate until the atomic use-case kit lifecycle lands.

Get the normalized onboarding-goal contract and freshly resolved approval enforcement for one WorkspaceUseCase. Use this instead of reading raw config when deciding whether an operation is automatic, approval-gated, disabled, misaligned, or unresolved. This tool is read-only and does not run workflows, trigger routines, call providers, spend credits, make approval decisions, or perform external writes.

Get the current fit assessment for one record in a workspace use case. The response keeps fit assessment separate from sourceOperationalStatus and explicitly reports zero workflow, routine, provider, approval, CRM, and credit side effects. This tool is read-only.

Get full details of a workflow including all steps, context, metadata, and configuration. Also returns hasDraftSnapshot (boolean) and draftSnapshot summary if a draft exists for a live workflow. When available, useCaseContext links the workflow to its WorkspaceUseCase and operating-guide README commands. Read the linked use case and guide before making workflow-specific claims or edits; missing-guide warnings mean context is incomplete.

Get aggregated workflow analytics from persisted snapshots. Use type="business" to retrieve business metrics configured in analyticsConfig, including trackingEvent metrics such as opened/clicked when configured. Use period="lifetime" for all-time totals or period="daily" for a time series.

Get ledger-derived, period-labelled credit usage for a single workflow. Defaults to period=rolling-30-days. Set includeCostDrivers=true for bounded step/model/app cost drivers. Always show the returned period.label/display/start/end with any credit total. Use all-time intentionally because it can scan more ledger rows.

Get workspace company info, current authenticated user, team visibility, and knowledge schema overview. Returns currentUser for the API key owner, company details, active team members when available, pending team invitations when available, and a summary of all knowledge lists with their field definitions and row counts. Use this as a first call to understand what data the workspace has.

Get the workspace company profile and company knowledge text. Returns the company record used for workspace setup plus markdown from knowledge keys company.profile and company.products. Use this when you need the editable company profile rather than the broader workspace context.

Get a concise, ledger-derived workspace credit cost-driver report. Defaults to period=rolling-30-days and includeCostDrivers=true. Returned totals are period-labelled; always show the period.label/display/start/end alongside credit totals. Cost drivers include bounded top workflows, steps, models, and apps. Use all-time intentionally because it can scan more ledger rows.

Get the authenticated workspace's canonical creditSnapshot plus optional period-labelled usage statistics. Returns: - creditSnapshot: schemaVersioned point-in-time balance (plan allowance, monthly remaining, purchased stored/available/unavailable, refresh/renewal dates, unsupported reservation=0, usable credits). Prefer these fields. - currentBalance / monthlyCredits / purchasedCredits / nextCreditResetAt: deprecated flat aliases during migration (monthlyCredits means remaining monthly balance, not plan allowance) - period: exact labelled window for every usage total (label, display, start, end) - periodDays: lookback window for usage stats when applicable - usedThisPeriod: total credits consumed in the labelled period - totalExecutions: number of unique workflow executions in the period - averageCreditsPerExecution: average cost per run - recentUsage: last 20 credit deductions with execution/step context unless includeRecentUsage=false - costDrivers: optional bounded top workflows, steps, models, and apps when includeCostDrivers=true Workspace identity comes only from the API key. Every usage total is ledger-derived and must be shown with its period label. Use creditSnapshot for exact spendable balance; compose usage reporting separately.

Read the authoritative lifecycle and installation bindings for a registered workspace package. This is read-only and does not activate or run installed assets.

Get a workspace-created skill by ID.

Get one saved WorkspaceView by stored id or key. Read agentGuidance before rendering or acting from the view. View reads are safe; action execution must still use the normal approval and side-effect policies.

Create a new Agentled workflow from an n8n JSON import. Behavior: - runs deterministic import preview - creates workflow in preflight draft mode - stores imported contract for review/approval - does NOT auto-apply scaffold Requires write access when connected with OAuth.

Import a workflow from an export JSON into this workspace. Accepts the full WorkflowExport object (from export_workflow) and creates a new workflow with fresh IDs. Associated pages are recreated. Import provenance is recorded in the workflow metadata. Use this together with export_workflow to move workflows between environments. Tip: register separate MCP servers for sandbox and prod, export from one, import into the other. Requires write access when connected with OAuth.

Import a Markdown, SKILL.md, or JSON skill file into a draft workspace skill. This creates one backing workspace AgentFile and then one draft WorkspaceSkill. Imported allowedApps/allowedActions are recommended apps/actions only. Import does not grant those tools, publish the skill, assign it to an agent, run chat/routines/workflows, write providers, send messages, bypass approvals, or spend credits. Use publish_workspace_skill and explicit agent assignment only after reviewing the draft. Requires write access when connected with OAuth.

Inspect the workspace Home tabs and Recent tab configuration, and return the current workspace revision. Returns "tabs": every Home tab in display order (the Recent tab plus one tab per active use case) with its id, kind, label, and isDefault flag, plus "defaultTabId" for the tab Home opens by default. A Recent tab marked "visibleWhenRunsExist" has no stored configuration yet, so Home shows it only once the workspace has runs. Call this before configure_home_recent_tab. The configuration is display-only and inspecting it does not run workflows, call providers, spend credits, or mutate customer data.

Inspect eligibility, installability, blockers, and current lifecycle state for a registered workspace package. This is read-only and reports every side-effect flag. It never installs, runs, activates, connects, calls providers, spends credits, sends, or imports data.

List all files attached to an agent. These include reference documents, knowledge files, and any other files uploaded to provide the agent with context.

List supported agent skill IDs for create_agent, update_agent, create_routine, and update_routine. Use these IDs in skillIds. They are stored internally as enabledSkills, but user-facing copy should say Skills. By default this returns only public user-facing skills. Pass includeRuntime: true only for advanced runtime bundle configuration such as workflow-operator, template-runner, inline-execution, routine-core, or channel-email. The agent-manager and routine-manager skills are control-plane tools for draft goal groups, owner agents, reusable assets, and paused schedules; activation or scheduled autonomy still requires explicit approval and audit.

List all agents in the workspace. Agents are workspace identities with instructions, files, assigned workflows, chat, and optional attached routines for scheduled/autonomous work. Each agent includes a channels array for currently reachable inbound channels: - email appears for every agent when the workspace email channel is enabled, with the derived per-agent address - Slack, WhatsApp, Signal, and Telegram appear only on the agent assigned as that channel's defaultAgentId

List available apps/integrations in Agentled. Returns app names, descriptions, and action summaries. Use this to discover what integrations are available before building a workflow. Common apps: agentled (LinkedIn enrichment, email finder), hunter (email), web-scraping, affinity-crm, specter, http-request. Pass `grep` to filter by keyword — much cheaper than fetching the full catalog when you only want to check a single platform (e.g. `grep: "producthunt"` to answer "is there a ProductHunt app?"). The keyword is matched (case-insensitive) against app id, name, description, and action ids/labels. Always run this before designing any "find / fetch / discover / source" step — falling back to aiActionWithTools + web_search without checking is how agents spend 25 credits per page when a 1-credit native call exists.

List work items eligible for this authenticated builder. Defaults to queued and needs_changes items assigned to the registered builder/API key when available.

List open/stale/submitted builder work items for a business agent by sourceAgentEntityId.

List the workspace's channel integrations and their configuration. Returns each configured channel (email, slack, whatsapp, signal, telegram) with: - enabled: whether the channel is active - defaultAgentId: the agent handling inbound conversations on default-routed channels - inboundAddress (email): workspace address pattern; each agent also exposes its own email in list_agents/get_agent/create_agent - Other non-secret config (team names, channel IDs, phone numbers) Secret credentials (bot tokens, access tokens, signing secrets) are REDACTED in the response. Use this to discover which channels exist before assigning agents to default-routed channels.

List all connected integrations for the workspace. Returns a unified list of connections from all sources: - OAuth connections (via Composio) - API key connections (e.g., Hunter, Affinity CRM) with masked key preview - Native OAuth (social accounts) Each connection shows appId, status, source, and for API keys a masked keyPreview (e.g., "c5a1...5532"). Use this to check which apps are configured before running workflows that depend on them.

List recent executions for a workflow. Returns execution id, pipelineExecutionInputId, status, timestamps. Use pipelineExecutionInputId to match an executionInputId returned by start_workflow when executionId was not available yet.

List all knowledge list schemas with field definitions, row counts, and metadata. Returns detailed information about each list including fields, source type, category, entity config, and KG sync status. Use this to discover what lists exist and understand their structure before querying rows. When you mention knowledge lists or text entries back to a human, include both the human-readable name/title and stable key/id, not only the id. Example: VC Contacts (`gtm_vc_contacts`). **KG-First:** Call this BEFORE generating any AI-step prompt that references business-specific personalization (ICP criteria, scoring rubrics, sector lists, seed lists, etc.) to check whether the content already lives in workspace knowledge. If it does, reference it at runtime via kg.read-list rather than hardcoding it in the prompt template.

List all memories in a given scope. Returns memories sorted by confidence.

List all supported AI models for workflow steps. Returns model ID, provider, display name, tier (mini/standard/max), credit cost, and category. Use the model ID in step.agent.model and the provider in step.agent.provider when configuring AI steps. Example: agent: { model: "claude-5-5-opus", provider: "anthropic" }

List output pages currently pinned to the workspace home/sidebar. Pinned outputs are workspace-level shortcuts to workflow output pages, stored on Workspace.metadata.pinnedOutputs. Use this before changing pins so you can avoid duplicating or removing the wrong shortcut.

List public form links for a workflow. Public URLs use /en/forms/{formLinkId}.

List all routines for an agent. Routines are scheduled tasks that run automatically on a fixed interval (e.g. daily, weekday-morning). Pass the agent's slug (e.g. "dealflow") or ID as `agent_id`.

List config snapshots for a workflow, paginated across all pages (cap 500). Snapshots are automatically captured before every external API update, allowing you to restore a previous configuration. Includes both saved versions and unpublished drafts. Use filter to narrow results: "all" (default, includes drafts), "saved" (no drafts), or "draft" (drafts only). Returns snapshot ID, timestamp, source, and which fields changed.

List timelines (step execution records) for a specific execution. Each timeline represents a step that ran, with its status, output, and metadata. Use this to inspect individual step results, debug failures, or see the execution flow. When sharing a specific timeline/approval/output/failure with a human, use /runs?runId=<executionId>&step=<workflowStepId>; the step value is the workflow step id from these records, not the timeline id. To debug the actual prompt used for a step in an execution, find that step's timeline here, then call get_timeline and inspect metadata.computedPrompt. get_step only shows the configured prompt template, not the resolved execution prompt.

List raw tracking events for a workflow, such as email sent/opened/clicked events. Supports filtering by eventType, executionId, timelineId, channel, and createdAt range. Set aggregate=true to include simple counts by event type, channel, and URL for the returned page.

List current fit assessments for records in one workspace use case. Cleared/Unreviewed records are omitted. This tool is read-only and does not run workflows, trigger routines, call providers, change approvals, write CRM data, or spend credits.