Navitag MCPREAD-ONLY

Connect your Navitag account to an AI assistant. This page describes exactly what that connection can and cannot do.

Connecting

Add this as a custom connector in your AI client, then sign in with your Navitag account.

https://mcp.navitag.com/mcp

Authorization is OAuth 2.1 with PKCE, issued by https://oauth.navitag.com. Clients register themselves; there is nothing to configure by hand.

What it can do — 10 tools

get_day_summary — Daily driving summary

Summarises one device on one date: distance travelled, engine running time, moving and idling time, stops with their locations and durations, top and average speed, and a timeline of alerts (ignition, power cut, low battery, GPS loss, SOS, speeding). Use this for "how far did it go", "where did it stop", "what happened yesterday" questions. Returns summarised figures, never raw GPS points.

  • imei optional — Device IMEI (exact match).
  • name optional — Device name (case-insensitive, partial match allowed).
  • date optional — Local calendar date as YYYY-MM-DD. Defaults to today in UTC, which may be a day behind the user — pass their local date when you know it. Future dates are rejected, and history is limited to the last 31 days on the basic plan or 90 on pro.
  • timezone optional — IANA timezone, e.g. Asia/Manila. Omit to let the account profile decide, which is usually correct.

get_device — Get one device

Looks up a single device by IMEI or by name. Use this when the user names one vehicle rather than asking about the whole fleet.

  • imei optional — Device IMEI (exact match).
  • name optional — Device name (case-insensitive, partial match allowed).

get_device_status — Subscription and expiry

Reports when each owned device's tracking subscription and mobile data expire, and which plan it is on. Use this for "when does it run out" or "do I need to renew" questions.

  • No parameters.

get_location — Where is a device now

Returns the most recent known position of one device: coordinates, address if available, speed, whether the engine is on, and how long ago the fix was taken. Use this for "where is my car" questions.

  • imei optional — Device IMEI (exact match).
  • name optional — Device name (case-insensitive, partial match allowed).

get_notification_settings — Alert settings

Shows which alerts this account will receive and for which devices: the master switch, the emergency switch, and the per-device event rules.

  • No parameters.

list_devices — List devices

Lists every GPS device visible to this account: devices the user owns, and devices other people have shared with them. Each entry includes the IMEI, name, model, online status, and when it last reported. Shared devices also carry the permissions the owner granted.

  • include_shared optional — Include devices shared with this user by other accounts. Defaults to true.
  • status optional — Filter by current status. "unknown" means the device has not reported recently enough for the server to classify it. Defaults to all.

list_energy_logs — Fuel, charge and odometer logs

Lists the fuel fill-ups, EV charges and odometer readings recorded for one device in a calendar month, newest first. Use this for running-cost and consumption questions.

  • imei optional — Device IMEI (exact match).
  • name optional — Device name (case-insensitive, partial match allowed).
  • month optional — Month as YYYY-MM. Defaults to the current month.
  • timezone optional — IANA timezone. Omit to let the account profile decide.

list_geofences — List geofences

Lists the zones this account has defined. Geofences apply to every device the user owns. Use this to answer what areas are being watched.

  • No parameters.

list_permissions — List sharing permissions

Shows device sharing in both directions: devices this user has shared with other people (and what those people can do), and devices other people have shared with this user.

  • direction optional — Which side of sharing to report. Defaults to both.

whoami — Account summary

Returns the connected Navitag account: plan tier, how many devices it owns, how many are active, and the geofence allowance. Call this first when you need context about the account before answering.

  • No parameters.

What it cannot do

This is enforced by the server, not by instructions to the model: no write operation is exposed, and the access token carries a read-only scope (fleet.read).

Rate limits

5 requests per second
Per connected client. Bursts above this are refused immediately.
120 requests per 60 seconds
Per account, across every client you connect — so adding a second assistant does not double the load on the tracking servers.

Exceeding either returns HTTP 429 with a Retry-After header. Well-behaved clients back off automatically.

Privacy and control

What it reaches
Only the Navitag account that authorised it, through the same API the phone app uses. Every ownership check, sharing scope and plan limit applies exactly as it does in the app.
What is stored here
The OAuth grant, and one audit row per tool call recording who called what, when, and whether it succeeded. Tool arguments are not stored — they can name vehicles and dates.
History limits
Trip history is capped by plan: 31 days on basic, 90 on pro. Future dates are refused.
Revoking
Disabling or deleting the Navitag account immediately kills this connection too. The grant is re-checked from the database on every single tool call, so a revocation takes effect at once rather than when the token expires. A self-service disconnect screen is not built yet.

Machine-readable

The same manifest as JSON: https://mcp.navitag.com/capabilities

Navitag MCP server v0.2.0 · navitag.com