Delopt delivery dispatch

io.transopt.delopt.apiPublished by api.delopt.transopt.ioOfficial publisherv1.0.5Updated Oct 24, 2026

AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Delopt is a remote MCP server for AI-driven food and local delivery dispatch, letting an assistant assign orders to drivers, sequence stops and time departures.

What you can do
Assign delivery orders to drivers through AI dispatch logic. Sequence stops along a route. Time departures for delivery runs. Connect over a remote endpoint, signing in with OAuth or supplying an API key.
When to use it
Useful when an assistant should help plan or adjust food and local delivery dispatch, such as choosing drivers, ordering stops or setting departure times for delivery runs.
Requirements
A remote streamable HTTP endpoint at api.delopt.transopt.io. Authentication is required: either OAuth sign-in through the client or a Delopt API key supplied in the x-api-key header. No local runtime or packages are needed.
Before you install
The server needs a Delopt API key (x-api-key) or OAuth sign-in; treat the key as a secret. Dispatch actions assign orders to drivers and set routes and departure times, so changes may affect real deliveries and drivers. Review any write actions before letting an assistant apply them.

Installation

In SourceWeft

  1. Open Delopt delivery dispatch in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.transopt.delopt.api%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "delopt-delivery-dispatch": {
      "type": "http",
      "url": "https://api.delopt.transopt.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v1.0.5LatestOct 24, 2026
  2. v1.0.4Oct 19, 2026
  3. v1.0.1Oct 14, 2026
  4. v1.0.0Oct 13, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.