Connect a remote MCP client
- Use the hosted HTTPS endpoint at
/api/mcpon your TruckerFetch origin. - Complete the client’s OAuth sign-in flow. Check the requesting client, proposed scopes and selected account before approving.
- Try the read-only
get_latest_editiontool, thensearch_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.