"n8n workflow automation platform" matching MCP tools:

• toggle_automation

  MisarMail MCP Server

  Activate or pause one automation workflow. This is consequential in one direction: ACTIVATING starts enrolling contacts, which means real emails begin going out on the workflow's schedule without further confirmation. Pausing stops new enrolments. Read the workflow with get_automation first so you know what activating will actually send. Contacts already part-way through a paused workflow are held rather than dropped, so pausing is not a cancellation. Safe to repeat. Requires an API key.

  Connector

• submit_response

  Ansvar: EU Compliance & Legal Intelligence

  Provide an answer to the current step in a compliance workflow. Use this when someone provides information requested by the workflow, such as 'our system processes health data' or 'we use AES-256 encryption'. The workflow engine validates the response and advances to the next step. Pass user_acknowledged=true only after the user has supplied the fields listed in user_provided_fields. evidence_references accepts document UUIDs, doc:// segment URIs, or regulatory URLs. For an unattended gate, pass approved_by='auto' and leave user_acknowledged=false so the report does not misrepresent automation as human review. approved_by accepts only 'auto'; human review is asserted via user_acknowledged, never by naming an approver.

  Connector

• taskbounty_security_check

  TaskBounty

  Scan a PUBLIC GitHub repo for GitHub Actions + CI security/maintenance hygiene before launch — ideal for apps built with Lovable, Bolt, Replit, Cursor, or v0 ("is my AI-built app safe to ship?"). Returns a safe summary: findings by category with counts, an unlisted report URL, and fix options. SCOPE, honestly: it checks GitHub Actions workflow + update-automation hygiene only — it does NOT check exposed secrets, auth, payments, webhooks, or runtime behavior, which need a manual review. No API key required. For PRIVATE repos, tell the user to run `npx taskbounty-check .` locally so their source never leaves their machine.

  Connector

• unpublish_workflow

  Dreamlit

  Use after explicit user intent to unpublish a Dreamlit workflow. Side effect: disables live triggers or schedules for that workflow and stops future automated sends. Returns updated workflow status and app URLs. Do not use for deleting drafts, canceling one broadcast run, or editing workflow content.

  Connector

• get_platform_info

  venumark

  What VenuMark is (the food vendor application and compliance platform for Florida events), how the workflow runs, current pricing tiers, and which tier fits an organizer. Use when someone asks about running vendor applications, pricing, or whether VenuMark fits their event.

  Connector

• list_collections

  Skill of Skills

  The curated buyer-intent collections (e.g. mcp-servers, testing-qa, browser-automation). Use get_collection for the ranked tools inside one.

  Connector

• ios_tap

  Robot Actions — Remote Device Control

  Tap at (x,y) on an iOS device screen — the FALLBACK for when an element has no usable label. Prefer ios_tap_by_label (taps by accessibility label via the automation session, no coordinate math, works even on zero-area elements) whenever the target has a name in ios_page_source. Coordinates here are in physical screen points and must come from ios_page_source (the authoritative source), NOT eyeballed from a screenshot. Requires an active iOS automation session.

  Connector

• ios_navigate_url

  Robot Actions — Remote Device Control

  Navigate Safari to a URL on an iOS device via the automation session (address-bar type + submit), then VERIFY the navigation actually landed via the Web Inspector — so it never falsely reports success. For Safari, prefer ios_safari_navigate (CDP-based, also cold-opens Safari). Requires an active iOS automation session (auto-starts if needed).

  Connector

• ios_crash_analytics

  Robot Actions — Remote Device Control

  List crash reports on an iOS device with aggregate analytics (total, per-app, per exception type, per-day timeline). Telemetry and in-house automation processes are excluded. Use ios_crash_detail with a returned crash id for the full log. No automation session required.

  Connector

• submit_meta_council_feedback

  Meta Council

  Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface. Platform feedback only: do NOT use this for anything about your own business, customers, deals, invoices, or other data Meta Council manages on your behalf — use the relevant business tool for that instead (e.g. create_deal, create_invoice). Use it the moment a tool result, council run, or workflow falls short. Stored per-user and visible only to platform admins — the response returns an id + acknowledgement and submissions cannot be read back. Include machine context (tool name, session id, model) in the context object.

  Connector

• await_decision

  Hatch

  Create a human-in-the-loop review on the live artifact. Default options: Approve / Request changes / Reject. Reviewers see a Review required chip → modal. Request changes is non-terminal: webhook or poll returns changes_requested, then call continue_decision after regenerating. Optional timeoutSeconds and maxIterations (default 5). If the page has interactive controls (sliders/forms), the hatch HTML MUST expose window.__VR_HITL_GET_SETTINGS__ so the review can attach those assumptions as JSON. When the user integrates n8n, Temporal, CI, or any external workflow, pass webhookUrl (MCP opens the review; the platform POSTs each transition to that URL — prefer webhook over poll_decision for automation). See PARTNER-WEBHOOKS.md for event payloads.

  Connector

• list_automations

  MisarMail MCP Server

  List automation workflows on the account — welcome series, re-engagement, drip sequences — with their status and enrolment counts. Use it to see what is running before adding another workflow that might overlap, and to find an automation id for get_automation or toggle_automation. Listing does not reveal the individual steps; get_automation does that. Reads only; nothing is activated, paused, or enrolled. Requires an API key. An automation may exist while inactive, so read the status rather than assuming a listed workflow is sending.

  Connector

• get_automation

  MisarMail MCP Server

  Get one automation workflow in full: its trigger, every step with its settings, and current enrolment counts. Use it to understand exactly what an automation will do to contacts before activating it — the step list is where sends, waits and branches become visible. For the list of automations, use list_automations; to start or pause one, toggle_automation. Reads only; reading a workflow does not enrol anyone or trigger a step. Requires an API key. An automation can be defined but inactive, so check its state rather than assuming it is running.

  Connector

• ios_tap_hid

  Robot Actions — Remote Device Control

  Tap at (x,y) via the direct input path (no automation session needed). Coordinates are iOS screen points (same frame as ios_page_source). Single-contact only. Prefer ios_tap for normal automation; use this to force HID or when the automation session is unavailable. Returns "no HID available" on iOS 17.x / no-tunnel.

  Connector

• ios_set_location

  Robot Actions — Remote Device Control

  Set the iOS device's GPS location for testing location-aware apps. Works on physical devices (iOS 16.4+) via the bundled iOS automation agent's simulated-location route. Coordinates persist until the device reboots or ios_clear_location is called. PREREQ: On the device, grant the iOS automation agent app Location Services permission (Settings → Privacy & Security → Location Services → automation runner → While Using App). Without this, the simulated value is cached server-side but apps on the device still see zero coordinates. SCOPE: only affects apps that read CoreLocation (CLLocationManager, Safari navigator.geolocation). Does NOT affect apps using IP-based geolocation, Wi-Fi/cell-tower triangulation, or anti-fraud detection paths.

  Connector

• federation_catalog_agents

  ComOS Federation

  Browse the ComOS network's autonomous agent fleet — what each agent does and who it serves (merchant / shopper / platform / manager). Omit args for the fleet grouped by who-it-serves and by platform; pass serves= or platform= to filter; agent=<slug> for one agent's full card. Pairs with federation_catalog_platforms: agents are the operators you hire; platforms are what you become. Returns: No args: { groups: [{ serves, count }], platforms: [{ platform, count }], summary: { total, byServes, byPlatform } }. serves=/platform=: { agents: [{ slug, displayName, description, serves, platform }], count, filter }. agent=<slug>: { agent: { slug, displayName, description, serves, platform, repo } }. Example: call federation_catalog_agents with arguments {}.

  Connector

• describe_assessment

  TEK BOSS Small Business AI Strategy Assessment

  Use this read-only tool when a business owner asks "How can AI help my business?", "Where do I start with AI?", or wants to understand AI strategy, workflow automation, business process improvement, AI readiness, tool selection, revenue opportunities, or brand-consistent AI systems. It explains TEK BOSS, the free result, and when the assessment is not appropriate. It never retrieves customer data.

  Connector

• n8n_get_workflow

  N8n

  Get one workflow's detail by id from your n8n instance — name, active state, node list (which integrations it uses), tags, timestamps. Get the id from n8n_list_workflows. Requires your instance_url + n8n API key (_apiKey).

  Connector

• get_guide

  Canvs

  Returns guidance on diagram-creation workflow and tool selection: how to choose between Mermaid and manual element creation, and the recommended iteration workflow. Consult before building complex diagrams.

  Connector

• dispatch_social_listening_researcher_async

  Heista

  Dispatch to the SOCIAL LISTENING RESEARCHER — multi-platform community-signal interpretation. Use for: "what are practitioners saying about X across platforms / what jargon is emerging in field Y / what is the cross-platform discourse around brand/topic Z". Treats T3 community sources as primary data, distinguishes cross-platform patterns from single-platform noise. ≥3 platforms sampled per brief. Returns: Signal map (Signal / Platforms / Volume / Sentiment + recency) + Per-platform evidence trail + Cross-platform vs single-platform classification + Confidence flag + Sources. NOT for: single-source thematic work (use dispatch_qualitative_researcher) / numerical sentiment effect sizes (use dispatch_quantitative_researcher). ASYNC version: returns { job_id } immediately, the specialist runs durably on a Vercel Workflow (no 300s timeout). Use this version when the specialist is expected to take >90s. Call get_dispatch_result(job_id) periodically (respect wait_ms_hint in the response) until status === 'completed' or 'failed'. Idempotent: same brief + same org reuses the same job_id, so retries don't fan out duplicate runs.

  Connector