Connect ChatGPT or Claude

Let an AI app answer questions about your tags, locations, and geofences

Overview

TagLogger runs an MCP server, the open standard AI apps use to reach outside services. Once connected, you can ask questions such as “Which tags have not reported this week?” or “When did the generator leave the yard?” and the app looks up the answer in your workspace.

Read-only: a connected app can read your data. It cannot rename, move, pause, or delete anything.
Your approval first: the app gets access only after you approve it on a TagLogger page, and only to the data you approve.
Who can connect: the workspace owner, with an active subscription. Team members can ask the owner to connect.

Connect an App

In your AI app, add a custom connector (some apps call it an MCP server or integration) with this address:

https://api.taglogger.com/mcp

The app opens a TagLogger page. Sign in if asked.
Review what the app is asking to see, then choose Allow.
Back in the app, ask a question about your tags.

The same address is shown in the dashboard under Settings, Connected apps.

What the App Can Read

You approve three kinds of access: Tags (names, labels, battery, last report), Locations (positions and location history), and Geofences (zones, the tags they watch, and entry and exit events). The app picks from these tools:

get_fleet_summaryTags

How many tags you have, how many reported in the last 24 hours and 7 days, which tags have gone quiet, battery counts, and paused tags.

list_tagsTags (positions need Locations)

Your tags with name, labels, battery status, and when each last reported. Search by name or filter by label.

get_tagTags (position needs Locations)

One tag in detail, including its most recent position with time, accuracy radius in meters, and a map link.

get_tag_historyLocations

Where one tag was during a time window, up to 31 days. Defaults to the last 7 days.

list_geofencesGeofences

Your geofences with center, radius in meters, the tags each one watches, and which alerts are on.

list_geofence_eventsGeofences

When tags entered or left a geofence, newest first. Defaults to the last 7 days, up to 90 days.

Each position has a time and an accuracy radius. Geofence event times are when TagLogger noticed the crossing, not the exact moment.

Disconnect an App

Open Settings, Connected apps in the dashboard and choose Disconnect next to the app. It loses access within a minute. If your subscription ends, connected apps stop receiving data.

For Developers

Any MCP client that supports OAuth 2.1 can connect. The server publishes its metadata, so most clients need only the address above:

Protected resource metadata: https://api.taglogger.com/.well-known/oauth-protected-resource/mcp
Authorization server metadata: https://api.taglogger.com/.well-known/oauth-authorization-server
Authorization code flow with PKCE (S256). Clients register with dynamic client registration or a client ID metadata document.
Scopes: read:tags, read:locations, read:geofences.
Access tokens last one hour. Refresh tokens last 90 days and change on every use.

Scripts can also call the MCP server with a Developer API key as the bearer token. The key’s scopes and tag restrictions apply. See API Keys.