corporatetravel-dispatch-mcp

Right repo? You want corporatetravel-dispatch-mcp (this one) for the MCP server. The dispatch platform source lives at corporatetraveldc-dispatch. The public mirror is at ctdi-dispatch.

MCP server exposing the CS Executive Services dispatch platform and airplanes.live flight tracking as portable, agent-agnostic tools. Works with any MCP-compatible agent: Claude Code, Cline, Cursor, Zed, Windsurf, and others via mcpo → Open WebUI.

Tools (21 total)

Dispatch Platform — Tier 0 (no auth required)

Dispatch Platform — Watchlist

Admin (requires DISPATCH_TOKEN)

Flight Tracking — airplanes.live (no auth)

Hex resolution order: callsign → registration → hex. Always confirm hex via flight_get_by_registration before adding to watchlist — hex is airframe-bound; callsign-to-hex mappings can be stale day-over-day.

Related MCP server: Enterprise AI Bridge (MCP)

Install

pip install -e .

Requires Python 3.11+.

Configure

Context efficiency and plan compatibility

MCP tool responses are structured and compact — each tool returns only the data the agent actually needs, rather than dumping raw API payloads into the context window. This matters for subscription plan users:

• Claude Pro ($20/mo) — operational dispatch workflows (TFR checks, CPS queries, flight lookups, daily brief) stay well within the 5-hour message window because context stays lean. No API key required. Pairing with a context guardian skill (e.g. the dispatch-context-guardian Cowork skill bundled with this deployment) automatically compacts sessions before they hit plan limits, extending sessions significantly without manual intervention.

• Claude Max / API — no additional benefit from a guardian on that axis, but the compact responses still reduce per-request token cost and latency.

• Cline / Cursor / Windsurf — same economy applies; MCP tool calls consume far fewer tokens than equivalent REST-then-paste workflows.

The guardian angle is specifically useful for operators running continuous dispatch monitoring inside a chat session — without it, accumulated API responses and skill output would exhaust a Pro plan window in under an hour. With compact tool responses + guardian-triggered compaction, the same session can run for a full shift.

Use with Claude Code

Register at user scope (persists across projects):

claude mcp add dispatch \
  -e DISPATCH_BASE_URL=https://ops.csexecutiveservices.com \
  -e DISPATCH_TOKEN=your-token-here \
  --scope user \
  -- dispatch-mcp

Or add to ~/.claude/.claude.json directly under "mcpServers":

{
  "mcpServers": {
    "dispatch": {
      "type": "stdio",
      "command": "/full/path/to/dispatch-mcp",
      "args": [],
      "env": {
        "DISPATCH_BASE_URL": "https://ops.csexecutiveservices.com",
        "DISPATCH_TOKEN": "your-token-here"
      }
    }
  }
}

Use with Cline / Cursor / Zed / Windsurf

Same MCP JSON config block — each supports mcpServers in their settings file. Path the command to the installed dispatch-mcp binary or python -m dispatch_mcp.server.

Use with Open WebUI / Conduit

See docs/mcpo-openwebui.md for the mcpo bridge setup.

Verify syntax

python -m py_compile dispatch_mcp/server.py \
  dispatch_mcp/config.py \
  dispatch_mcp/client.py \
  dispatch_mcp/tools/dispatch.py \
  dispatch_mcp/tools/flight.py \
  dispatch_mcp/tools/admin.py
echo "All clean"

Notes

• Tier 0 endpoints (/api/v1/*) require no authentication.

• dispatch_get_runsheet is Tier 1 (Tailscale-gated): set DISPATCH_BASE_URL=http://100.94.80.100:8000.

• Admin endpoints require DISPATCH_TOKEN. Create tokens on the Pi: csex-token create.

• dispatch.csexecutiveservices.com has Cloudflare Access on POST routes; use ops.csexecutiveservices.com for programmatic access.

• CUI rules: this server never generates or exposes SHARES/HEARS/HEART frequencies. The platform ships with empty placeholder credential files.

License

MIT