Mailhub MCP

Model Context Protocol (MCP) is the standard an AI assistant uses to reach operations outside its own conversation. Mailhub runs a remote MCP server at the Mailhub end of that connection. A tool is one operation the assistant can call; Mailhub publishes eight tools and nothing else.

The assistant acts as you — the Mailhub user who authorized it. It holds no API key and is not a separate machine identity, so your own roles and permissions still bound everything it does.

Is MCP the right choice?

	Mailhub MCP	Mailhub API
Caller	An AI assistant acting as one signed-in user	Your own application or service
Credential	Browser authorization by that user	An account API key exchanged for a token
Reach	That user's roles and permissions	The account the API key belongs to
Available operations	Eight fixed tools	The documented public operations
Built for	Interactive work with a person present	Unattended system-to-system integration

If your code runs without a person in the loop, this is the wrong choice — use the API and start at How to start.

Can you connect?

MCP access is not self-service

Mailhub connects only clients and environments it has confirmed, and registers each client in advance — an MCP client cannot register itself, so being MCP-capable is not by itself enough to connect and neither is knowing the server URL. Connecting in Claude has the URLs and the steps.

To find out whether your intended assistant and environment can be used, ask through the support arrangement already in place for your Mailhub account; Developer Support explains what to include in that request.

How the objects fit together

Order → Shipment → Rate → Label.

• An Order is the fulfillment record, and it carries the Shipment identifier the next step needs.
• A Shipment is what gets rated. You rate it with its shipmentId.
• A Rate is one carrier's price and service for that Shipment. You buy with its rateId.
• A Label is the postage that purchase creates. Buying it also moves the Order on, and cancelling it uses the labelId.

The eight tools

Tool	What it does	Changes data
mailhub_list_orders	Page through the account's Orders	No
mailhub_get_order	Read one Order and its Shipment	No
mailhub_create_order	Create an Order	Yes
mailhub_get_shipment_rates	Get carrier Rates for a Shipment	No
mailhub_buy_label	Buy a Label for a chosen Rate	Yes — spends wallet funds
mailhub_download_label	Get a link to a purchased Label	No
mailhub_cancel_label	Cancel a purchased Label	Yes
mailhub_update_order_status	Move an Order to another status	Yes

Each tool has its own page in the Tool Reference, with its exact inputs and what it returns. Limits & Current Scope covers what these eight tools do not do, and where that work belongs instead.

mailhub_buy_label is the only tool that spends money. All four changing tools are refused by the server unless the call carries an explicit confirmation — Confirmations & Spend Safety is the full account of that and of the spend limits around it.

You do not have to move an Order to Packed, or to any other status, before asking for Rates or buying a Label.

Start here

• You have confirmed MCP access → Before You Connect, to get the account and permissions ready, then Connecting in Claude.
• You are building an unattended integration → How to start, the API-key surface.
• You are reviewing this for security → Security Model.