Zenduit Developer Reference

Trax Public MCP

Connect Claude — or any MCP client — to live fleet-telematics data (devices, drivers, trips, safety, maintenance, and more) through read-only tools generated straight from the API's own contract. Sign in once through a secure browser screen; there are no tokens to copy and no headers to configure.

Read-only — every tool is a GET tools generated from the live spec Secure OAuth sign-in
Overview

What this server does

trax-mcp-service exposes an MCP endpoint at /public/mcp. Every tool on it is generated automatically from the Trax Public API's OpenAPI spec — one tool per endpoint — so the catalog can never drift from what the API actually supports, and it grows the moment a new endpoint ships.

Tenant isolation is enforced by the API itself, from the access token's company_id claim — the model never chooses or supplies a tenant, and this server holds no shared credential of its own.

MCP endpoint
/public/mcp
Transport
HTTP Streamable
Sign-in
OAuth in your browser — or HTTP Basic for headless clients
Access
Read-only, automatically scoped to your company
Add the connector

Connect in about a minute

Connecting takes a browser and your company credentials — that's it. You add the server by its URL, then sign in on a secure Trax screen. There are no access tokens to mint, paste, or refresh by hand.

  1. Have a way to sign in. Most people use their own Trax account (the same email or username and password you use for Trax), and see only what their Trax role and groups allow. For company-wide access or automation, use a company-scoped client_id / client_secret issued by Zenduit — there's no self-service signup. Email support@zenduit.com to request a client for your company, and store the secret safely (it's shown once).

  2. Add the connector in your MCP client by pointing it at the endpoint. In Claude, open Settings → Connectors → Add custom connector and paste the URL:

    MCP endpoint (HTTP Streamable)
    /public/mcp

    Any MCP client that supports remote servers with OAuth works the same way — give it the URL and let it discover the rest. For scripts or automation tools without a browser, see Headless & automation.

  3. Sign in on the Trax screen. Your client opens a secure Trax sign-in page in your browser. Sign in with your Trax email or username and password (and your verification code, if two-step verification is on), or open Use company API credentials and enter the client_id and client_secret. Trax validates them and hands your client its access automatically. You never paste a token or edit a header.

    The Trax sign-in screen: a Client ID field, a Client secret field, and an Authorize button.
    The Trax sign-in screen — the only place your credentials are entered.
    i

    Your credentials are entered only on this Trax screen — never in a chat message — and the connector stores nothing. Once you're signed in, access refreshes automatically; you won't be asked again unless you disconnect.

  4. Start asking. Paste this credential-free prompt into the connected assistant to orient it. It contains no secrets — it just tells the model to discover its tools and what it can do.

    Starter prompt (safe to paste)
    You're connected to the Trax Public MCP server, giving you read-only access to my fleet-telematics data. Every tool is a GET, and results are automatically scoped to my company — you never handle credentials or choose a tenant.
    
    Start by listing your available tools so we both know the exact surface, then give me a one-line summary of what I can ask for. I can query data across devices, drivers, trips, safety events, maintenance, jobs, forms, diagnostics, locations, summaries, IFTA, and more.
    
    When I ask a question: pick the right tool(s), and if you need an ID first (a device, driver, zone, …) list to find it before fetching the detail. If a call is rejected for scope, tell me which scope the credential is missing.
How it works

What happens when you connect

You sign in once on the Trax screen. Trax checks your credentials, then issues your client a short-lived access token and keeps it fresh — so every later tool call just works. The server holds no shared key of its own, and your results are scoped to your company by the token, never by anything the model chooses.

Trax sign-in /connect (your browser) MCP client Claude / any MCP client trax-mcp-service /public/mcp trax-public-api your company's data 1  sign in once (OAuth) 2  access granted 3  tool calls (read-only) 4  scoped to your company
Tool catalog

Tools across your fleet domains

Every tool is a straight read against one Trax Public API resource. Scopes gate what a given client can call — request only what the integration needs. This list is generated live from the server's current tool set, so it never drifts from what /public/mcp actually exposes.

ToolWhat it returnsScope
Loading the live tool catalog…
Headless & automation

Connecting without a browser

For scripts, servers, or automation tools like n8n that can't open the browser sign-in, authenticate with HTTP Basic — your client_id:client_secret in the Authorization header. Trax exchanges them for an access token and refreshes it for you on every call, so you configure the credential just once.

  1. Base64-encode your client credentials.

    Terminal
    echo -n '<CLIENT_ID>:<CLIENT_SECRET>' | base64
  2. Send it as a header to the MCP endpoint. In n8n, use the MCP Client Tool node with Header Auth; in a config file or CLI, set the same header.

    Authorization header
    Authorization: Basic <output from step 1>
i

Each caller supplies its own credentials — the server stores no shared key, and your results are scoped to your company by the token it mints. Keep the secret in your client's credential store, never in a prompt.

Reference

Endpoints & discovery

MCP clients that support OAuth discovery configure themselves from these standard metadata documents — you normally never touch them directly. They're listed here as the source of truth for any integration.

DocumentURL
MCP endpointPOST /public/mcp
Protected Resource Metadata (RFC 9728)GET /.well-known/oauth-protected-resource
Authorization Server Metadata (RFC 8414)GET /.well-known/oauth-authorization-server
Live tool catalog (JSON)GET /public/tools
Troubleshooting

Common failure modes

SymptomCauseFix
The sign-in screen rejects your credentials The client_id / client_secret is mistyped, or the client isn't active Re-check both values (the secret is shown only once at issue). If it persists, contact support@zenduit.com
A tool call is rejected for scope Your credential doesn't include the scope that tool needs The error names the missing scope — request it for your client from support@zenduit.com
Your client never opens the sign-in screen / finds no OAuth It was added as a local/command server, or it doesn't support remote MCP servers with OAuth Add it as a custom / remote connector by URL. If the client can't do OAuth, use Headless & automation instead
You're asked to sign in again The connection was disconnected or its session ended (access otherwise refreshes automatically) Re-run the connector's sign-in once; no tokens to regenerate by hand
Headless request returns 401 Missing OAuth credentials The Authorization header is missing or malformed Send Authorization: Basic <base64 of id:secret> (or a Bearer token) — see Headless & automation