Home › MCP

Find any package in seconds — from Claude or ChatGPT

Connect your Cortex control tower to Claude and ChatGPT, live. Paste a tracking number and get the driver, route, address and proof of delivery instantly — then ask anything about your operation. Real-time, inside the AI you already use.

Claude · cortexdsp
who delivered TBA304…917 and did it reach the door?
Hernaldo Peña — Route CX12, delivered 18:04.
Beethovenstraat 400, 1082PR Amsterdam.
Marked delivered 19 m from the pin · handed to a neighbour (no in-hand scan). weak proof — flag for photo next time

One question. One answer. Straight from your live data — no digging through Amazon's panels.

Two pieces. That's the whole product.

① Extension

Pulls your operation out of Amazon

One Chrome extension, running on your own Amazon session. No servers, no shared credentials — in minutes your whole operation is captured, out of Amazon's slow, fragmented panels.

② MCP

Puts it inside your AI

The MCP lets Claude and ChatGPT read that live operation. Paste a package and find it; ask anything and get the answer from your real data, right now.

Capture, then ask. That loop is Cortex. There's a full dashboard too — but most days you'll never open it. You just ask.

Ask anything about your operation — live

Where's this package?Paste a tracking number → driver, route, address, proof of delivery, distance to the pin.
What DNR do I owe today?Open investigations, their deadlines and how strong the delivery evidence is.
Did we beat last week?DCR, POD, DNR and RTS compared week over week.
Who's dragging my scorecard?POD, DNR and RTS per driver, for any date range.
Who's on VRM / Mentor today?Live routes crossed with today's eMentor shifts.
What did we lose?Missing packages (PNOV) and the station mail that matters.

Connect it in 30 seconds

Works with Claude (Desktop or claude.ai) and ChatGPT via its MCP connector. Add your CortexDSP key and your live operation is one question away:

{
  "mcpServers": {
    "cortexdsp": {
      "command": "npx",
      "args": ["-y", "cortexdsp-mcp"],
      "env": { "CORTEXDSP_API_KEY": "your-key-here" }
    }
  }
}

No key, no data — every tool needs a valid CortexDSP key. The key is what scopes the answers to your DSP and nobody else's.

Included with Cortex

The MCP isn't a separate add-on — it comes with your Cortex subscription, same as the extension. One operation, answered by the AI you already use.

Get access →

Open client, your key, your data

The client is public on GitHub so you can see exactly what it does: it's a thin proxy with no credentials and no business logic. It talks to the CortexDSP API over HTTPS using your key — which lives only in your local config. Your customers' addresses are stored with an irreversible hash, and each DSP only ever sees its own operation.

Your whole operation, in your AI

Paste a package and find it. Ask anything and get the answer, live. That's Cortex — the extension captures it, the MCP answers it.

Get access