For the complete documentation index, see llms.txt. This page is also available as Markdown.

Navixy User MCP (navixy-user)

Monitor your fleet, check sensor readings, review track history, and inspect IoT Logic flows from your AI client, with a full reference of the tools available through Navixy User MCP.

Navixy User MCP connects your AI client to your Navixy user account. Use it to monitor your fleet, check sensor readings, review track history, inspect IoT Logic flows, and visualize live tracker positions — all from the AI client you already work in.

This page describes what Navixy User MCP can do and provides a full reference for all available tools (operations your AI client can perform), including parameter names and example prompts for developers building integrations. If you haven't set up the connection yet, refer to Getting started.

Endpoint: https://platform.mcp.navixy.com/user/mcp

See also:

What you can do with Navixy User MCP

Monitor your fleet

Get the current status of all your trackers or a specific set of them. Your AI client can tell you which trackers are online, moving, parked, or offline, along with their last known position, speed, heading, ignition state, and battery level. You can ask for all trackers at once or filter by group or tag.

Example prompts:

Which of my trackers are online right now?
Show me all moving vehicles and their current speed.

Look up a specific tracker or vehicle

You can refer to any tracker by name rather than by ID. Navixy User MCP uses fuzzy matching, so approximate names work. "Fiat" will find "Fiat Fiorino," and "Volvo" will find "Volvo Truck."

For a named tracker, your AI client can retrieve its current state (position, movement status, ignition) or its latest sensor readings (voltage, fuel level, temperature, odometer, engine hours).

Example prompts:

View track history

Your AI client can retrieve the movement history of any tracker for a specified time period. The response lists individual track segments with start point, end point, distance, and duration for each segment. A single day of driving typically returns multiple segments separated by stops.

Example prompts:

Organize by groups and tags

Your AI client can list all tracker groups and tags in your account, search for a specific group or tag by name, and filter the tracker list by group or tag. Filtering supports both "match all tags" and "match at least one tag" logic.

Example prompts:

Work with vehicles

Your AI client can retrieve the full vehicle list with metadata, including registration number, vehicle type, fuel type, and average fuel consumption. It can also find a specific vehicle by name using fuzzy matching.

Example prompts:

Work with IoT Logic flows

Your AI client can list all IoT Logic flows in your account, retrieve details and configuration of a specific flow, export a flow definition, list all endpoints across all flows, and show which devices are assigned to which flows.

This is particularly useful for auditing your IoT Logic setup or checking source mappings across a large number of devices.

Example prompts:

Visualize the tracker on the map

Your AI client can display an interactive live map of all your trackers, grouped by movement status (moving, parked, offline), with automatic updates every five seconds.

Example prompt:

Navixy Tracker Map rendered in Claude Desktop, showing moving, parked, and offline trackers across Europe. The map updates automatically every five seconds and groups trackers by movement status
Navixy tracker map

Tools reference

Trackers

Tool
What it does
Parameters
Example prompt

tracker_list

Retrieves all trackers with metadata. Optionally filters by group or tag.

groupId (optional, -1 or omitted means no filtering), tagIds (optional, empty means no filtering), atLeastOneTagIdMatch (optional, default false)

"List all my trackers."

tracker_states

Returns the current state of one or more trackers: position, speed, movement status, ignition, inputs, battery. Pass empty array for all trackers.

trackerIds (required, empty array means all)

"Which trackers are currently moving?"

tracker_state_by_label

Returns the current state of a single tracker found by fuzzy name match.

trackerLabelQuery (required)

"What is the current status of the Volvo Truck?"

tracker_readings

Returns the latest sensor readings for one or more trackers: inputs, counters, virtual sensors. Pass empty array for all trackers.

trackerIds (required, empty array means all)

"Show me fuel levels for all trackers."

tracker_readings_by_label

Returns the latest sensor readings for a single tracker found by fuzzy name match.

trackerLabelQuery (required)

"What is the odometer reading for the Fiat Fiorino?"

tracker_track_list

Returns the movement history of a tracker for a given time period.

tracker (required, tracker ID), from (required, yyyy-MM-ddTHH:mm:ss), to (required, yyyy-MM-ddTHH:mm:ss)

"Show me the Volvo Truck's tracks from yesterday."

Groups and tags

Tool
What it does
Parameters
Example prompt

tracker_group_list

Returns all tracker groups in the account.

None

"List all my tracker groups."

tracker_group_by_title

Finds a tracker group by fuzzy name match.

labelQuery (required)

"Find the group called Delivery."

tag_list

Returns all tags in the account.

None

"What tags do I have?"

tag_by_name

Finds a tag by fuzzy name match.

labelQuery (required)

"Find the tag called refrigerated."

Vehicles

Tool
What it does
Parameters
Example prompt

vehicle_list

Returns all vehicles with metadata including type, fuel type, registration number, and average consumption.

None

"List all vehicles and their registration numbers."

vehicle_by_label

Finds a vehicle by fuzzy name match.

labelQuery (required)

"What fuel type does the Honda Forza use?"

IoT Logic

Tool
What it does
Parameters
Example prompt

iot_logic_flow_list

Lists all IoT Logic flows with their status and device count.

None

"List all my IoT Logic flows."

iot_logic_flow_read

Returns the full configuration of a specific flow.

flow_id (required)

"Show me the configuration of the Demo flow."

iot_logic_flow_export

Exports a flow definition as a reusable template.

flow_id (required)

"Export the Demo flow."

iot_logic_endpoint_list

Lists all input and output endpoints across all flows.

None

"What endpoints do I have in IoT Logic?"

iot_logic_endpoint_read

Returns the detailed configuration of a specific endpoint.

endpoint_id (required)

"Show me the configuration of the Default Output Endpoint."

iot_logic_sources_mapping_list

Lists all device-to-flow assignments. Supports pagination.

limit (optional, default 10000), offset (optional, default 0)

"Which devices are assigned to the Demo flow?"

Geocoding

Tool
What it does
Parameters
Example prompt

search_address_by_location

Converts GPS coordinates to a human-readable address.

lat (required), lng (required)

"What is the address of the Fiat Fiorino's current location?"

Visualization

Tool
What it does
Parameters
Example prompt

show_tracker_map

Displays an interactive live map of all trackers grouped by movement status. Updates every five seconds.

groupId (optional), tagIds (optional)

"Show me my trackers on a map."

Utility

Tool
What it does
Parameters
Example prompt

get_current_datetime

Returns the current date and time in the user's account timezone. Supports multiple output formats.

dateTimeFormat (required: date, time, iso, datetime, or custom Luxon format)

"What time is it in my account timezone?"

get_current_datetime returns a formatted string in the user's account timezone, not the local system time. The format depends on the dateTimeFormat parameter: iso returns a full ISO 8601 timestamp, date returns the date only, time returns the time only.

Last updated

Was this helpful?