# Upper Route Planner MCP by usefulapi

> Upper Route Planner MCP by usefulapi is an MCP server. Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/upper-route-planner/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/upper-route-planner
- **MCP Registry name:** io.usefulapi/upper-route-planner
- **Listing updated:** 2026-11-13

## About

Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http upper-route-planner https://upper-route-planner.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://upper-route-planner.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "upper-route-planner": {
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "upper-route-planner": {
      "type": "http",
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "upper-route-planner": {
      "serverUrl": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "upper-route-planner": {
      "type": "http",
      "url": "https://upper-route-planner.usefulapi.io/mcp"
    }
  }
}
```

## 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 active stops are returned. Upper has no paging, so this tool pages locally: `limit` stops (default 100, max 500) startin
- `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-route.
- `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 flags the route for re-optimization; stops on an active route cannot be edited. POST /ext-update-stop.
- `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. POST /ext-assign-drivers.
- `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 returned. POST /ext-optimize-route.
- `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 /ext-share-to-driver.

## FAQ

### How do I add Upper Route Planner MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http upper-route-planner https://upper-route-planner.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/upper-route-planner-mcp-by-usefulapi
