"Understanding Cline Rules Automation" matching MCP tools:

• relm_manage_automationA

  Relm CRMA

  Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's trigger/conditions/actions, delete and recreate.

  Connector

  Destructive

  No auth

• get_node_configsA

  NoClickA

  Manual fallback: returns a node type+operation's config SCHEMA (the fields you can set) — NOT a live node's saved config (use get_node for that). Takes "type:operation" pairs (e.g. ["automation-slack:send_message_to_channel"]). Prefer search_operations(detail_level='full') for intent lookup, or update_workflow(include_configs=true) while building.

  ConnectorOAuth

• search_use_casesA

  The AI Integration HubA

  Search 1,000+ vetted AI use cases by keyword, industry, or business workflow (e.g. 'invoice', 'dental', 'customer support'). Use when someone asks how AI can help their business, wants AI ideas for an industry, or looks for automation opportunities. Also use it to find the slug before get_agent_playbook or run_agent. Returns titles, summaries, and links. Public: no sign-in.

  ConnectorNo auth

• recipe_runsA

  Local MCPB

  Shows the history of past recipe runs and their results (recorded by recipe_run), so you can reuse, compare, or debug an automation. Pass `name` for one recipe's runs, or omit for a compact history across all recipes. Pass `run_id` (with `name`) to get that run in full detail. Newest first.

  ConnectorOAuth

• list_candidatesA

  JobMojitoA

  [Candidates] List the merchant's candidates, filtered by text, activity tab, source, channel, owner, prospect or applicant. To search like the admin's segment builder (tags, positions, steps, status, dates, countries, skills, custom fields...) pass `rules` as an object (or the same JSON as a string) {"match": "all", "rules": [...]}, field ids and values from list_candidate_filters, e.g. '{"match":"all","rules":[{"field":"tag","op":"any","values":["<tag id>"]},{"field":"applied","op":"within_days","value":30}]}' (list operators take `values`, the others `value`); or `segment_id` for a segment's members. Every argument in full, with examples: get_tool_reference.

  ConnectorNo auth

• create_agentA

  WebRun Browser AutomationA

  Create a scheduled agent — a recurring or one-time automation that runs on a timer in a real Chrome browser. Two modes. WORKFLOW MODE: pass workflowId plus a schedule — the platform copies everything else (prompt, starting URL, output contract, model, proxy, policy, files) from the workflow and bakes your variables into the prompt; results and memory stay centralised on the workflow. STANDALONE MODE: omit workflowId and provide name, prompt (a Goal / Ground rules / Stages / Output browsing runbook — see the prompt field description), and a schedule; the connection's environment is used automatically. Ask the user only what it should do and when it should run, in plain language — pick sensible defaults for everything else and state them; never ask about environments or technical settings. Results are delivered to your connected chat and appear in session history.

  ConnectorNo auth

• fetchA

  AI Developer Toolkit documentationA

  Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.

  ConnectorNo auth

• cromanion_set_playbookA

  CromanionA

  Reword a distilled rule, or ask for a fresh distillation. Rules are what the agent learned from real sessions; cromanion_decide approves or pauses them, and this changes what they SAY. Send a ruleId with condition and/or recommendedAction to reword one — ids come from cromanion_config, which also shows rules you have already approved or paused. Send redistill: true instead to distil new rules from recent sessions; they arrive as `proposed` for you to rule on. Rate-limited to one distillation an hour. Needs the decisions permission.

  Connector

  Destructive

  No auth

• delete_contactA

  SendingA

  Permanently delete one contact (by contactId or email): identities, tags, list memberships and automation enrollments go with it. Messages already sent are kept (delivery history), and a suppressed address stays suppressed, so deleting an unsubscribed contact never makes it reachable again. To stop marketing to someone without deleting them, update their consent with upsert_contact instead.

  Connector

  Destructive

  API key

• mcp_crm_automations_createA

  MailzzyA

  Create a new automation DEFINITION for the authenticated user. The new automation is always created INACTIVE (a definition only) — it does NOT run, send, or activate. Use when the user wants to define a new automation by name. Do NOT use to activate, run, or wire the automation's step graph — activation is a separate, later capability and is not available here. Do NOT use to edit an existing automation — use mcp_crm_automations_update. The automation's status cannot be set via this tool. Tenant is bound to the session and cannot be changed via arguments. Automation-level RULES (all optional, and all independent of the step graph — use mcp_crm_automations_set_steps for that): entryConditions / exitConditions / restartConditions are arrays of {type, segmentId, operator, contactFilters, campaignIds, linkUrl} where type is one of added_to_lists, removed_from_lists, contact_in_segment, contact_matches_filters, email_opened, email_clicked, email_unsubscribed; a membership type needs segmentId, contact_matches_filters needs contactFilters, and the email types take optional campaignIds (plus linkUrl on email_clicked). operator is MATCHES or DOES_NOT_MATCH. Pass an EMPTY array to clear a slot; omit the key to leave it unchanged. reentryPolicy is once (a contact runs this automation at most once) or every_time, with reentryWaitMinutes as the cool-down before a contact may re-enter. onDeactivate is continue (in-flight contacts finish) or cancel (in-flight contacts are cancelled when a human deactivates the automation). Returns the created automation projection (id, name, status, rules, version).

  ConnectorOAuth

• affirm_ruleA

  NEXUS AGIA

  Record that a rule was checked against the current state of things (code, data, documentation) and still holds. Rules lose confidence over time and low-confidence rules are queued for review. Affirming resets the rule's staleness clock and restores its confidence to the configured maximum, taking it out of the review queue. It is meant for rules actually verified as correct, not for rules that were merely retrieved or look plausible. Args: rule_id: UUID of the verified rule.

  ConnectorAPI key

• check_hmi_import_csvA

  HMI Import PreflightA

  Check a supplied CSV before importing it into an HMI project. Use tags_csv for a supported FactoryTalk View tag export, digital_alarms_csv for a digital-alarm export, and analog_alarms_csv for an analog-alarm export; each argument is the complete CSV text and may be omitted when that export type is not being checked. The tool validates deterministic import contract rules such as the expected export version marker, record shape, required fields, addresses, alarm severity and analog threshold structure. It returns result (PASS, REVIEW_REQUIRED, or INSUFFICIENT_INPUT), issue_count, a list of issues with code/severity/message and row or record provenance when available, plus a summary by issue code. Use this tool for static import preflight only; it does not connect to any HMI or PLC and does not certify runtime or safety behavior. This is an independent compatibility check, not an official Rockwell Automation service.

  ConnectorNo auth

• check_hmi_import_csvA

  RegEvidenceHub FactoryTalk Import PreflightA

  Check a supplied CSV before importing it into an HMI project. Use tags_csv for a supported FactoryTalk View tag export, digital_alarms_csv for a digital-alarm export, and analog_alarms_csv for an analog-alarm export; each argument is the complete CSV text and may be omitted when that export type is not being checked. The tool validates deterministic import contract rules such as the expected export version marker, record shape, required fields, addresses, alarm severity and analog threshold structure. It returns result (PASS, REVIEW_REQUIRED, or INSUFFICIENT_INPUT), issue_count, a list of issues with code/severity/message and row or record provenance when available, plus a summary by issue code. Use this tool for static import preflight only; it does not connect to any HMI or PLC and does not certify runtime or safety behavior. This is an independent compatibility check, not an official Rockwell Automation service.

  ConnectorNo auth

• edit_task_formA

  MCPBinderA

  Edit an existing active task identified by its UUID or task reference. Prefill a native form with its current title, description, due date and project workflow status, then save only accepted changes. Cancelling makes no change. Requires a host supporting MRTR form elicitation; otherwise use item_update. Accepted task changes may send configured notifications, webhooks and automation actions.

  Connector

  Destructive

  OAuth

• volanea_create_workflowA

  VolaneaA

  Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".

  Connector

  Destructive

  No auth

• volanea_create_workflowA

  VolaneaA

  Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".

  Connector

  Destructive

  No auth

• get_facet_countsA

  Federal RegisterA

  Get document counts grouped by type, agency, topic, or time period. Accepts the same filter conditions as search_documents. Returns aggregated counts without individual document results. Facets: type, agency, topic (categorical) plus daily, weekly, monthly, quarterly, yearly (publication-date buckets, useful for trend lines). Useful for understanding the volume of rulemaking by agency, type, or over time within a date range before drilling into specific documents. presidential_document_type (executive_order, proclamation, memorandum, determination, notice, presidential_order, other) narrows to one kind of presidential document, e.g. executive orders per month. At least one filter (agencies, doc_types, term, pub_date_gte/lte, or cfr_title) is required. An unfiltered facet query returns the entire all-time aggregate. FAR Council counts: facets cannot express "filed by DoD AND GSA AND NASA", and no single agency slug covers FAR documents (OFPP only from about mid-2025; 'federal-acquisition-regulation-system' holds 2 documents ever). Count FAR rules with search_documents(far_council=True, doc_types=[...], pub_date_gte/lte=...) and read its count.

  ConnectorNo auth

• pm_list_reference_dataA

  DutifyA

  List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.

  ConnectorNo auth

• pm_list_reference_dataA

  DutifyA

  List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.

  ConnectorNo auth

• automation_createA

  Perspective AIA

  Creates an automation on a perspective. Triggers: per_interview (fires on every completed conversation) or scheduled (daily/weekly, with digest, invite, or insights purpose). Actions: internal insight discovery, webhook, email, or connected provider-backed integrations such as Slack, HubSpot, Gmail, Google Docs, Notion, and Confluence. Execution modes: direct (fast, deterministic, webhook-only) or agent (LLM-powered, required for insights and delivery channels). Behavior: - Each call creates a new automation — even if name/config matches an existing one. - Once enabled, the automation starts firing on real events: per_interview sends on every completed conversation going forward; scheduled sends a real message on the configured cadence (daily/weekly). - For HubSpot, the workspace's HubSpot connection is required — errors with "Could not resolve HubSpot portal ID — please reconnect HubSpot" if not connected. - Webhook channels: do NOT ask the user for the endpoint URL or credentials — neither is accepted through this tool. The automation is created disabled and the response includes configure_url, a web app page where the user sets the URL (and an authentication header if needed). Share that link and ask the user to reply "Done" after saving, then enable the automation via automation_update. - Insight automations use kind "insights", execution_mode "agent", omit channel, and use scheduled purpose "insights" when scheduled. - Errors when the perspective is not found or you do not have access. When to use this tool: - The user wants ongoing notifications on every completed conversation (per_interview). - Building a daily/weekly digest delivered to Slack, email, HubSpot, or a webhook (scheduled). - Running scheduled insight automation which creates insights without external delivery. When NOT to use this tool: - Trying a one-off send before going live — create the automation, then use automation_test (use override_email on email channels to avoid hitting real recipients). - Editing or toggling an existing automation — use automation_update. - Connecting Slack or HubSpot — use integration_manage first; the provider must be connected before slack/hubspot channels work. Example — per-conversation Slack notify (resolve the channel with slack_channel_resolve first, then pass it as resource_id): ``` { "perspective_id": "...", "automation": { "name": "Notify Slack", "trigger": { "type": "per_interview" }, "execution_mode": "agent", "channel": { "type": "composio", "delivery_config": { "provider": "slackbot", "tool_slug": "SLACKBOT_SEND_MESSAGE", "resource_id": "C0123ABCD", "resource_name": "#research" } } } } ``` resource_id is the Slack channel ID or name. The channel is re-verified live on create; an unresolvable channel is rejected. Typical flow: 1. integration_manage (operation: "list"/"connect") → ensure Slack / HubSpot is connected (only needed for those channels) 2. For Slack: slack_channel_search / slack_channel_resolve → find/verify the channel to use as resource_id 3. automation_create → create the automation 4. automation_test (with overrides) → verify delivery before relying on it

  ConnectorOAuth

• automation_testA

  Perspective AIA

  Runs a single end-to-end execution of an existing automation, returning success/failure plus the target and duration. Mirrors a real production firing. Behavior: - Sends REAL messages: posts the configured webhook, sends the configured email, posts the Slack message, or writes the HubSpot record. Use override_email (email channels) to redirect delivery to a safe test target. - Insight automations use REAL research conversations, create a normal analysis session and insights, and consume normal analysis-session credits. They do not advance the configured trigger's schedule. - Each call fires another real delivery. - Errors when the perspective or automation is not found, or you do not have access. Webhook automations whose endpoint URL hasn't been set yet (at configure_url) error with a pointer to that page. - Mock conversation defaults: trust score 85, status complete, "Test Participant" / test@example.com. Override participant_name, participant_email, summary, and tags via test_data. HubSpot note and record-update automations find the contact by participant_email, so set it to an existing contact's email. - Returns success: false when the automation skips delivery (e.g., tag/trust filter doesn't match the mock, or no HubSpot record matches the participant email); the message gives the skip reason. The error field is populated only on real delivery failures. When to use this tool: - Verifying a freshly-created automation actually delivers before relying on it (override_email directs email tests to a safe target instead of real recipients). - Reproducing a delivery failure surfaced in automation_list (last_error). When NOT to use this tool: - Listing what's configured — use automation_list. - Changing config — use automation_update. - Removing the automation — use automation_delete.

  Connector

  Destructive

  OAuth