India Logistics MCP Server

India Logistics MCP 🇮🇳 — How can my AI agent ship a parcel across India (Delhivery / Bluedart / Ekart via Shiprocket)?

Remote MCP server that lets any AI agent ship parcels across India — over Delhivery, Bluedart, Ekart, Xpressbees, DTDC and more — through the Shiprocket shipping API. Check courier serviceability + live rates by pincode, create shipping orders, track parcels by AWB, and cancel orders. Stateless, bring-your-own merchant credentials, never stores anything.

Live endpoint: https://logi-in.wishpool.app/mcp · Registry: app.wishpool/india-logistics-mcp

Quick start

{
  "mcpServers": {
    "india-logistics": {
      "type": "http",
      "url": "https://logi-in.wishpool.app/mcp",
      "headers": {
        "x-shiprocket-email": "your_api_user@example.com",
        "x-shiprocket-password": "your_api_user_password"
      }
    }
  }
}

No shared demo — use your own Shiprocket account. Create an API user in the Shiprocket dashboard (Settings → API → Configure / Create an API User) and send its email + password in the headers above. The server is stateless: on every call it exchanges the credentials for a short-lived Bearer token at Shiprocket's /auth/login and stores nothing. Real shipping requires completed merchant KYC (Aadhaar/GSTIN) and at least one registered pickup location — merchant-side prerequisites.

Tools

Owner policy guardrails ride optional headers (x-agentpay-max-amount, x-agentpay-approval-above, x-agentpay-allowed-tools) — set by the human owner in client config; the agent cannot relax them. The order value (INR) is gated before the order is created: approval-above returns an unsigned draft with no order created.

Units

Weight in kilograms (kg), parcel box dimensions in centimetres (cm), money in INR.

Develop

node test/serve.js   # local server on :3246 (/mcp)
node test/e2e.js     # protocol + validation + policy/shiprocket units + fake-credential live probe to apiv2.shiprocket.in (expects native 403)

How it talks to Shiprocket

Every tool call is two server-to-server requests: first POST /v1/external/auth/login ({ email, password } → { token }), then the business endpoint with Authorization: Bearer <token> — the token is never cached (stateless). check_serviceability is GET /v1/external/courier/serviceability/?pickup_postcode=&delivery_postcode=&weight=&cod=. create_shipment is POST /v1/external/orders/create/adhoc. query_tracking is GET /v1/external/courier/track/shipment/{shipment_id} (or /track/awb/{awb}). cancel_shipment is POST /v1/external/orders/cancel ({ ids: [...] }). Base URL https://apiv2.shiprocket.in.

Safety

Pure stateless translation layer. Orders, labels and tracking are held by Shiprocket and the couriers; the merchant credentials travel per-request in headers, are exchanged for a short-lived token, and nothing is stored. Parcels flow sender ↔ courier ↔ recipient directly. Privacy policy.

Sister servers

USA labels (USPS/UPS/FedEx) via EasyPost live in usa-logistics-mcp; Taiwan CVS pickup + home delivery in taiwan-logistics-mcp. One family of stateless BYO local-commerce MCP servers: local payments in 81 countries at mcp.wishpool.app, plus electronic-invoice servers across nine countries including India GST, Mexico CFDI, Brazil NF-e, Chile DTE and Peru CPE.

MIT licensed.