# Track-POD MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Track-POD MCP

Track delivery orders, routes, drivers and proof of delivery; create new orders.

- Record: https://musedirectory.ai/connector/track-pod-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/track-pod/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 4266ms, checked 2026-10-29T10:45:48Z
- Endpoint: https://track-pod.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:46:22Z)
- Source: Found in the official MCP Registry (io.usefulapi/track-pod) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ftrack-pod

Connects to Track-POD delivery management system. Read orders by date or route, check delivery status and proof of delivery with signatures and photos. List drivers, vehicles and routes. Create new unscheduled orders for dispatch.

Example request: "Show me all orders scheduled for delivery today and which ones have been completed."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Track-POD MCP to help me. It is a free service with an MCP server at https://track-pod.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- trackpod_list_orders: List the orders of one day — by order date (GET /Order/Date/{date}) or by planned route date (GET /Order/Route/Date/{date}) — with optional filters on delivery status, driver and route number. Track-POD returns the whole day at once; this tool pages it (offset/limit) and reports 
- trackpod_list_orders_changed_since: List orders whose delivery status changed after a moment in the last 24 hours (GET /Order/Status/Date/{date-time}; Track-POD accepts no earlier time than UTC now − 1 day). Good for 'what was delivered / failed since this morning'. Paged here (offset/limit).
- trackpod_list_route_orders: List the orders on one route, in route order, by route code (GET /Order/Route/Code/{code}). Paged here (offset/limit).
- trackpod_get_order: Get one order with every field: client, address, time slot, goods lines, route, driver, delivery status, ETA, signature/photo links and tracking link. Pass exactly one of number, order_id or track_id (GET /Order/Number|Id|TrackId/{…}). A removed order answers with who removed it 
- trackpod_find_orders_by_number: List the last 25 orders that share one order number (re-deliveries, repeated jobs) — GET /Order/Number/{number}/List. Use it when an order number was reused and trackpod_get_order returns only one of them.
- trackpod_get_proof_of_delivery: Get the electronic proof of delivery (ePOD) of one order: status and status time/GPS, who signed, signature and photo links (valid 24 h), driver comment, reject reasons, delivered vs ordered goods quantities, cash collected, customer feedback and the PDF delivery-note link (Repor
- trackpod_list_reject_reasons: List the account's reasons for not delivering / not collecting: site, order, goods and scanning issues (GET /RejectReason).
- trackpod_list_routes: List the routes of one day (GET /Route/Date/{date}): code, status (Draft, Ready, Loaded, InProgress, Closed), driver, vehicle, planned vs actual start/finish, distance, cost, current GPS position, and per-route order counts by status. Paged here (offset/limit).
- trackpod_get_route: Get one route with its status, driver, vehicle, timings, distance, cost, current GPS position and its orders. Pass exactly one of route_code or route_id (GET /Route/Code|Id/{…}).
- trackpod_get_route_track: Get the driver's recorded GPS track of a route (latitude, longitude, speed in m/s, time) — GET /Route/Track/Code|Id/{…}. Pass exactly one of route_code or route_id. Points are paged here (offset/limit, max 1000 per call).
- trackpod_list_drivers: List the account's drivers: name, username, phone, vehicle, depot, zone, teams and active flag (GET /Driver). Paged here.
- trackpod_get_driver: Get one driver by Track-POD id (UUID) or by username (GET /Driver/Id/{id} or /Driver/Username/{username}). Pass exactly one.
- trackpod_list_vehicles: List the account's vehicles: plate number, assigned driver, depot, capacity (weight/volume/pallets/size), limits, costs, type and carrier (GET /Vehicle, optional plate-number filter). Paged here.
- trackpod_get_vehicle: Get one vehicle by its Track-POD id (an integer, from trackpod_list_vehicles) — GET /Vehicle/{id}.
- trackpod_list_vehicle_checks: Driver vehicle inspections (before/after route): checklist items with pass/fail, notes, photo links (valid 24 h), odometer and signature. date only: every check of that day (GET /VehicleCheck/Date/{date}); date + vehicle_number: that vehicle's checks of the day; vehicle_number on
- trackpod_create_order: Create ONE REAL unscheduled order in Track-POD (POST /Order): a delivery or a collection for a client at an address, ready to be planned into a route by a dispatcher. It does not create or optimise routes. Depending on the account's notification settings the customer may later re

Screening checks:
- MCP handshake: pass (Answered in 1564ms)
- Domain against threat feeds (Cloudflare security DNS): pass (track-pod.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (16 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)