Agent plugins¶

A plugin installs the connector and the workflow guidance together, in one command — so your assistant does not only have the tools, it knows how Freight Right expects them to be used. Six clients install it: Claude Code, Codex, GitHub Copilot CLI, Cursor, Grok and Muse Code.

Testing an integration against staging?

The plugin ships the production URL, https://mcp.freightright.com/mcp. Developers who want the staging connector beside it add that one by hand — the exact command or file for each client is on Developer tools, under a different server name so the two never collide. The skills work with either.

The connector on its own gives an assistant sixteen tools. The plugin adds the judgment that goes with them: which of two organization lists a shipment is billed through, that repeating a price check costs nothing, that an estimate that has passed is not a delay, that an administrator names the organization to bill, and that no tool here can book freight on your behalf.

Claude Code¶

Add the marketplace and install the plugin
```
claude plugin marketplace add freight-right/agent-plugins
claude plugin install freightright@freightright
```
Inside a session, /plugin marketplace add freight-right/agent-plugins does the same thing.
Sign in Run /mcp, choose freightright, and sign in with your Shipment Manager account. There is no key or secret to paste — the plugin contains no credentials.
Give it room to answer Set your tool timeout to at least 60 seconds. A price check asks carriers live, and a slow lane genuinely takes that long.

Already added the connector by hand?

Remove your existing server first — claude mcp remove freight-right. Two copies of the same connector means two sign-ins and two sets of tools, and your assistant will not know which to use.

Codex¶

codex plugin marketplace add freight-right/agent-plugins
codex plugin add freightright@freightright

GitHub Copilot CLI¶

copilot plugin marketplace add freight-right/agent-plugins
copilot plugin install freightright@freightright

Grok¶

grok plugin marketplace add freight-right/agent-plugins
grok plugin install freightright@agent-plugins --trust

Grok reads the portable manifest, so it needs nothing specific to it. --trust is Grok's own confirmation that a plugin may run skills and MCP servers on your machine.

Cursor¶

cursor-agent plugin marketplace add https://github.com/freight-right/agent-plugins

Cursor takes a full git URL rather than owner/repo, and indexes the default branch unless you pass --git-ref <branch|tag>. A marketplace is added per account; enable the plugin from the plugin list in Cursor. A listing on the Cursor marketplace itself is pending; until then the git URL above is the way in.

Muse Code¶

Muse Code's plugin commands are a developer preview: in 1.3.0 every muse plugins call — install, update, remove — runs only with MUSE_EXPERIMENTAL_PLUGINS=1. A session loads the installed plugin without the flag.

MUSE_EXPERIMENTAL_PLUGINS=1 muse plugins marketplace add freightright freight-right/agent-plugins
MUSE_EXPERIMENTAL_PLUGINS=1 muse plugins install freightright@freightright

The install prints a dozen warnings — multiple-manifests, agent-overlay-inactive, and one unsupported-capability for the MCP server. They are expected: Muse Code reads the portable manifest, notes the other clients' files beside it, and installs the five skills. What it does not do yet is start a plugin's HTTP MCP server, so the connector goes into ~/.config/muse/settings.json and you sign in from the command line:

{
  "schema_version": 1,
  "mcpServers": {
    "freightright": {
      "type": "streamable-http",
      "url": "https://mcp.freightright.com/mcp",
      "mode": "optional"
    }
  }
}

muse mcp login freightright

mode: optional keeps Muse Code starting when the connector is unreachable. Keep whatever else the file already holds, and never put required beside mode on the same entry — Muse Code drops the whole mcpServers member when it sees both.

What the skills cover¶

Skill	It knows
Connection and billing	What this connection may do — a customer's organizations or, for an administrator, every organization and the one to bill — and whether a price is billed to an organization or a company name
Instant pricing	What each mode needs, resolving places to codes, and what a price check costs
Quote requests	When only Freight Right's pricing team can answer, how to ask, and how to find a quote by organization, text or date
Booking handoff	Preparing a confirmation link, the expiry windows, which requests this connection may book, and reading what you decided
Shipment tracking	Searching by any reference, narrowing to one organization, and reading dates and milestones correctly

Your assistant loads a skill when it is relevant, so none of this takes up room until it is needed.

The connector it installs¶

Production Live

https://mcp.freightright.com/mcp

Your live Freight Right account: real shipments, real prices, real bookings. This is the URL used throughout these pages, and the one the agent plugins ship.

Staging Live

https://staging-mcp.sm.freightright.com/mcp

For developers testing an integration. Sign in with a staging Shipment Manager account; everything there is test data, and a booking placed there reaches nobody.

The plugin ships the production URL. To try an integration against staging, add the staging URL above by hand as a second server; the plugin's skills work with either.

Source¶

The plugin is open source under the MIT licence at github.com/freight-right/agent-plugins — the skills are plain Markdown, so you can read exactly what your assistant is told. The repository's README carries the compatibility matrix with the client versions each install was verified on. The repository is published with the production release; until then the link answers only to Freight Right's own GitHub members.