MCP server
Ask questions about your tracked assets in plain language. Blecon Track exposes a Model Context Protocol (MCP) server that gives AI assistants (including Claude Code and Claude Desktop) direct access to your tracking data.
Once connected, you can ask things like "which assets are currently in the loading bay?" or "show me the position history for forklift #3 over the last 24 hours" and get live answers, without writing API calls or navigating the dashboard. You can also make changes in plain language — create a geofence, add an alert rule, acknowledge an alert, or set up a notification channel — with edits subject to your workspace role (a viewer can read everything but can't modify).
Endpoint
https://api.blecon.net/tracker/mcp/
Connecting Claude Code
-
Add the MCP server to your Claude Code settings (
~/.claude/settings.json):{ "mcpServers": { "blecon-tracker": { "type": "http", "url": "https://api.blecon.net/tracker/mcp/" } } } -
Start a new Claude Code session: Claude Code will open a browser window to sign in to your Blecon account. Once authenticated, the tracker tools are available automatically.
No API key is required. The MCP server uses OAuth and your existing Blecon account credentials.
What you can do
The server gives assistants nine tools, one per area of Track. Each tool both reads data and, where you have permission, makes changes — the assistant picks the right operation for your request. Together they cover most of what the API can do.
| Tool | What it covers |
|---|---|
workspaces |
Discover the workspaces you can access and their details |
assets |
List, search and inspect assets; register, rename, archive/unarchive, delete, and associate them (e.g. attach a tag to a container) |
asset_history |
Position trails, movement summaries, sensor (temperature / humidity / battery) history, and association/trip history |
zones |
List and inspect zones and who's inside them; create, edit and delete geofences; view live occupancy, historical occupancy, and entry/exit events |
network_zones |
List, create and delete network (indoor) zones |
alert_rules |
List and inspect alert rules; create, edit, enable/disable and delete them |
alerts |
List alerts and stats/history; acknowledge, resolve and add notes |
analytics |
Fleet summary, position volumes, historical stats, missing-asset reports, and movement trail / heatmap data |
notification_channels |
Manage where alerts are delivered — webhook and email channels (create, edit, delete, and send a test) |
Changes are always subject to your workspace role: reads need Viewer access, most edits need Member, and a few (deleting an asset, managing network zones) need Admin. If a tool doesn't appear at all, MCP access may not be enabled for your account yet — contact Blecon to turn it on.
Example prompts
Which assets are currently in the "Warehouse Floor" zone?
Show me the position history for asset urn:uuid:abc123 over the last 48 hours.
Create a bounding-box geofence around the depot and add an alert rule that
fires when any tag leaves it.
How many alerts are active right now? Acknowledge the low-battery ones and
add a note that maintenance has been scheduled.
Add an email notification channel for ops@example.com and send a test.
Which assets haven't been seen in the last week?