Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app. For delivery and field-service dispatchers who plan driver routes in Upper Route Planner. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"upper-route-planner": {
"url": "https://upper-route-planner.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"upper-route-planner": {
"type": "http",
"url": "https://upper-route-planner.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI lists the stops that no route holds, with address, time window and service duration. You see what still needs planning.
upper_list_stops
The AI lists the stops of a route in optimized order with address, contact, time window and status.
upper_list_stops upper_get_optimization_status
Give a route name, a date and the addresses. The AI creates the route and adds each address as a stop for Upper to geocode.
Changes data · upper_create_route upper_create_stop
The AI assigns drivers to a route, starts the optimization of its stop order and polls until the route shows as optimized.
Changes data · upper_list_drivers upper_assign_drivers upper_optimize_route upper_get_optimization_status
The AI changes the address, time window or route of an existing stop. A stop on an optimized route flags that route for a new optimization.
Changes data · upper_list_stops upper_update_stop
After you confirm, the AI pushes the route to the drivers' mobile app, which notifies each assigned driver.
Changes data · upper_list_drivers upper_share_route_to_drivers
The login page asks for your Upper API token.
Find it in Upper (crew.upperinc.com) under Settings → Webhooks → API Token (copy button). The token gives full programmatic access to your Upper account, so treat it like a password. It is used only to call the Upper API on your behalf and is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Upper API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Upper Route Planner connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
upper_list_drivers | read | 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 | read | 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 active stops are returned. Upper has no paging, so this tool pages locally: `limit` stops (default 100, max 500) starting at `offset`; the reply says if more remain (truncated, next_offset). GET /ext-get-stops. |
upper_get_optimization_status | read | Get route 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 | read | Get stop 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 | read | 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 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-route. |
upper_update_route | write | 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 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 | 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 flags the route for re-optimization; stops on an active route cannot be edited. POST /ext-update-stop. |
upper_assign_drivers | write | Assign drivers to a route 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. POST /ext-assign-drivers. |
upper_optimize_route | write | 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 returned. POST /ext-optimize-route. |
upper_share_route_to_drivers | write | 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 /ext-share-to-driver. |
upper_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
upper_request_feature | Request a missing feature Tell usefulapi that the user needs something the Upper Route Planner tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
upper_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Upper Route Planner (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
upper_cancel_subscription | Cancel the Pro subscription Cancel the caller's Upper Route Planner Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run upper_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Upper Route Planner server only. Subscribe with upper_upgrade (it returns a Stripe Checkout link). Cancel any time with upper_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running upper_upgrade before then undoes the cancel. Or write to [email protected].
Find stops that are not on a route yet. Review the stops of one route. Set up tomorrow's route from a list of addresses. Assign drivers, optimize and wait for the result. Move or correct a stop. Send a finished route to the drivers' app. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Upper Route Planner. The server calls the Upper Route Planner API with your own Upper Route Planner access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Upper API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Upper API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Upper Route Planner API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Upper Route Planner.
Yes, if you approve it. 7 of the 12 Upper Route Planner tools can create or change data. The other 5 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Upper Route Planner server only. Cancel any time: Pro then runs to the end of the paid period. Run upper_usage_status to see how many calls you used.
Ask the AI to run upper_upgrade: it returns a Stripe Checkout link. To cancel, run upper_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with upper_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.