Indonesia Logistics MCP 🇮🇩 — How can my AI agent ship a parcel across Indonesia (JNE / J&T / SiCepat via Biteship)?

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

{
  "mcpServers": {
    "indonesia-logistics": {
      "type": "http",
      "url": "https://logi-id.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

git clone https://github.com/junter1989k-ai/indonesia-logistics-mcp && cd indonesia-logistics-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Remote MCP server that lets any AI agent ship parcels across Indonesia — over JNE, J&T, SiCepat, AnterAja, Ninja, Pos Indonesia, Lion Parcel, Gojek and Grab — through the Biteship shipping API. Compare courier rates by postal code (cek ongkir), create shipping orders, track parcels by waybill, and cancel orders. Stateless, bring-your-own Biteship API key, never stores anything.

Live endpoint: https://logi-id.wishpool.app/mcp · Registry: app.wishpool/indonesia-logistics-mcp

Quick start

{
  "mcpServers": {
    "indonesia-logistics": {
      "type": "http",
      "url": "https://logi-id.wishpool.app/mcp",
      "headers": {
        "x-biteship-key": "biteship_live_your_api_key"
      }
    }
  }
}

No shared demo — use your own Biteship account. Get an API key in the Biteship dashboard at dashboard.biteship.com (Settings → API Key) and send it in the header above. The server is stateless: on every call it sends the key as the Authorization header directly to api.biteship.com and stores nothing. A biteship_test_ key runs in the sandbox; a biteship_live_ key ships real parcels and debits your Biteship balance.

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 (IDR) is gated befo

... View full README on GitHub