Multi-Carrier Shipping API — powered by Secureship
Secureship MCP gives AI assistants access to a multi-carrier shipping API covering rate comparison, label generation, package tracking, pickup scheduling, address book management, shipment history, customs documents, and more — across carriers like UPS, FedEx, Purolator, Canpar, and others. Browse 150+ live endpoint schemas, parameters, and auth details — always current, never stale. Secureship isn't just for shipping with one carrier — it's a multi-carrier shipping platform, and this MCP server gives AI assistants full access to the API documentation for every supported action: compare rates across carriers, generate shipping labels, track packages, schedule pickups, manage address books, review shipment history, produce customs documents, handle invoices, and even perform actions available on the Secureship web dashboard — all through a single API. The MCP documentation server exposes live endpoint metadata pulled directly from the running application — not static docs that go stale. That means AI assistants always get the correct paths, parameters, request bodies, response schemas, and authentication requirements for 150+ endpoints. Read-only, public, no API key needed to browse. Authentication for the actual shipping API uses a simple X-API-KEY header. **Tools exposed:** - SearchDocs — keyword search across all API endpoints - GetEndpointDetail — full schema for a specific endpoint (params, request body, responses, auth) - ListEndpoints — list all endpoints, optionally filtered by category - GetAuthInfo — authentication instructions (X-API-KEY header) **Categories:** Shipping, logistics, e-commerce, carriers, rates, labels, tracking, address book, customs documents, shipment history
How to connect
https://docs--secureship.run.tools
tools/list returns the expected tools before relying on them in production.Tools
(4)-
get_endpoint_detailGet the full schema for a specific Secureship API endpoint — all parameters, request body fields, response format, and authentication requirements. Use after SearchDocs identifies the right endpoint. Authentication uses the X-API-KEY header.
-
get_auth_infoGet Secureship API authentication instructions. Call this FIRST before generating any code examples with authentication headers. Secureship uses X-API-KEY header authentication, NOT Bearer tokens.
-
search_docsSearch Secureship API documentation. Use when you need to find endpoints for a specific task (e.g. 'create a shipment', 'get rates', 'address book'). Returns matching endpoints with method, path, summary, and tags. Follow up with GetEndpointDetail to get full parameter schemas. IMPORTANT: Secureship API uses the X-API-KEY header for authentication (NOT Bearer token). Pass your API key as: X-API-KEY: your-api-key
-
list_endpointsList all Secureship API endpoints, optionally filtered by category. Categories include: carriers, shipment, history, address-book, auth, account, users, invoices, pickups, documents, integrations, settings, dashboard. Use for discovery when you don't know which endpoint to search for.