Zuper's Model Context Protocol (MCP) Server

Zuper offers a Model Control Protocol (MCP) server enabling AI assistants and other applications to access the Zuper platform from beyond the Zuper interface. This server provides a way to interact with your Zuper workspace through various AI platforms and tools that support MCP.


Available Tools

Zuper MCP server offers over 25+ tools including:

  • Job tracking and status updates
  • Customer & Technician information
  • Dispatching & Job Assignment
  • Communicating with end customers

Connecting to Zuper MCP Server

You can connect to our MCP server natively via Claude Integration, or by using the mcp-remote module in Cursor, Windsurf, and other MCP compatible clients. Zuper MCP server is available at: https://mcp.zuperpro.com/sse

Our MCP Server requires authentication with your Zuper account to use. When connecting, you will be prompted to authorize the application to access your Zuper data. You can also connect by sending authorization headers under Authorization or x-api-key to the MCP server.


Setup Instructions

Claude.ai

  1. Navigate to Settings in the sidebar on web or desktop
  2. Scroll to Integrations at the bottom and click Add more
  3. In the prompt enter:
  1. Make sure to enable the tools in any new chats

Cursor

  1. Open Cursor Settings - CTRL/CMD + Shift + J
  2. Select MCP
  3. Click on Add new global MCP server
  4. Add the following
  {
  "mcpServers": {
    "zuper": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.zuperpro.com/sse", "--header", "x-api-key: ${ZUPER_API_KEY}", "--header", "x-account-region: ${ZUPER_API_REGION}"]
    },
    "env": {
      "ZUPER_API_KEY": "...",
      "ZUPER_API_REGION": "..."
    }
  }
}

Windsurf

  1. Open Windsurf Settings - CTRL/CMD + Shift + J
  2. Go to Cascade -> MCP servers
  3. Click on Add Server -> Add custom server
  4. Add the following,
{
  "mcpServers": {
    "zuper": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.zuperpro.com/sse", "--header", "x-api-key: ${ZUPER_API_KEY}", "--header", "x-account-region: ${ZUPER_API_REGION}"]
    },
    "env": {
      "ZUPER_API_KEY": "...",
      "ZUPER_API_REGION": "..."
    }
  }
}

Troubleshooting

  • If authentication fails, ensure your API key is valid & API region is set right
  • Ensure your MCP client supports SSE-based servers (not Streamable HTTP)
  • Check that your client can handle header based authentication flows