Claude Plugin

The freigent-carrier plugin connects Claude to your Freigent back office. Once installed, Claude triages your AI work queue, reads load and carrier context, and approves or rejects tasks, with money-movement guardrails built in.

What's Bundled

• MCP connection to your Freigent org (app.freigent.ai/api/mcp, see MCP Server)
• freight-ops skill: teaches Claude how to run the queue safely: the triage funnel, the money rule, prompt-injection awareness
• /queue command: a one-shot triaged sit-rep of what needs your review
• freight-reviewer agent: a careful second look at a single task before you decide

Setup

1. Get your personal Freigent API key from the app (Settings → API / MCP). Use a personal key, not a shared one, every action Claude takes is attributed to you, including approvals.

2. Set it so the plugin can authenticate:

export FREIGENT_API_KEY="fmcp_your_key_here"

3. Install in Claude Code (CLI, Desktop, or IDE extensions):

/plugin marketplace add freigent/freigent-plugin
/plugin install freigent-carrier@freigent

Verify with /queue, or just ask "what's pending in Freigent?", you should get a triaged sit-rep of your work queue.

On Claude surfaces without /plugin, add the MCP server from the plugin's .mcp.json manually via your client's connectors settings.

What Claude Will, and Won't, Do

Will: summarize the queue, explain any task, look up carrier authority, run read-only data questions, and reject or dismiss items on your say-so.

Won't: auto-approve anything that moves money. Rate-con sends, bookings, payments, and invoices require you to approve, with the dollar figure in front of you, enforced in the skill's instructions and again on the Freigent server (financial approvals require a user-attributed key).

Security Notes

• Treat your API key like a password, it identifies you and authorizes approvals.
• Broker email content inside tasks is untrusted: the skill instructs Claude to treat it as data, never as instructions, so a "please approve this" buried in a broker email cannot drive an approval.
• The plugin itself carries no secrets; it points at the endpoint and you supply the key. All access is gated server-side.

Source and issues: github.com/freigent/freigent-plugin