"Automating Design and Deployment of n8n Workflows" matching MCP tools:

• confirm_service_setupA

  AnkraB

  Confirm a prepared managed-service review and start its deployment (step two of `ankra services setup`). The digest must be the one prepare_service_setup returned: a plan that changed since, or that expired, is refused. Starting the deployment is not proof the service is ready; follow it with get_service_instance. Requires applications.deploy.

  ConnectorOAuth

• get-create-design-async-jobA

  CanvaB

  Gets the status and result of a design generation job started by create-design. Pass the job_id and continuation_token from the previous create-design or get-async-job response. While the job is still running, wait the number of seconds the response's polling_policy.wait_seconds gives, then poll again with the same job_id and the updated continuation_token. Never poll sooner than that: it returns the same answer and the design arrives no earlier. Follow the polling_policy.instructions in every response, and relay them to the user while they wait. When the job completes, share the design link with them. When the completed response carries design.print.is_printable as true, and you are replying in text alone — no UI surface of your own rendering the design — then alongside the design link tell the user they can also order this design as a physical print with Canva Print and share design.print.print_url. Otherwise say nothing about printing: when print is absent or is_printable is false, there is nothing to do and nothing to relay. Never tell the user a design cannot be printed.

  ConnectorOAuth

• get-create-design-async-jobA

  Canva MCPB

  Gets the status and result of a design generation job started by create-design. Pass the job_id and continuation_token from the previous create-design or get-async-job response. While the job is still running, wait the number of seconds the response's polling_policy.wait_seconds gives, then poll again with the same job_id and the updated continuation_token. Never poll sooner than that: it returns the same answer and the design arrives no earlier. Follow the polling_policy.instructions in every response, and relay them to the user while they wait. When the job completes, share the design link with them. When the completed response carries design.print.is_printable as true, and you are replying in text alone — no UI surface of your own rendering the design — then alongside the design link tell the user they can also order this design as a physical print with Canva Print and share design.print.print_url. Otherwise say nothing about printing: when print is absent or is_printable is false, there is nothing to do and nothing to relay. Never tell the user a design cannot be printed.

  ConnectorOAuth

• create_webhook_endpointA

  Reach MCPA

  Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=<unix>,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only. Use when the user wants to react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code; needs an https URL they control. Not for the model to call itself.

  ConnectorAPI key

• create_webhook_endpointA

  Reach MCP — LinkedIn for AI agentsA

  Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=<unix>,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only. Use when the user wants to react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code; needs an https URL they control. Not for the model to call itself.

  ConnectorOAuth

• workflows_designA

  9botA

  Discovers capabilities and creates, composes, edits, versions, validates, or simulates Workflow definitions. Use it for design rather than execution; use workflows_connections_manage for accounts and workflows_execute for publishing or activation. New Workflows remain inactive unless explicitly authorized, and visual layout does not change execution. Simulation and preview do not prove external delivery. For a preview, set input.preview=true; preview never applies the mutation. When confirmation is required, repeat the same operation and parameters with the returned input.confirmation_id.

  Connector

  Destructive

  OAuth

• system_defaultA

  blink artifactB

  Set (or with null clear) your default design system. New slides, design and dashboard artifacts get it installed automatically; html only when you pass system to publish_html. system is the id of a design system you can read, or null. Returns { default: { id, title } | null }.

  ConnectorAPI key

• searchA

  developer-toolkit-mcpA

  Search the AI Developer Toolkit documentation: 1100+ guides on Cursor, Claude Code and OpenAI Codex, covering setup, agent workflows, hooks, MCP, testing, CI and deployment, in English and Polish. Returns at most 10 ranked results, each with a short snippet rather than the article text; an empty list means the corpus has nothing on the topic. Pass a result id to `fetch` for the full text.

  ConnectorNo auth

• list_destinationsA

  SignalRavenA

  List where your signals are delivered — Slack channels, webhooks, Google Sheets, n8n, Clay and Notion — with each destination’s health and recent failure state. Connection settings (URLs, tokens) are never returned.

  ConnectorOAuth

• execution_explainA

  AutomateLab n8n MCPA

  Diagnose a failed or surprising n8n execution. Paste the execution JSON (from the n8n UI 'Show details' or `GET /executions/:id?includeData=true`); returns a per-node summary highlighting nodes that returned 0 items, unresolved `={{ ... }}` expressions, errors with hints, and LLM token usage. Hits the most common debugging pain point: items 'silently disappearing' between nodes. Deterministic, rule-based.

  ConnectorNo auth

• design-it-twiceA

  ClairvoyanceA

  Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design something twice, or before committing to any significant design of classes, modules, APIs, or architecture. Also use when asked how to structure or architect a feature, or when writing the design or alternatives section of an RFC, design doc, or ADR. Not for judging strategic vs. tactical investment in existing code (use strategic-mindset) or whether a change degrades design (use code-evolution).

  ConnectorNo auth

• load_skillA

  FormstepA

  Load a domain-knowledge skill — themes, settings, analytics, logic-rules, editing-flows, question-types, etc. Returns markdown reference content. Use when the task touches a domain whose conventions or constraints are not obvious from the surrounding tools. For loading additional MCP tool catalogs (deferred tools by bundle name) use `load_tools` instead. Available skills: - toon-format: TOON format reference for reading and parsing form document structure - question-types: All question types with parameters, validation, and when to use each - logic-rules: Conditional logic conditions, actions, patterns, and examples - editing-flows: Editing workflows, node chaining, batch operations, and best practices - form-best-practices: Form design best practices for question design, ordering, and type selection. - analytics: Form analytics interpretation, metrics, and actionable insights - form-settings: Form configuration options, security, notifications, email customization, and data retention - form-themes: Form visual theming system — schema, constraints, design guidelines, and examples - requests: Requests: asking named people to fill a form — field keys, prefill shapes, building the form in the same call, delivery, callbacks, polling

  ConnectorOAuth

• test-and-repair-automation-workflowA

  GigSoul x402A

  Validate and repair an n8n workflow JSON before production. static: deterministic plus model checks of nodes, connections, credentials, expressions, reachability. simulated: synthetic dry run with safe fixtures. repair: minimal RFC 6902 JSON Patch plus a replay fixture, re-validated in-worker. Returns PASS/FAIL/REVIEW with exact node and field, stable reason codes, and an evidence packet. n8n only. Put a JSON string in query: {"mode":"static|simulated|repair", ...}. Price by mode: static $0.10 (default if mode is missing or the JSON is unparseable), simulated $0.50, repair $2.00. The payment challenge reflects the mode you send. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• deployments_listA

  SceneplaneA

  List every deployment this account can access. The session is bound to one deployment for project/scene/render tools; switch by adding ?deployment=<slug> to the endpoint URL.

  ConnectorAPI key

• portal_evm_get_contract_deploymentA

  SQDA

  Locate the create trace and parent transaction that deployed a specific EVM contract address within a bounded window. COMMON USER ASKS: - Find BAYC deployment - Find recent deployment - Find deployment from known range FIRST CHOICE FOR: - who deployed this EVM contract - when was this contract deployed - what deployment transaction created this contract WHEN TO USE: - You need the deployer, deployment block, deployment timestamp, or deployment transaction for an EVM contract. - You can provide a starting block/time window, a contract address, or a supported well-known contract alias such as BAYC/Bored Apes. - You want a deployment lookup instead of general contract activity. DON'T USE: - You need all activity for a contract after deployment. - The contract is old and no block/time hint is available; provide from_block or from_timestamp first. EXAMPLES: - Find BAYC deployment: {"network":"ethereum-mainnet","contract":"bored apes","from_block":12000000,"to_block":13000000,"scan_order":"earliest"} - Find recent deployment: {"network":"base-mainnet","contract_address":"0xabc...","search_depth_blocks":100000} - Find deployment from known range: {"network":"ethereum-mainnet","contract_address":"0xabc...","from_block":17000000,"to_block":17100000,"scan_order":"earliest"}

  ConnectorNo auth

• workflow_libraryA

  conductorC

  List all available predefined workflows with descriptions and step counts.

  ConnectorNo auth

• get-statusA

  mcpA

  Get the current deployment status for a project, including the live URL (https://{slug}.sota.io), detected framework, and recent deployment history. Deployment statuses: pending (queued), building (build in progress), built (image ready), deploying (starting container + health checks), running (live and healthy), failed (build or health check error), stopped (replaced by newer deployment). Use this to verify a deployment succeeded after calling deploy.

  ConnectorNo auth

• create-design-from-candidateA

  CanvaB

  LEGACY-ONLY — DO NOT CALL WHEN create-design IS AVAILABLE. If create-design is in the tool list, you MUST NOT call this tool. Call create-design instead. BRAND EXCEPTION: create-design cannot apply a brand kit or base a design on a brand template. When the user asks for an on-brand design — their brand kit, their brand colours, fonts or logo, or a brand template to base the design on — call this tool instead of create-design. All instructions below apply when create-design is absent from the tool list, and whenever the request is an on-brand one. A failed create-design call does not make it unavailable. Create a new Canva design from a generation job candidate ID. This converts an AI-generated design candidate into an editable Canva design. If successful, returns a design summary containing a design ID that can be used with the `editing_transaction_tools`. To make changes to the design, first call this tool with the candidate_id from generate-design results, then use the returned design_id with start-editing-transaction and subsequent editing tools.

  ConnectorOAuth

• analyze_agent_latencyA

  ALPNAI — Agent Performance ToolsA

  Find slow agent workflows and retry overhead before scaling. Supply recorded attempts with task_id, workflow, variant, cost_usd, success and optional latency_ms. Returns P50/P95 of summed recorded attempt durations per task, retry counts, duration coverage and an optional P95 threshold check for each workflow and variant. Missing durations produce null percentiles, not zero latency. This measures supplied durations, not live end-to-end service latency. Free calculation; requires an active ALPNAI agent key; no payment or automatic deployment.

  ConnectorNo auth

• edgegap_get_deploymentA

  EdgegapA

  Read the current status of one deployment, including connection address and ports once it is ready. For a deployment you just created, prefer edgegap_wait_for_deployment — it polls for you instead of making you call this in a loop.

  ConnectorAPI key

• deployment_deleteA

  SceneplaneA

  Delete an EMPTY deployment (owner/admin only). Delete its projects first — a deployment with projects refuses.

  Connector

  Destructive

  API key