---
title: "MCP server · Zaiped API documentation"
description: "The MCP server is remote: one URL, your API key as the bearer, and every REST route becomes a tool with the same validation and the same errors. Streamable HTTP transport, stateless, no session id."
lang: "en-US"
canonical: "https://zaiped.com/en/developers/docs/mcp"
alternate: "https://zaiped.com/developers/docs/mcp"
---

# MCP server

The MCP server is remote: one URL, your API key as the bearer, and every REST route becomes a tool with the same validation and the same errors. Streamable HTTP transport, stateless, no session id.

```
https://zaiped.com/mcp
```

## Claude Code

```
claude mcp add --transport http zaiped https://zaiped.com/mcp \
  --header "Authorization: Bearer zp_..."
```

## Claude Desktop, Cursor and others (mcp.json)

```
{
  "mcpServers": {
    "zaiped": {
      "url": "https://zaiped.com/mcp",
      "headers": { "Authorization": "Bearer zp_..." }
    }
  }
}
```

Tool names are the route ids: list_numbers, send_message, create_template, list_flows, create_webhook and so on. Inputs flatten path parameters, query and body into one object. upload_media is the only route without a tool: bytes do not travel in JSON-RPC.