MCP server

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 URL	`https://mcp.sendcloud.com/mcp`
Transport	Streamable HTTP
Authentication	OAuth 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.

Before you connect – please read.Results are reference information only. This connector lets your AI assistant read data already available to you via the Sendcloud API (e.g. shipment status, tracking, rates, order details). That data reflects a snapshot at the time your AI assistant made the request and can change afterwards – for example, carrier surcharges, tracking status, and delivery estimates update over time. Do not treat a response from your AI assistant as a confirmed or binding figure; for anything time-sensitive or in dispute (e.g. a surcharge query), check your Sendcloud account directly or contact Sendcloud support.Sendcloud does not control your AI assistant’s output. We cannot control, and are not responsible for, how your chosen AI assistant interprets, summarises, or responds to this data, including any follow-up questions or attempts to get it to “confirm” a figure.You choose the AI tool. You are solely responsible for selecting the AI assistant you connect to this feature. Sendcloud does not select, endorse, or control that AI provider, and has no visibility into or control over how it subsequently stores, uses, or discloses the data it receives – that is governed by your own agreement with that provider, not by Sendcloud.By connecting, you confirm you have read and accept the above.

Connecting

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"
    }
  }
}

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.

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.

Toolset	What it covers
`analytics`	Carrier and shipping-option transit times
`brands`	Brands configured on your account
`carriers-dp`	Carrier delivery-point order finalization
`compat`	Compatibility shipping-options endpoint
`contracts`	Carrier contracts and their schemas
`duties-and-taxes`	Duties and taxes calculations
`dynamic-checkout`	Checkout delivery options
`event-subscriptions`	Webhook subscriptions and connections
`integrations`	Integrations, logs, and order-status mappings
`orders`	Create, list, retrieve, update, and delete orders
`organization`	Organization metadata
`parcel-documents`	Retrieve parcel documents
`parcel-statuses`	Parcel status definitions
`parcel-tracking`	Register and retrieve tracking
`pickups`	Schedule and retrieve pickups
`reporting`	Parcel reports
`returns`	Create, validate, and manage returns
`sender-addresses`	Sender addresses
`service-points`	Service-point lookup and availability
`ship-an-order`	Create labels for orders (sync and async)
`shipments`	Create, announce, cancel, and retrieve shipments; validate addresses
`shipping-options`	Fetch shipping options and quotes
`store-locations`	Store-location management
`support`	Support tickets, carrier contacts, and documents
`user`	User authentication metadata

How tools map to the API

Tool naming and namespacing

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.

Safety annotations

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.

Getting started

Shipments

Addresses

Orders

Dynamic Checkout

Returns

Service points

Parcel tracking

Marketplaces

Archive

Endpoint

Connecting

Selecting toolsets

Available toolsets

How tools map to the API

Next steps

Authentication

API v3 reference

​Endpoint

​Connecting

​Selecting toolsets

​Available toolsets

​How tools map to the API

​Next steps

Authentication

API v3 reference

Endpoint

Connecting

Selecting toolsets

Available toolsets

How tools map to the API

Next steps