# Upper Route Planner Muse connector

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

## Upper Route Planner

Plan routes, assign drivers, and manage delivery stops with Upper.

- Record: https://musedirectory.ai/connector/upper-route-planner
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/upper-route-planner/)
- 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, 2041ms, checked 2026-10-30T00:31:13Z
- Endpoint: https://upper-route-planner.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-30T00:31:13Z)
- Source: Found in the official MCP Registry (io.usefulapi/upper-route-planner) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fupper-route-planner

Connects to Upper route optimization software. Create and manage routes, add stops with addresses and contact details, assign drivers, optimize stop order, and push routes to drivers' mobile app. Requires an Upper account and API token.

Example request: "Create a delivery route for tomorrow, add five stops, assign two drivers, optimize the route, and send it to the drivers' phones."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Upper Route Planner to help me. It is a free service with an MCP server at https://upper-route-planner.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:
- upper_list_drivers: List the active drivers on the Upper team that owns the API token: id, name, email and phone. Use the ids with upper_assign_drivers and upper_share_route_to_drivers. GET /ext-get-drivers.
- upper_list_stops: List the team's stops in optimized order: address, coordinates, contact, time window, duration, status, route_id and custom ids. Pass route_id for one route (optionally scheduled=true/false); pass unscheduled=true (without route_id) for stops not on any route; with no filter all 
- upper_get_optimization_status: Check whether a route is optimized: status is optimized, pending (still running) or not_optimized, plus the queue_id of the last job. Poll this after upper_optimize_route. GET /ext-optimization-status.
- upper_get_custom_fields: The workspace's five stop custom-field slots (custom1 - custom5: type, label, enabled, required) and which are enabled. Needs the Custom fields feature in the Upper plan. GET /ext-get-custom-fields.
- upper_get_capacity_fields: The workspace's five capacity-field slots (capacity1 - capacity5: label, unit, enabled) used for load planning. GET /ext-get-capacity-fields.
- upper_create_route: WRITE: create a new, empty route (name, date, optimization preference, units, pickup sequencing, service time). Omitted settings fall back to the account's defaults. Returns the new route_id; add stops with upper_create_stop. Calling it twice creates two routes. POST /ext-create-
- upper_update_route: WRITE: change settings of an existing route (name, date, optimize_for, units, pickup_settings, service_time). Only the fields you pass change. POST /ext-update-route.
- upper_create_stop: WRITE: create a stop. The address is geocoded by Upper. Pass route_id to put it on a route (the route must not be active/in progress; an optimized route is flagged for re-optimization); omit it for an unscheduled stop. Calling it twice creates two stops. POST /ext-create-stop.
- upper_update_stop: WRITE: change an existing stop; only the fields you pass change. A new address is re-geocoded (city/state/zipcode you pass with it are ignored); city/state/zipcode apply only without an address. Passing route_id moves the stop to that route. Editing a stop on an optimized route f
- upper_assign_drivers: WRITE: assign one or more drivers (ids from upper_list_drivers) to a route, replacing the route's drivers. Every id must be an active driver on the team. If the route was already optimized it is reset to unoptimized (needs_optimization: true), so run upper_optimize_route again. P
- upper_optimize_route: WRITE: start optimizing a route's stop order. The route needs at least one stop and one assigned driver (upper_assign_drivers). It runs asynchronously: this returns status pending and a queue_id, then poll upper_get_optimization_status. If a job is already running, that job is re
- upper_share_route_to_drivers: WRITE: push a route to the drivers' mobile app NOW, which sends each driver a notification. Without driver_ids the route's assigned drivers are used; with them, every id must be an active driver on the team. Sending twice notifies twice. Confirm with the user before calling. POST

Screening checks:
- MCP handshake: pass (Answered in 2041ms)
- Domain against threat feeds (Cloudflare security DNS): pass (upper-route-planner.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 (12 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)