Integration guide · Model Context Protocol
The STEADYWRK dispatch control plane speaks the Model Context Protocol. Point any MCP client at one Streamable-HTTP endpoint. dispatch.evals is public. Quote and order need a credential you mint at POST /api/mcp/oauth/register — not a key printed here.
Claude
Settings → Connectors → add https://steadywrk.app/api/mcp. Keyless: probe, dispatch.evals, index, estimate. Quote/order: POST https://steadywrk.app/api/mcp/oauth/register then POST https://steadywrk.app/api/mcp/oauth/token, or hello@steadywrk.app.
Open Claude connectorsClaude Desktop mcpServers JSON
{
"mcpServers": {
"steadywrk-dispatch": {
"type": "http",
"url": "https://steadywrk.app/api/mcp"
}
}
}Cursor
Add to Cursor opens cursor://anysphere.cursor-deeplink/mcp/install (Cursor desktop, not a web page). name=steadywrk-dispatch is the mcp.json key — not registry id app.steadywrk/mcp-dispatch. If the link does nothing, paste the JSON into ~/.cursor/mcp.json or %USERPROFILE%\.cursor\mcp.json. dispatch.evals is public.
Add to CursorCursor mcp.json snippet
{
"mcpServers": {
"steadywrk-dispatch": {
"url": "https://steadywrk.app/api/mcp"
}
}
}ChatGPT
Developer-mode Connectors: paste https://steadywrk.app/api/mcp. No Apps Store listing is claimed. Keyless probe, dispatch.evals, index, and estimate run without a key.
Open ChatGPTMCP Streamable-HTTP URL
https://steadywrk.app/api/mcp
Step 1 · Connect
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 — including dispatch.evals. Quote and order mint at https://steadywrk.app/api/mcp/oauth/register then https://steadywrk.app/api/mcp/oauth/token.
{
"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.
Agents mint a scoped token themselves (RFC 7591). This is not mailbox-only. No key is printed on this page. dispatch.evals stays public — DCR is only for quote and order.
POST register — https://steadywrk.app/api/mcp/oauth/register — and keep client_id / client_secret from the JSON. Those values come from the response, never from this site.POST token — https://steadywrk.app/api/mcp/oauth/token — with grant_type=client_credentials plus the placeholders <client_id_from_register> and <client_secret_from_register>.Authorization: Bearer or x-api-key. Anonymous quote/order calls return JSON-RPC error -32001.curl -sS -X POST https://steadywrk.app/api/mcp/oauth/register \
-H 'content-type: application/json' \
-d '{"grant_types":["client_credentials"],"token_endpoint_auth_method":"client_secret_post"}'curl -sS -X POST https://steadywrk.app/api/mcp/oauth/token \
-H 'content-type: application/x-www-form-urlencoded' \
-d 'grant_type=client_credentials&client_id=<client_id_from_register>&client_secret=<client_secret_from_register>'hello@steadywrk.app still works for humans.
Add to Cursor is a cursor:// protocol link. It opens Cursor desktop (or a browser that hands the URL to Cursor). It is not a website and it does not embed a key.
cursor://anysphere.cursor-deeplink/mcp/installsteadywrk-dispatch — not the registry id app.steadywrk/mcp-dispatch{"url":"https://steadywrk.app/api/mcp"}If the button does nothing, Cursor is not registered for cursor://. Paste this JSON into ~/.cursor/mcp.json or %USERPROFILE%\.cursor\mcp.json, then restart Cursor. After install, dispatch.evals is public. Quote and order still need DCR.
Full deeplink
cursor://anysphere.cursor-deeplink/mcp/install?name=steadywrk-dispatch&config=eyJ1cmwiOiJodHRwczovL3N0ZWFkeXdyay5hcHAvYXBpL21jcCJ9{
"mcpServers": {
"steadywrk-dispatch": {
"url": "https://steadywrk.app/api/mcp"
}
}
}Step 2 · The 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. Lead with agentic.readiness_probe — it's free, needs no key, and points a real audit path (Store Guard, $149) at whatever it finds broken. agentic.readiness_probe, dispatch.estimate, dispatch.evals, dispatch.index are public; the rest need a client-presented key or POST /api/mcp/oauth/register. hello@steadywrk.app still works for humans. Anonymous quote/order calls return JSON-RPC error -32001 — the server does not proxy them.
agentic.readiness_probepublic · no keyFree multi-surface storefront readiness snapshot (UCP/ACP discovery, product schema, robots, answer-engine maps). Not an attested Store Guard grade. Response includes a Store Guard $149 CTA. No API key required.
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Public storefront URL or domain",
"maxLength": 255
}
}
}dispatch.quotex-api-keyRequest a field-service quote by trade, location, and urgency. Returns availability and quote details when available. Accepts a provisioned integration key through x-api-key or a scoped self-serve OAuth token through Authorization: Bearer. MCP also accepts the provisioned key through Authorization: Bearer. Obtain a self-serve token through POST /api/mcp/oauth/register, then POST /api/mcp/oauth/token with grant_type=client_credentials. Anonymous callers receive HTTP 401 with WWW-Authenticate. Public modeled pricing is available through dispatch.estimate.
{
"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.estimatepublic · no keyPublic modeled field-service price estimate using cited BLS wage data and disclosed model assumptions. Returns wage_basis and billed_estimate so callers can inspect the calculation and geographic basis. The response identifies estimates based on a national baseline and distinguishes model assumptions from observed prices. Use dispatch.quote with an accepted credential to request a quote. No API key required.
{
"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"
}
}
}dispatch.orderx-api-keyCreate a field-service order and return its status URL. HTTP 201 returns a created order; HTTP 202 returns an order accepted_pending_fulfilment with fulfilled=false. Order creation requires a provisioned integration key through x-api-key. MCP also accepts that key through Authorization: Bearer; direct REST order creation requires x-api-key. A self-serve OAuth token authenticates but is not entitled to create orders: HTTP 402 payment_required (JSON-RPC -32002 over MCP). Anonymous callers receive HTTP 401 with WWW-Authenticate. Provisioning contact: hello@steadywrk.app.
{
"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 keyReturn the public evaluation document for a selected rolling window. Consult its per-field provenance and methodology to distinguish self-reported estimates, measurements, and unavailable fields. It is not an independent audit or a service-level guarantee. No API key required.
{
"type": "object",
"properties": {
"period": {
"type": "string",
"enum": [
"rolling_7d",
"rolling_30d",
"rolling_90d"
],
"default": "rolling_30d"
}
}
}dispatch.indexpublic · no keyReturn the catalog of 8 dispatch trade verticals. Per trade: the BLS OES hourly WAGE (medianRateDollars/p25/p75 — what a technician earns, NOT a price) alongside billedHourlyRateRoutineDollars, what a buyer pays hourly at routine urgency, derived by the same wage→billed transform dispatch.estimate uses. See the wage_vs_billed block. No API key required.
{
"type": "object",
"properties": {}
}The first prompt is public. Quote requires a credential; order requires a provisioned ordering credential, writes production data, and must be explicitly confirmed.
Step 3 · Worked example
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.
{
"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"
}
}
}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 client must send the same key; without one, quote and order return JSON-RPC error -32001. Mint at POST /api/mcp/oauth/register or write hello@steadywrk.app. The server does not proxy those tools with its own key.
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.
Lead with agentic.readiness_probe — keyless, finishes, Store Guard $149 CTA, not an attested grade. agentic.readiness_probe, dispatch.estimate, dispatch.evals, dispatch.index are public, no-auth tools. dispatch.quote and dispatch.order require the client to send its own integration key as x-api-key (or Authorization: Bearer) or a Bearer from POST /api/mcp/oauth/register then POST /api/mcp/oauth/token. hello@steadywrk.app still works for humans. Calling keyed tools without a credential returns JSON-RPC error -32001 — the server does not apply its own key for anonymous callers.
Start keyless with agentic.readiness_probe. For quote/order, register at POST /api/mcp/oauth/register then POST /api/mcp/oauth/token, or send your own integration key as x-api-key (or Authorization: Bearer) — hello@steadywrk.app still works for humans. 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. Without a credential those two tools return JSON-RPC error -32001. Both steps follow the JSON-Schema input shapes published on this page.
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.
Use Add to Cursor. That is a cursor://anysphere.cursor-deeplink/mcp/install link: it opens Cursor desktop, not a web page, and it does not include a key. The name query is steadywrk-dispatch — the mcp.json key — not the registry id app.steadywrk/mcp-dispatch. config is the base64 of {"url":"https://steadywrk.app/api/mcp"}. If the link does nothing, paste that JSON into ~/.cursor/mcp.json or %USERPROFILE%\.cursor\mcp.json. dispatch.evals is public after install. Quote and order still need DCR.
POST /api/mcp/oauth/register (RFC 7591), then POST /api/mcp/oauth/token with grant_type=client_credentials using client_id and client_secret from the register response — never a key copied from this page. hello@steadywrk.app still works for humans. dispatch.evals does not need a credential.
Public tools — including dispatch.evals — work with zero setup. For dispatch.quote and dispatch.order, mint at POST /api/mcp/oauth/register then POST /api/mcp/oauth/token. Humans can still write hello@steadywrk.app.