Integration guide · Model Context Protocol

Route a work order over MCP

The STEADYWRK dispatch control plane speaks the Model Context Protocol. Point any MCP client at one Streamable-HTTP endpoint and call the dispatch tools directly — quote a field-service job, create a tracked work order, and read live evals — from Claude or any MCP-native agent.

/api/mcpMCP endpoint

2025-11-25protocol

<2hr targetquote turnaround

Step 1 · Connect

Register the MCP endpoint

Add the Streamable-HTTP endpoint to your MCP client. In Claude Desktop, this goes in the mcpServers block of your config. No key is needed to list tools or call the public ones.

claude_desktop_config.json

{
  "mcpServers": {
    "steadywrk-dispatch": {
      "type": "http",
      "url": "https://steadywrk.app/api/mcp"
    }
  }
}

Prefer discovery first? The agent card at /.well-known/agent-card.json lists the same skills, and the OpenAPI 3.1 document at /openapi.yaml describes the REST equivalents.

Listed in the official MCP Registry as app.steadywrk/mcp-dispatch. Lookup/install entry: registry.modelcontextprotocol.io/v0/servers?search=steadywrk.

Step 2 · The tools

Four dispatch tools

Every field below is the live tool definition — names, descriptions, auth posture, REST mapping, and JSON-Schema input shape are read straight from the dispatch discovery contract. dispatch.evals and dispatch.index are public; the rest need an API key, and return a coming_soon result when the key is absent.

dispatch.quotex-api-key

Return an instant dispatch quote for a field-service job. Accepts trade + location + urgency and returns matched contractor, estimated cost in cents, ETA tier, and valid_for_minutes.

POST /api/dispatch/v1/quote

Input JSON-Schema

{
  "type": "object",
  "required": [
    "trade",
    "location"
  ],
  "properties": {
    "trade": {
      "type": "string",
      "description": "Trade code (plumbing, electrical, HVAC, etc.)"
    },
    "location": {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "minLength": 2,
          "maxLength": 2
        },
        "zip": {
          "type": "string",
          "maxLength": 10
        },
        "city": {
          "type": "string",
          "maxLength": 255
        }
      }
    },
    "urgency": {
      "type": "string",
      "enum": [
        "emergency",
        "urgent",
        "routine",
        "scheduled"
      ],
      "default": "routine"
    },
    "nte_cents": {
      "type": "integer",
      "minimum": 1
    },
    "description": {
      "type": "string",
      "maxLength": 2000
    }
  }
}

dispatch.orderx-api-key

Create a dispatch work order. Auto-matches a contractor from the active pool and returns a tracked order with masked contractor reference and status URL.

POST /api/dispatch/v1/order

Input JSON-Schema

{
  "type": "object",
  "required": [
    "trade",
    "location",
    "description"
  ],
  "properties": {
    "trade": {
      "type": "string"
    },
    "location": {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "minLength": 2,
          "maxLength": 2
        },
        "zip": {
          "type": "string",
          "maxLength": 10
        },
        "city": {
          "type": "string",
          "maxLength": 255
        },
        "address": {
          "type": "string",
          "maxLength": 1000
        },
        "name": {
          "type": "string",
          "maxLength": 500
        }
      }
    },
    "urgency": {
      "type": "string",
      "enum": [
        "emergency",
        "urgent",
        "routine",
        "scheduled"
      ],
      "default": "routine"
    },
    "nte_cents": {
      "type": "integer",
      "minimum": 1
    },
    "description": {
      "type": "string",
      "minLength": 1,
      "maxLength": 5000
    },
    "callback_url": {
      "type": "string",
      "format": "uri"
    },
    "reference_id": {
      "type": "string",
      "maxLength": 255
    }
  }
}

dispatch.evalspublic · no key

Return the public evals dashboard: completion rate, NTE variance, dispatch latency, human-override rate, and operational counts for the selected rolling window. No API key required.

GET /api/dispatch/analytics/evals

Input JSON-Schema

{
  "type": "object",
  "properties": {
    "period": {
      "type": "string",
      "enum": [
        "rolling_7d",
        "rolling_30d",
        "rolling_90d"
      ],
      "default": "rolling_30d"
    }
  }
}

dispatch.indexpublic · no key

Return the catalog of 8 dispatch trade verticals with baseline model rates (routine urgency, 1.0× multiplier). Rates are STEADYWRK model rates informed by BLS OES data — not BLS verbatim. No API key required.

GET /api/dispatch/index

Input JSON-Schema

{
  "type": "object",
  "properties": {}
}

Step 3 · Worked example

Route a work order via Claude

Two tool calls: quote the job, then place the order. These are raw JSON-RPC tools/call payloads — an MCP client builds them for you from natural language, but the arguments map one-to-one to the published input schemas above.

1. dispatch.quote → matched contractor, cost, ETA

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dispatch.quote",
    "arguments": {
      "trade": "hvac",
      "location": { "state": "AZ", "city": "Phoenix", "zip": "85001" },
      "urgency": "urgent",
      "nte_cents": 120000,
      "description": "Rooftop unit not cooling on a retail suite"
    }
  }
}

2. dispatch.order → tracked order, masked contractor ref

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "dispatch.order",
    "arguments": {
      "trade": "hvac",
      "location": { "state": "AZ", "city": "Phoenix", "zip": "85001" },
      "urgency": "urgent",
      "description": "Rooftop unit not cooling on a retail suite",
      "reference_id": "wo-2026-0042"
    }
  }
}

The same calls work over REST against the OpenAPI 3.1 surface — POST to /api/dispatch/v1/quote and /api/dispatch/v1/order with an x-api-key header. Over REST, a missing or invalid key returns 401. Over MCP, the server proxies both tools with its own server-side key — if that key is ever unconfigured, they return a coming_soon result instead of failing.

Go deeper

Developer hub: API, SDKs, MCP OpenAPI 3.1 spec Agent card (A2A skills)Public evals feed (developer proof)Live evals dashboard How the Dispatch Engine works

Frequently asked questions

What is the STEADYWRK MCP endpoint?

The STEADYWRK dispatch control plane exposes a Streamable-HTTP Model Context Protocol endpoint at https://steadywrk.app/api/mcp (JSON-RPC 2.0, protocol version 2025-11-25). Any MCP client — Claude Desktop, an MCP-aware agent, or your own JSON-RPC caller — can list and call the dispatch tools there. The same tools are also reachable over REST via the OpenAPI 3.1 spec.

Which dispatch tools can an agent call without an API key?

dispatch.evals and dispatch.index are public, no-auth tools — an agent can call them today with zero setup. dispatch.quote and dispatch.order require a server-side DISPATCH_API_KEY; when the key is absent the MCP server returns a coming_soon result rather than failing, so discovery never breaks.

How do I route a work order through Claude using MCP?

Register the STEADYWRK MCP endpoint in your MCP client, then call dispatch.quote with a trade and location to get a matched contractor, estimated cost, and ETA tier, and call dispatch.order with the job details to create a tracked work order with a masked contractor reference and status URL. Both steps follow the JSON-Schema input shapes published on this page.

Is the OpenAPI 3.1 spec available for the dispatch API?

Yes. The OpenAPI 3.1 document is published at https://steadywrk.app/openapi.yaml and is built from the same tool definitions as the MCP server, so the REST surface and the MCP surface stay in agreement. Each MCP tool maps to one REST endpoint, listed in the tool reference on this page.

Get a dispatch API key

The public tools work today with zero setup. For dispatch.quote and dispatch.order, keys are issued manually — reach us at [email protected].

Request API access Back to the developer hub

Route a work order over MCP

/api/mcpMCP endpoint

2025-11-25protocol

<2hr targetquote turnaround

Add the Streamable-HTTP endpoint to your MCP client. In Claude Desktop, this goes in the mcpServers block of your config. No key is needed to list tools or call the public ones.

claude_desktop_config.json

{
  "mcpServers": {
    "steadywrk-dispatch": {
      "type": "http",
      "url": "https://steadywrk.app/api/mcp"
    }
  }
}

Prefer discovery first? The agent card at /.well-known/agent-card.json lists the same skills, and the OpenAPI 3.1 document at /openapi.yaml describes the REST equivalents.

Listed in the official MCP Registry as app.steadywrk/mcp-dispatch. Lookup/install entry: registry.modelcontextprotocol.io/v0/servers?search=steadywrk.

Four dispatch tools

{ "type": "object", "required": [ "trade", "location" ], "properties": { "trade": { "type": "string", "description": "Trade code (plumbing, electrical, HVAC, etc.)" }, "location": { "type": "object", "required": [ "state" ], "properties": { "state": { "type": "string", "minLength": 2, "maxLength": 2 }, "zip": { "type": "string", "maxLength": 10 }, "city": { "type": "string", "maxLength": 255 } } }, "urgency": { "type": "string", "enum": [ "emergency", "urgent", "routine", "scheduled" ], "default": "routine" }, "nte_cents": { "type": "integer", "minimum": 1 }, "description": { "type": "string", "maxLength": 2000 } } }

{ "type": "object", "required": [ "trade", "location", "description" ], "properties": { "trade": { "type": "string" }, "location": { "type": "object", "required": [ "state" ], "properties": { "state": { "type": "string", "minLength": 2, "maxLength": 2 }, "zip": { "type": "string", "maxLength": 10 }, "city": { "type": "string", "maxLength": 255 }, "address": { "type": "string", "maxLength": 1000 }, "name": { "type": "string", "maxLength": 500 } } }, "urgency": { "type": "string", "enum": [ "emergency", "urgent", "routine", "scheduled" ], "default": "routine" }, "nte_cents": { "type": "integer", "minimum": 1 }, "description": { "type": "string", "minLength": 1, "maxLength": 5000 }, "callback_url": { "type": "string", "format": "uri" }, "reference_id": { "type": "string", "maxLength": 255 } } }

{ "type": "object", "properties": { "period": { "type": "string", "enum": [ "rolling_7d", "rolling_30d", "rolling_90d" ], "default": "rolling_30d" } } }

{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "dispatch.quote", "arguments": { "trade": "hvac", "location": { "state": "AZ", "city": "Phoenix", "zip": "85001" }, "urgency": "urgent", "nte_cents": 120000, "description": "Rooftop unit not cooling on a retail suite" } } }

{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "dispatch.order", "arguments": { "trade": "hvac", "location": { "state": "AZ", "city": "Phoenix", "zip": "85001" }, "urgency": "urgent", "description": "Rooftop unit not cooling on a retail suite", "reference_id": "wo-2026-0042" } } }