Skip to content
Menu
DEVELOPERS · PRO

Hosted MCP

Connect an authorized MCP client to your carrier workspace.

Connect a remote MCP client

  1. Use the hosted HTTPS endpoint at /api/mcp on your TruckerFetch origin.
  2. Complete the client’s OAuth sign-in flow. Check the requesting client, proposed scopes and selected account before approving.
  3. Try the read-only get_latest_edition tool, then search_carriers. Ask “Which edition was last published, and when was its source observed?”

In ChatGPT, choose a predefined OAuth client with ID truckerfetch-chatgpt. In Claude, choose “Use your own OAuth client” with ID truckerfetch-claude. Both use a public client, so leave the secret empty.

In Cursor, add this entry to the mcpServers object in mcp.json.

{
  "truckerfetch": {
    "url": "https://truckerfetch.com/api/mcp",
    "auth": {
      "CLIENT_ID": "truckerfetch-cursor",
      "scopes": [
        "data:read"
      ]
    }
  }
}

REST keys never belong in a chat prompt. Review or revoke connected apps under Connected apps.

Limits and errors

REST and MCP share account limits. Respect the retry interval on a 429 response. A 401 requires a valid credential. A 402 means the account lacks the required plan, and a 403 can indicate insufficient scope or archive access. Reauthorize after a revoked OAuth grant and replace expired REST keys in the dashboard.