About Delivery Tracking (Korea)
Delivery Tracking (Korea) is a read-only MCP server for checking parcels with Korean and international carriers. It provides individual and batch tracking, including status history and attention indicators.
Key features
- 01Track an individual parcel
- 02Track up to 20 parcels per request
- 03View event history in KST
- 04Identify parcels needing attention
- 05List supported carriers and aliases
Use cases
- 01Check the latest status of a shipment
- 02Review delivery progress across many orders
- 03Filter parcels with delivery issues
- 04Look up supported carrier names
MCP support
The MCP server exposes parcel tracking, batch tracking and carrier-listing tools to MCP clients. It uses Delivery Tracker credentials.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @appmonster/mcp-deliveryDELIVERY_TRACKER_CLIENT_IDClient ID from console.tracker.delivery (free)DELIVERY_TRACKER_CLIENT_SECRETSecretClient Secret from console.tracker.deliveryLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 6d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| carrier | string | Yes | Carrier name or id, e.g. CJ대한통운, 우체국, kr.hanjin |
| maxEvents | integer | No | |
| trackingNumber | string | Yes | 운송장 번호 — hyphens/spaces are ignored |
Details
From the project README@appmonster/mcp-delivery
MCP server for parcel tracking — Korean carriers (CJ대한통운, 우체국, 한진, 롯데, 로젠, 경동, 쿠팡, 편의점택배…) and global ones (Yamato, Sagawa, Japan Post, DHL, UPS, FedEx, USPS, EMS) through Delivery Tracker. Read-only. Korean carrier names work directly.
택배 조회 MCP 서버 — "이 주문 어디쯤이야?", "오늘 발송분 중 아직 안 간 거?"를 에이전트가 답합니다.
Tools
| Tool | What it does |
|---|---|
delivery_track_parcel | one parcel → status (접수/집화/이동중/배송출발/배송완료/실패/수령대기/이상), delivered, needsAttention, last event, event history (KST) |
delivery_track_many | up to 20 parcels → per-parcel status + counts (delivered / in transit / needs attention); errors isolated per parcel; your ref echoed back |
delivery_list_carriers | supported carriers (id + name) with the built-in aliases |
Carrier can be a name (CJ대한통운, 우체국, 한진, 야마토, DHL) or an id (kr.cjlogistics). Unknown names fall back to a live search.
Setup (1 minute, free)
- https://console.tracker.delivery → sign in (Google/email) → Create Project → Credentials → Create → copy Client ID / Client Secret (the secret is shown once).
- Claude Desktop / Cursor:
{ "mcpServers": { "delivery": { "command": "npx", "args": ["-y", "@appmonster/mcp-delivery"],
"env": { "DELIVERY_TRACKER_CLIENT_ID": "…", "DELIVERY_TRACKER_CLIENT_SECRET": "…" } } } }
Example prompts
- "CJ 1234-5678-9012 지금 어디야?" →
delivery_track_parcel - "어제 발송한 스마트스토어 주문 전부 배송 상태 확인해줘" →
naver_list_orders→delivery_track_many(ref = 주문번호) - "배송 이상 있는 건만 골라서 고객한테 보낼 문자 초안 써줘" →
delivery_track_many→ filterneedsAttention
Notes
- Free plan credentials expire every 21 days — the console shows the expiration; create a new pair before then (our nightly canary flags it as
AUTHwhen it lapses). Paid plans get lifetime credentials. - Delivery Tracker answers in < 1 s typically; this client gives up after 15 s with a
TIMEOUTerror instead of hanging the agent. - Brand-new labels can take a few hours before the carrier reports anything (
NOT_FOUNDwith a hint). - Times are converted to KST (
+09:00).
MIT © Appmonster
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.