Skip to main content
The Sendcloud MCP server exposes the Public API v3 to AI assistants and agents through the Model Context Protocol (MCP). Every API operation (for example creating shipments, listing orders, tracking parcels, and more) is available as a tool your MCP client can call, so an agent can act on your Sendcloud account in natural language without you writing any HTTP code. It is an aggregated server: a single endpoint that bundles every Public API v3 domain as a separate toolset. You connect once and get access to all of them, or narrow the connection to just the toolsets you need.
This page describes how to use the MCP server as an agent or MCP client. For the underlying endpoints and schemas, see the API v3 reference.

​
Endpoint

MCP URLhttps://mcp.sendcloud.com/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.0 (bearer token)
The server speaks the standard MCP protocol over HTTP, so any MCP-compatible client (for example Claude, Claude Code, Cursor, or your own agent built on an MCP SDK) can connect to it.

​
Connecting

1

Add the server to your MCP client

Point your client at the MCP URL. For example, with the Claude Code CLI:
claude mcp add --transport http sendcloud https://mcp.sendcloud.com/mcp
Other clients (Cursor, Claude Desktop, custom agents) accept the same URL in their MCP server configuration. A typical JSON config looks like:
{
  "mcpServers": {
    "sendcloud": {
      "type": "http",
      "url": "https://mcp.sendcloud.com/mcp"
    }
  }
}
2

Authorize with OAuth 2.0

The first time your client connects, it discovers the authorization server automatically (via RFC 9728 protected-resource metadata) and walks you through an OAuth 2.0 sign-in at account.sendcloud.com. After you approve access, the client stores the resulting token and attaches it to every tool call.Your credentials live in the MCP client, never in the server. See Authentication for how Sendcloud OAuth 2.0 works.
OAuth 2.0 is currently available as a beta feature for a limited number of clients. Reach out to Sendcloud if your account is not yet enabled.
3

Discover and call tools

Once connected, the client lists the available tools. Ask the agent to perform a task (for example “list my most recent orders” or “track parcel 123456789”) and it selects and calls the matching tool, forwarding the request to the Public API v3 and returning the response.

​
Selecting toolsets

By default the server exposes all toolsets. To limit a connection to a subset (for example keeping the agent’s tool list focused and relevant) add a ?toolsets= query parameter with a comma-separated list of toolset names: 
# Only the orders and shipments tools
claude mcp add --transport http sendcloud "https://mcp.sendcloud.com/mcp?toolsets=orders,shipments"
The filter applies to both tool discovery and tool calls: a tool outside the selected toolsets is hidden from the list and rejected if called directly.

​
Available toolsets

Each toolset maps to one Public API v3 domain.
ToolsetWhat it covers
analyticsCarrier and shipping-option transit times
brandsBrands configured on your account
carriers-dpCarrier delivery-point order finalization
compatCompatibility shipping-options endpoint
contractsCarrier contracts and their schemas
duties-and-taxesDuties and taxes calculations
dynamic-checkoutCheckout delivery options
event-subscriptionsWebhook subscriptions and connections
integrationsIntegrations, logs, and order-status mappings
ordersCreate, list, retrieve, update, and delete orders
organizationOrganization metadata
parcel-documentsRetrieve parcel documents
parcel-statusesParcel status definitions
parcel-trackingRegister and retrieve tracking
pickupsSchedule and retrieve pickups
reportingParcel reports
returnsCreate, validate, and manage returns
sender-addressesSender addresses
service-pointsService-point lookup and availability
ship-an-orderCreate labels for orders (sync and async)
shipmentsCreate, announce, cancel, and retrieve shipments; validate addresses
shipping-optionsFetch shipping options and quotes
store-locationsStore-location management
supportSupport tickets, carrier contacts, and documents
userUser authentication metadata

​
How tools map to the API

Each tool corresponds to one HTTP operation. The tool name is derived from the operation’s operationId, and is namespaced by toolset to avoid collisions — for example orders_sc_public_v3_orders_get_list_orders (list orders) or shipments_sc_public_v3_scp_get_shipment_by_id (retrieve a shipment).The operation’s path, query, and header parameters — plus the request-body fields — become the tool’s arguments. Required API parameters stay required on the tool.
Every tool call includes an intent_summary argument: a short, natural-language statement of why the agent is calling the tool. It is used for product analytics and is stripped before the request reaches the Public API — it never changes the API call itself.
Tools are annotated with hints about their effect, derived from the HTTP method: read-only (GET), idempotent, or destructive (DELETE, POST). MCP clients use these to auto-confirm safe lookups while prompting you before a tool that creates, cancels, or deletes data.
Tools that create or cancel shipments act on your live account. As with the API directly, you may be invoiced for shipments you create if they aren’t cancelled within the cancellation deadline.

​
Next steps

Authentication

How Sendcloud OAuth 2.0 works

API v3 reference

The endpoints behind every MCP tool