MCP-native · machine-readable workflows

An automation tool your AI can actually drive.

Legacy RPA hides the workflow inside a binary. Worksloth makes every workflow a small, versioned JSON your agent can read, reason about, and reproduce — steps, the fields each step needs, and exactly which steps a human must do. Then it drives all of it over MCP.

1. Your agent reads the workflow

Canonical guide/v1 JSON. No scraping, no guessing.

{
  "worksloth": "guide/v1",
  "title": "Vahan new vehicle registration",
  "stepCount": 7,
  "requires": ["Chassis No", "Engine No", "Name", "Mobile", "PAN"],
  "steps": [
    { "n": 1, "action": "fill",  "caption": "Fill the fields from the record",
      "fields": ["Chassis No", "Engine No"], "attended": false },
    { "n": 2, "action": "click", "caption": "Click Get Details",
      "target": "Get Details", "attended": false },
    { "n": 3, "action": "pause", "caption": "Enter the Aadhaar OTP, then Resume.",
      "attended": true }
  ]
}

2. Your agent drives it over MCP

Drop this in your MCP client config:

{
  "mcpServers": {
    "worksloth": {
      "command": "node",
      "args": ["/path/to/worksloth/mcp/index.mjs"],
      "env": {
        "WORKSLOTH_SERVER": "https://dms.prk.sh",
        "WORKSLOTH_TOKEN": "dd_ext_your_token"
      }
    }
  }
}

Three formats from one workflow

  • POST /api/guides/json — machine format (guide/v1)
  • POST /api/guides/md — Markdown for humans and LLMs
  • POST /api/guides/pdf — a printable step-by-step guide

MCP tools

Everything the app does, your AI can do:

ws_list_workflowsws_get_workflowws_create_workflowws_update_workflowws_synthesize_workflowws_list_templatesws_get_templatews_publish_templatews_install_templatews_list_recordsws_create_recordws_update_recordws_list_workspacesws_create_workspacews_list_webhooksws_create_webhook

Give your agent hands on the real screens

Record the workflow once. Your AI understands it, reproduces it, and runs it — on the legacy portals that will never have an API.

Start free — no card