Skip to content

Soxoa Automation Planner

by soxoa.com · remote · no sign-in to list tools · v1.0.0 · published by com.soxoa

Estimate illustrative automation ROI and rank recurring workflows to automate. Read-only, no auth.

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http automation-planning https://soxoa.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • build_workflow_pilotBuilds a pilot plan from supplied workflow facts: current steps, trigger, inputs, desired output, source and destination systems, review owner, risk, data sensitivity and success c…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Builds a pilot plan from supplied workflow facts: current steps, trigger, inputs, desired output, source and destination systems, review owner, risk, data sensitivity and success checks. Returns proposed steps, tools, a ready-to-use drafting prompt, review gates, acceptance checks, rollout and a Markdown plan. It does not connect accounts, start provider work, store a plan, send messages or execute the workflow.

    Annotations the server declares

    • title: Build a workflow pilot
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • estimate_automation_roiEstimates reclaimable team capacity and an illustrative payback period from caller-supplied workload figures.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimates reclaimable team capacity and an illustrative payback period from caller-supplied workload figures. Requires people, weekly hours per person and loaded hourly cost; when automatable share or working weeks are omitted, the server uses 60% and 48. Payback is calculated only when an implementation cost is supplied. Returns weekly and annual hours reclaimed, annual capacity value, payback months, the assumptions used and a recommended next step. Results are planning estimates, not guaranteed savings or financial advice.

    Annotations the server declares

    • title: Estimate automation ROI
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • prioritize_automation_workflowsRanks 1 to 12 caller-described workflows by value, predictability, judgment, data sensitivity and integration complexity, and labels each automate, assist or discovery.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Ranks 1 to 12 caller-described workflows by value, predictability, judgment, data sensitivity and integration complexity, and labels each automate, assist or discovery. Each workflow requires a name, weekly hours, predictability, judgment required, error cost, data sensitivity and system count. Returns each workflow's score, recommendation, human-review flag and rationale, plus a recommended first workflow and guardrails. It does not connect to or change any system.

    Annotations the server declares

    • title: Prioritize automation workflows
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http automation-planning https://soxoa.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__automation-planning__estimate_automation_roi",
      "mcp__automation-planning__prioritize_automation_workflows",
      "mcp__automation-planning__build_workflow_pilot"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as automation-planning. Review it before you use it.