Skip to main content
Glama
669,005 tools. Updated 2026-10-17 08:49

"MCP server for task number 1 automation" matching MCP tools:

  • Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).
    Connector
    Destructive
    OAuth
  • 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
  • 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
  • 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
  • Mark an existing task as completed or reopen it. Use this instead of create_task when the task already exists and you only need to change its completion state. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408). To resolve a public number to an internal ID, call list_tasks with workspaceId + number first.
    ConnectorOAuth
  • Automatically send an approved template to every NEW contact with a tag, e.g. a welcome message whenever a lead tagged "new-lead" is added (by add_or_update_contact, import_contacts, the REST API, or a Zapier/Make integration calling it). Only contacts created AFTER the automation qualify, each at most once: re-importing or tagging existing contacts never triggers it. To message existing contacts, use a broadcast; the response's existing_tagged_contacts says how many already have the tag. Only add contacts who agreed to receive WhatsApp messages. The template must be APPROVED with every {{n}} placeholder mapped (set_template_variables). One automation per tag. delay_minutes (0 to 10080) waits before sending. Returns the automation with live stats and any warnings (e.g. no WhatsApp number connected) that would make sends fail.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Generates random numbers (1-100) with astrological justification based on Mercury's current zodiac position, providing cosmic context for decision-making.
    34 npm
    MIT

Matching MCP Connectors

  • An MCP server for deep research or task groups

  • Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

  • Create a new task by asking the person for its title, description, due date and project workflow status in a native form. An optional projectId selects the project. Save only accepted values; cancelling makes no change. Requires a host supporting MRTR form elicitation; otherwise use item_create. Accepted task creation may send configured notifications, webhooks and automation actions.
    Connector
    Destructive
    OAuth
  • Permanently deletes an automation. Pauses any scheduled sends first, then removes the automation. Behavior: - DESTRUCTIVE and irreversible — the automation cannot be recovered. No undo. - Errors when the perspective or automation is not found, or you do not have access. Deleting an already-deleted automation errors as well. - If pausing the scheduled sender fails, the deletion is aborted and you'll get success: false with "Failed to stop running workflow. Please try again." — the automation stays intact in that case. When to use this tool: - The user explicitly asked to remove an automation and confirmed. - Cleaning up a misconfigured automation that automation_test repeatedly fails on. When NOT to use this tool: - The user just wants to pause it temporarily — use automation_update with { enabled: false } instead. - You're not sure which automation_id is correct — confirm via automation_list first.
    Connector
    Destructive
    OAuth
  • Creates a task in OmniFocus on this Mac. Needs OmniFocus Pro (the free tier blocks automation). Without `project` the task goes to the inbox. `project` must be the exact name of an existing project: if no project has that name the call fails with an error instead of falling back to the inbox — check the name with list_omnifocus_projects first. Called without confirm it returns a preview; pass confirm=true to create. Returns the task id.
    ConnectorOAuth
  • List tasks in a project, or look up a specific task by its public number. To resolve a public ID like 'TES-1': pass taskPrefix='TES' and number=1 — the prefix locates the correct workspace automatically (do NOT hardcode workspaceId when the prefix belongs to a different workspace). Alternatively pass workspaceId + number when you are certain of the workspace.
    ConnectorOAuth
  • Search real student IELTS Writing answers scored by AI examiner. Args: task: IELTS Writing task number — 1 (reports/letters) or 2 (essays). band: whole band to filter on; matches half-bands too (8 -> 8.0-8.5). query: free-text match against the question/prompt. limit: max results (1-50). Each result links to a full page with the question, the student's answer, and criterion-by-criterion examiner feedback. Use get_model_answer for the full content, or compare_question to see the same prompt at other bands.
    ConnectorNo auth
  • List submitted responses for a form, newest first. Args: - form_id (string): the form's ID - page (number): 1-based page (default 1) - limit (number): page size, 1-100 (default 20) - response_format ('markdown' | 'json') Returns: { total, page, limit, count, responses: [{ id, submitted_at, answers }] }. For aggregate metrics use foxform_get_form_analytics; for a full dump use foxform_export_responses.
    ConnectorNo auth
  • List submitted responses for a form, newest first. Args: - form_id (string): the form's ID - page (number): 1-based page (default 1) - limit (number): page size, 1-100 (default 20) - response_format ('markdown' | 'json') Returns: { total, page, limit, count, responses: [{ id, submitted_at, answers }] }. For aggregate metrics use foxform_get_form_analytics; for a full dump use foxform_export_responses.
    ConnectorNo auth
  • Reboot an iOS device. DISRUPTIVE and NOT REVERSIBLE: the device is unreachable for roughly a minute, the automation session and the stream go down, and anything in progress on the device is lost. Requires confirm=true — there is no default. Do NOT reach for this to recover from a flaky tool call; try ios_end_session first, which resets the automation session without touching the device. Reboot only when the device itself is wedged and a human has asked for it. No automation session required. The Android counterpart is device_reboot.
    Connector
    Destructive
    OAuth
  • Use this when the user wants something done for them on a schedule — every day, on certain weekdays, or every few hours — e.g. 'every Monday at 9, summarise my sales sheet'. Creates a Xenition automation that runs on its own at those times, even when nobody is in this chat. Results appear in Xenition, and anything that would act in a connected app waits for the user's approval. Do not use for a one-off task now (use run_agent).
    ConnectorNo auth
  • THE approval inbox for V2 rule automation — the ONLY surface for pending automation approvals (MinMax/AOE/scheduled-task tools are separate systems, not this inbox). status=pending (default) means NOT yet approved/dismissed by a user: pending_approval (manual queue + escalations), pending_ai_review (queued for AI Workforce Review — the Automation Review Analyst seat works this queue at its check-ins), shadow (legacy AI Shadow rows; needs your approve/dismiss) and ai_rejected (overridable). Rows carry approval_mode (manual|workforce_review|auto; legacy ai_review/ai_shadow read as workforce_review), rule owner, needs, undoable, and paginate with total_found/truncated/next_offset. scope=mine (default) shows only the calling user's rules; scope=all_users shows every user's. READ-ONLY: action=list. Approving/rejecting/undoing inbox items lives in stage_automation_review.
    ConnectorOAuth
  • List the authenticated user's automations. An automation is a saved task for the AI phone agent (`prompt`) that runs across one or more phones, on a schedule (`schedule_cron` in `timezone`), when its webhook is called, or on demand with run-automation-tool. Each run is followed with list-automation-runs-tool and get-automation-run-tool. `kind` is "prompt" for that, or "tiktok_warmup" for a TikTok account warm-up: its `settings` (niche, keywords, comment language, daily window, session counts and lengths) replace `prompt` and it has no `schedule_cron` — it plans and runs its own sessions every day on its own timetable, and run-automation-tool only ever starts an extra one now. Not the same as macros (list-macros-tool), which replay recorded input exactly with no AI. Automations are created and edited in the web app.
    ConnectorOAuth
  • Update an authorized project, task, or resource using its current version. Changes can send configured webhooks and workspace notifications or trigger automation rules. To update many, use items_update. Provide a unique requestId and reuse it when retrying this exact action. Item updates require the current version from get_tasks, get_items, or get_workspace. Permissions are enforced for the workspace, project, and account.
    Connector
    Destructive
    OAuth
  • Get fee rate estimate on Bitcoin mainnet for a target number of blocks. Returns estimated fee in BTC/kB and sat/byte. Use target=1 for next-block, target=6 for ~1 hour. Returns -1 if no estimate available.
    ConnectorNo auth
  • Get fee rate estimate on Bitcoin testnet3 for a target number of blocks. Returns estimated fee in BTC/kB and sat/byte. Use target=1 for next-block, target=6 for ~1 hour. Returns -1 if no estimate available.
    ConnectorNo auth
  • Return case metadata (no full task prompts): pair_id/id, axis, tier, grounding, and side indicators (malign/benign for axes 1/2/4; null for axis 3). Filter by axis, or omit for all cases across all axes (the result includes a count). Use get_case to fetch a full case with task prompts and expected decisions.
    ConnectorNo auth