Freigent exposes a Model Context Protocol (MCP) server at:
https://app.freigent.ai/api/mcpPoint an MCP client at it and your assistant can work your load offers by email and review your pending tasks, for the one company you pick when you sign in. The server enforces the same company scoping as the app.
What It Can Do
The server has 11 tools: list_load_offers, get_load_offer, negotiate_load,
draft_offer_reply, reply_to_offer, mark_load_booked, set_follow_up,
list_pending_tasks, get_task_details, review_task and search_docs.
- Load offers by email: list the offers in your connected inbox, open one, work out a counter from your own numbers, draft the reply, send it after you approve it, set a follow-up reminder, and mark the load booked.
- Your task queue: list pending tasks, see why the AI proposed each one, and decline them one at a time.
It does not search load boards, plan trucks, assign drivers, read or send rate confirmations, or run invoicing or compliance; those stay in the Freigent app.
What It Deliberately Cannot Do
The same human-held rules as the app apply, plus chat-specific guards:
- Accounting and money tasks can be declined from chat but are approved in the Freigent app, never rubber-stamped from a chat. Approving a held AI reply also opens the task in the app.
- Protected Safety tasks (drug tests, accident investigations, FMCSA items and their kin) are completed in the Freigent app through their dedicated paths, not from chat. So are driver assignment and repower tasks.
- One item at a time. Each task is approved or declined on its own, by name; "approve all" is refused.
- Sends only what you approve. A counter below your minimum is refused, replies never include your minimum, the shipper rate, links or other email addresses, and they go only to the broker on file or their company.
Connecting a Client
MCP clients authenticate via OAuth (the /api/mcp/oauth endpoints); most clients
handle the flow when you add the server URL above. Example for Claude Code:
claude mcp add --transport http freigent https://app.freigent.ai/api/mcpOrganization API keys are for Freigent-built integrations; contact support.
You will sign in with your Freigent account and approve the org scope. Everything the client can see and do is bounded by your own membership, the server enforces org isolation server-side, the same as the web app.