For Claude, ChatGPT and code editors

Send us your loads from Claude or ChatGPT

Connect Peer to your assistant, then ask it to send us the shipments in your spreadsheet, order export or email. We review every one and email you questions or a quote. No price comes back through the API, and nothing gets booked without you.

https://www.peer-freight.com/api/mcp

In Claude: Settings, Connectors, Add custom connector. Setup for ChatGPT and code editors is below.

Setup

Connect your assistant

It takes about a minute, and you only do it once.

Claude

Works on claude.ai and in the Claude apps.

  1. In Claude, go to Settings, then Connectors.
  2. Choose Add custom connector, name it Peer Freight, and paste the URL.
  3. Open a new chat and ask it to send us a shipment.
https://www.peer-freight.com/api/mcp

ChatGPT

On paid plans. Set it up once on chatgpt.com.

  1. In ChatGPT, go to Settings, then Apps & Connectors, then Advanced, and turn on Developer mode.
  2. Choose Create, name it Peer Freight, paste the URL and pick No authentication.
  3. In a new chat, open the plus menu, then More, then Developer mode, and switch on Peer Freight.
https://www.peer-freight.com/api/mcp

Cursor

One click, then confirm.

  1. Opens Cursor with Peer Freight filled in.
  2. Click Install.

Claude Code

One command.

  1. Run it in your terminal.
  2. Add --scope user to use it in every project.
claude mcp add --transport http peer-freight https://www.peer-freight.com/api/mcp

VS Code

Available in Agent mode.

  1. Opens VS Code and asks you to confirm.
  2. Pick it in the Tools menu of a chat.
Other clients JSON config for any app that supports MCP.
{
  "mcpServers": {
    "peer-freight": {
      "type": "http",
      "url": "https://www.peer-freight.com/api/mcp"
    }
  }
}

Ask

Things to ask it

Copy one into your assistant, or write your own. It works from whatever you already have: a spreadsheet, an order export, an email thread.

One load

“Send Peer a quote request for two crated pumps, 1,200 lb total, from Fresno, CA 93701 to Reno, NV 89501, picking up October 15. Use our shipping contact and tell me what Peer still needs.”

A spreadsheet

“Read the shipments in this spreadsheet and send them to Peer as one submission. Use only what is in the file, mark anything you don’t know as unknown, and give me the ticket reference and the open questions.”

Follow up

“Check submission SUB-7K3M9Q2XH4PZ8RTVWD2B with Peer and tell me which loads still have open questions.”

Build it in

“Read peer-freight.com/mcp.md and write a script that validates and sends our daily order export to Peer, grouped into one submission per day, with safe retries.”

What happens after you ask

Your assistant fills in our form so you don’t have to. Everything after that is a person at Peer, by email.

It maps your data

We publish every field, the units, and what counts as unknown. Your assistant fills them from your source and never guesses a weight or a date. A reviewer on our side reads each load and asks what a careful broker would, such as how copper scrap is staged before pickup.

One ticket per batch

One load or fifty in a submission. You get one receipt email, one ticket reference, and a reference for every load.

We reply by email

Questions and quotes come from team@peer-freight.com in the same thread. Your assistant can answer open questions from your records and check status by reference any time.

No price in the API

Rates come from a person after review. The connector never books a truck or promises capacity, and your assistant can’t accept a quote for you.

Prefer plain HTTP?

The same contract is available as JSON endpoints, with validation, idempotent retries and status by reference.

Rather type it in yourself?

The quote form takes the same details and lands on the same desk.

Have a load today?Get a Quote