Zuper developer hub · v1.0

Build on the platform your crews already run on.

REST APIs, webhooks and an MCP server for every job, quote, invoice and crew in Zuper. If your team can do it in the app, your code can do it too.

# Every account lives in one data center. Ask which.
curl https://accounts.zuperpro.com/api/config \
  -X POST \
  -H 'content-type: application/json' \
  -d '{"company_name":"your-company"}'
200 OK
{ "type": "success", "config": {
    "dc_country": "US WEST",
    "dc_api_url": "https://us-west-1c.zuperpro.com" } }
# Your key goes in one header. That's the whole auth story.
curl "https://us-west-1c.zuperpro.com/api/jobs?count=10" \
  -H "x-api-key: $ZUPER_API_KEY"
200 OK
{ "type": "success", "data": [ {
    "job_title": "Roof inspection",
    "job_priority": "HIGH",
    "current_job_status": { "status_name": "On the way" }
} ] }
// mcp.json in Cursor, Windsurf or any MCP client
{ "mcpServers": { "zuper": {
  "command": "npx",
  "args": ["-y", "mcp-remote",
    "https://mcp.zuperpro.com/sse",
    "--header", "x-api-key: ${ZUPER_API_KEY}"]
} } }
Connected
290 tools ready: list_jobs, create_job, reschedule_job…
500+ endpoints

Jobs to payroll, in one API

290 MCP tools

Across 28 modules

700 req / min

Top plan rate limit

1 header

x-api-key, over HTTPS

Model Context Protocol

Your AI agent can run the dispatch board.

Point any MCP client at one URL. Sign in with your Zuper account, or pass your API key, and the agent can list jobs, check a tech's conflicts and reschedule, the same way your dispatcher would.

  • Claude
  • Cursor
  • Windsurf
  • OpenAI Agent Builder
https://mcp.zuperpro.com/sse
  1. list_jobsFilter by status, tech, date
  2. check_schedule_conflictIs Dave free at 2pm?
  3. reschedule_jobMove it to Thursday
  4. create_job_invoiceBill it when it closes
  5. send_job_cardEmail the PDF to the customer