Point any MCP HTTP client at https://traxelio.com/mcp, approve OAuth, and use the same public OpenAPI tools and scopes as REST. A Traxelio login is always required.
Traxelio exposes one MCP server at https://traxelio.com/mcp. Any assistant or IDE that speaks MCP over HTTP can connect to that URL, finish OAuth in the browser, and use the same public OpenAPI tools your account already reaches through REST.
One production URL for every MCP HTTP client
Tools come from the public Traxelio OpenAPI document, so MCP adds no capability the API does not already expose
OAuth works the way it does for the REST API, and the consent screen lists what you are granting before you approve
A Traxelio login is always required. There is no anonymous path into the server
Opening the server URL in a browser brings you to this page. Clients talk to the same URL with POST requests
Have these ready so the connection stays short.
A Traxelio account you can sign in to, in the browser your client will open
Any MCP client that can register a remote HTTP or streamable HTTP server
The production URL ready to paste, exactly https://traxelio.com/mcp
A few minutes for the browser consent screen, including the rows marked Read first
Connected Apps in Traxelio on your phone or in your web profile, where you revoke access later
The recipe is host-agnostic. Register Traxelio as a remote HTTP MCP server, approve OAuth, confirm tools loaded, then ask about your fleet. The named examples below only show how a few popular clients phrase that same recipe.
Use the production URL exactly: https://traxelio.com/mcp
Register it as a remote or streamable HTTP server, not as a local command
Approve the OAuth consent screen your client opens in the browser
Wait for the tool list to load in the client
Ask a concrete question about your fleet, for example the last trip of a vehicle you already track
Revoke the connection under Connected Apps when you are done (phone Settings or web profile)
One example of a settings UI that takes a remote MCP URL.
Open Cursor and go to Settings, then MCP
Add a new MCP server
Paste https://traxelio.com/mcp as the server URL
Complete the OAuth consent flow the client opens in your browser
Wait for the Traxelio server to show as connected and for its tools to populate
One example of registering an HTTP MCP server from a CLI.
Run: claude mcp add --transport http traxelio https://traxelio.com/mcp
Authenticate the traxelio server from the client's MCP panel (often /mcp)
Approve the Traxelio consent screen in your browser
Confirm the server shows as connected
One example of a CLI that takes a URL flag, then a separate OAuth login.
Run: codex mcp add traxelio --url https://traxelio.com/mcp
Run: codex mcp login traxelio and approve the consent screen in your browser
Confirm the traxelio server is registered (for example with codex mcp list)
Some CLIs store the entry in a local config file under a url key if you need to inspect it
One example of a JSON config file that declares a remote server with a host-specific key name.
Open the client's MCP config (in Antigravity: MCP Servers, Manage, View raw config)
Add a Traxelio entry: "traxelio": { "serverUrl": "https://traxelio.com/mcp" }
Use the remote-server key your host documents. Antigravity uses serverUrl, not url
Save the config and reload MCP servers
If the client shows an Authenticate action, run it and finish OAuth in your browser
Confirm the Traxelio tools appear
If Allow access stays grey, Traxelio is asking you to open every row marked Read first. Those rows cover higher-consequence actions: updating your profile, stopping or resuming your vehicle's engine, removing devices from your account, and signing you out of a device. Expand each one, read the short description, then Allow access turns on.
Find the rows carrying a Read first badge
Open each of those rows to expand the description
Read what the action does before you approve it
When the orange reminder disappears, choose Allow access
To stop the connection later, revoke it under Connected Apps on your phone or web profile
Access ends when you revoke it, not when you close the client. You can revoke from Traxelio on your phone or from your web profile. Same list, same result.
On your phone: open Traxelio, then Settings → Connected Apps
Or on the web: open https://traxelio.com/user/profile and find Connected Apps
Tap Remove on the client you want to cut, then confirm
Revocation applies immediately, and the next call from that client fails
Reconnecting means running the OAuth flow again
Most failed connections come from the URL, the transport type, or a consent screen that was never finished.
That is the expected result. People get this page, clients POST to the same URL. Paste the URL into your MCP client instead of visiting it.
Check that the server URL is exactly https://traxelio.com/mcp, then add the server again in your client.
Clients load the tool list after the connection is approved. Give it a moment, then reload the Traxelio server in your client.
Rows marked Read first are still closed. Open each one, then the button turns on. That gate is intentional, not a broken button.
Remote MCP key names differ by client. Some want url, some want serverUrl, some use a settings form with no JSON. Follow your client's docs for a remote HTTP server, and keep the Traxelio value as https://traxelio.com/mcp.
Choose the remote or streamable HTTP option. Traxelio MCP is not a local binary to launch.
On your phone open Settings → Connected Apps, or on the web open Connected Apps on your profile. Tap Remove, confirm, and access stops immediately. Do not wait for a token to expire.
Use cases
FAQ
Next Steps
Set up Traxelio in the right order: verify vehicles, add alerts, invite the team, read the dashboard, and build the first month of operating data.
Choose GPS tracking by matching tracker hardware, monthly price, alerts, mobile access, and support to the way your fleet actually works.
Buy a GPS tracker or connect compatible hardware you already own.