Detrack
Detrack is a delivery management software that offers real-time vehicle tracking, electronic proof of delivery, and automated customer notifications.
Verdict
Common use cases
- Triage failed deliveries from Slack or email
- Bulk-schedule collections for next-day pickup
- Audit delivery status across multiple dates
- Delete test jobs before go-live
- Search deliveries by customer or address
Integration
- Vendor
- Detrack
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
detrack
Tools
- Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
- Delete All Collectionsdestructive
Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.
- Delete All Deliveriesdestructive
Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.
- Delete Deliverydestructive
Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
- Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
- List Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
- Search
Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.
- View All Collections
Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.
- View All Deliveries
Tool to view all deliveries for a specific date. use when you need to retrieve all delivery jobs on a given date.
- View All Vehicles
Tool to view all vehicles in the account. use when you need a complete list of your fleet with optional pagination.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations panel. 2. Select 'Add Integration' and choose Detrack from the list. 3. Log into your Detrack account, go to Settings > API, and copy your API key. 4. Paste the key into Switchy's Detrack configuration form and click 'Connect'. 5. Switchy will verify the key and confirm the connection. 6. Open any Space, type '@Detrack list jobs for today' and send — if you see a job list or a 'no jobs found' response, the integration is live. 7. You can now invoke any of Detrack's ten tools by @mentioning the integration and describing the task in plain language.
What teammates see: by default, memories from Detrack are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Today's Jobs
@Detrack list all jobs for today. Show me delivery order number, status, and customer name for each.Open in a Space →
Add New Collection
@Detrack add a collection for tomorrow at 123 Main St, customer John Doe, phone 555-1234, pickup window 9am to 11am.Open in a Space →
Search by Address
@Detrack search for all jobs with 'Elm Street' in the address from the past seven days.Open in a Space →
Bulk Delete Deliveries
@Detrack delete all deliveries scheduled for January 15th. Confirm before proceeding.Open in a Space →
Edit Delivery Details
@Detrack edit delivery DO-4567 for today. Change the address to 456 Oak Ave and update the delivery note to 'Leave at side door'.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Detrack list all pending deliveries for today in Singapore and show me the top 5 by priority
Found 23 pending deliveries scheduled for today in Singapore. Top 5 by priority: (1) D.O. #SG-4521 to Orchard Road, priority: urgent, customer: Acme Corp; (2) D.O. #SG-4518 to Jurong West, priority: high, customer: BuildCo; (3) D.O. #SG-4515 to Tampines, priority: high, customer: RetailHub; (4) D.O. #SG-4509 to Woodlands, priority: medium, customer: LogiTech; (5) D.O. #SG-4502 to Changi, priority: medium, customer: FastShip. All deliveries are assigned to active drivers and awaiting dispatch.
This example uses the List Jobs tool with date and country filters. The MCP requires a valid API key with read permissions. Response shape depends on your account's delivery volume and field configuration—actual results may include additional custom fields or fewer deliveries if your schedule is lighter.
@Detrack delete all deliveries scheduled for March 15th after confirming there are no active jobs for that date
Checked March 15th: found 8 deliveries, all marked 'completed' or 'cancelled'—no active jobs in progress. Proceeding with bulk deletion. Successfully deleted 8 deliveries for March 15th. This action is irreversible; delivery records and associated proof-of-delivery data have been permanently removed from your Detrack account.
This example demonstrates the Delete All Deliveries tool, which is destructive and cannot be undone. The MCP will not auto-confirm deletions—you must explicitly approve the action in your prompt. Use this workflow carefully during end-of-month cleanups or when resetting test data. Rate limits apply to bulk operations.
@Detrack pull all collections from the past week and draft a summary report highlighting any that are still marked incomplete
Retrieved 47 collection jobs from March 10-16. Of these, 44 are completed, 3 remain incomplete: (1) Collection #C-1032 from Marina Bay, scheduled March 12, status: driver reported access issue; (2) Collection #C-1041 from Toa Payoh, scheduled March 14, status: customer rescheduled; (3) Collection #C-1045 from Bukit Timah, scheduled March 15, status: pending driver assignment. Recommended action: follow up with customers on C-1032 and C-1041, assign driver to C-1045 before end of day.
This example pairs the View All Collections tool with AI reasoning to synthesize a status report. The MCP returns raw collection data; the AI interprets status flags and suggests next steps. Useful for daily standups or operations reviews. Ensure your API key has collection-read scope enabled.
Use-case deep-dives
When Detrack MCP saves time after a chaotic delivery day
A 6-person courier service runs 40-80 deliveries daily across two cities. At end-of-shift, the ops lead needs to reconcile completed jobs, cancel duplicates, and prep tomorrow's manifest. The Detrack MCP wins here because it exposes bulk delete and edit tools that let the AI handle the tedious reconciliation work—'delete all failed deliveries from today', 'update 12 delivery addresses that came in via email'—without opening the Detrack dashboard. The threshold: if your team runs fewer than 20 jobs a day, the manual UI is faster than teaching the AI your workflow. If you're above 30 jobs and dealing with frequent same-day changes, this MCP turns a 20-minute admin task into a 3-minute conversation.
Why this MCP fits weekly status rollups but not real-time tracking
A 3-person fulfillment team holds a Friday ops review to analyze delivery performance across the week. They need counts by status, breakdowns by country, and a list of outstanding collections. The Detrack MCP's List Jobs and Search tools handle this well—the AI can pull filtered job lists, aggregate counts, and surface outliers without manual CSV exports. The catch: Detrack's API doesn't stream live vehicle locations or driver ETAs, so this MCP won't replace a real-time dispatch board. Use it for retrospective analysis and bulk data prep, not for in-the-moment route decisions. If your review cadence is weekly or slower and you're tired of exporting spreadsheets, this MCP is the right call.
When this MCP answers 'where's my package' faster than your dashboard
A 2-person e-commerce support team fields 15-30 delivery status inquiries daily. Customers email tracking numbers or order IDs, and the team needs to confirm delivery status, update addresses, or flag failed attempts. The Detrack MCP's Search tool lets the AI look up jobs by delivery number, date, or recipient name in seconds—no context-switching to the Detrack portal. The trade-off: if your support volume is under 10 inquiries a day, the setup overhead isn't worth it. Above 15, especially if inquiries come via Slack or email where the AI already lives, this MCP cuts average response time from 3 minutes to 30 seconds. Best fit for teams where delivery lookups interrupt other work.
Frequently asked
What does the Detrack MCP do in Switchy?
It connects Switchy to your Detrack delivery and collection management system. You can add, edit, delete, and search deliveries or collections, list jobs by status or date, and bulk-delete entries for a specific date. The MCP surfaces Detrack's scheduling and tracking data so your team can query it or update routes without leaving the AI workspace.
Do I need admin access to connect Detrack?
You need an API key from your Detrack account, which typically requires admin or owner permissions to generate. Once you have the key, paste it into Switchy's connection flow. Detrack doesn't use OAuth, so there's no scope selection—the key grants full read-write access to deliveries, collections, and vehicles in that account.
Can the MCP update delivery statuses or driver assignments?
Yes, the Edit Delivery tool lets you modify delivery details by date and delivery order number, including status and driver fields. You can batch-edit up to 100 deliveries per call. It won't automatically push GPS updates or proof-of-delivery photos—those still happen in the Detrack driver app—but you can change scheduled times, addresses, and metadata from Switchy.
How is this different from using Detrack's web dashboard?
The MCP brings Detrack data into Switchy's conversational interface, so you can ask questions like "show me failed deliveries yesterday" or "delete all collections for March 15" without clicking through the Detrack UI. It's faster for bulk operations and ad-hoc queries, but you'll still use the dashboard for visual route maps and detailed analytics.
Who on the team should connect this MCP?
Whoever manages your delivery schedule or dispatch operations. Since the API key grants full write access—including bulk delete—you probably don't want every team member connecting it. One logistics lead or operations manager should set it up, then share the Switchy workspace with drivers or customer service reps who only need read access to job lists.