INDIVIDUAL MCP TOOL

optimoroute_send_routes

Dispatch the routes for a date to the drivers' mobile app (the web app's Send Routes).

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://optimoroute.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for optimoroute_send_routes and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.
A tool name or description suggests sending messages.

Parent server

usefulapi.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.optimoroute-mcp]
url = "https://optimoroute.usefulapi.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "optimoroute-mcp": {
      "type": "http",
      "url": "https://optimoroute.usefulapi.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: optimoroute-mcp
Remote MCP URL: https://optimoroute.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "optimoroute-mcp": {
      "url": "https://optimoroute.usefulapi.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "optimoroute-mcp": {
      "type": "http",
      "url": "https://optimoroute.usefulapi.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "optimoroute-mcp",
  "transport": "streamable-http",
  "url": "https://optimoroute.usefulapi.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

optimoroute_get_routes — Get the planned routes for one date: per driver/vehicle the duration, distance, loads and the ordered list of stops with scheduled times.
optimoroute_get_orders — Fetch full order data (location, time windows, assignment, loads, skills, contact) for up to 500 orders by orderNo or id.
optimoroute_search_orders — Find orders in a date range (at most 35 days) or by a list of orderNo/id, optionally filtered by status (e.
optimoroute_get_scheduling_info — Is this order scheduled, and if so on which driver/vehicle, at which stop number and time, plus the live ETA from the routes sent to drivers.
optimoroute_get_completion_details — Get the completion status of up to 500 orders (unscheduled, scheduled, on_route, servicing, success, failed, rejected, cancelled) with service start/end times and positions, proof-of-delivery form data (notes, signature and photo URLs, barcodes), the tracking URL and optionally customer feedback.
optimoroute_get_events — Read driver-app events for the live routes — on_duty, off_duty, start_route, end_route, start_service, success, failed, rejected, start_time_changed — up to 500 per call.
optimoroute_get_planning_status — Check a planning (route optimization) run started with optimoroute_start_planning: status N new, R running, C cancelled, F finished, E error, plus percentageComplete.
optimoroute_get_dispatch_status — Have the routes (and customer notifications) for a date been sent to drivers, when, and are they the live routes?