Integration

Miataru integration

Miataru is an open-source location sharing service: a phone running the Miataru app (or any device or workflow) reports its position under a device id, and anyone who knows that id can read it back. Report a position for a device, read the latest known location of one or more devices (also as a GeoJSON feature for maps), read a device's stored location history, see who looked a device up (its visitor history), and delete everything stored for a device. Locations expire after the retention time the reporter chose unless history is enabled. Device security management (setting a DeviceKey, the allowed-devices list, slogans and security status) is left to the Miataru app, and the WebSocket live feed is not covered. This connects to the public server at service.miataru.com and needs no account or credential: a device protected with a DeviceKey must have that key passed in the device_key parameter, as an ordinary value.

Connect Miataru How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Miataru.Built from the 6 Miataru tools below, on the connection you add once.

What you can do with Miataru

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Delete location, 1 operation

delete_locationDelete locationPOSTPermanently deletes everything the server stores for a device: its current location, its location history and its visitor history.

Get location, 1 operation

get_locationGet locationPOSTReturns the latest known position of one or more devices by device id. Each lookup is recorded in the target device's visitor history under requesting_device_id; an unknown, expired or forbidden device comes back as null.

Get location geo json, 1 operation

get_location_geojsonGet location geojsonGETReturns the latest known position of one device as a GeoJSON Feature, ready for a map; empty when no position is known. A device protected with a DeviceKey answers 401 here (use get_location instead). Not recorded in visitor history.

Get location history, 1 operation

get_location_historyGet location historyPOSTReturns up to amount stored positions of one device. A history exists only when the reporter enabled it; the lookup is recorded in the device's visitor history under requesting_device_id.

Get visitor history, 1 operation

get_visitor_historyGet visitor historyPOSTReturns who looked up a device's location: the requesting device id and time of each recent get_location or get_location_history call, up to amount entries.

Update location, 1 operation

update_locationUpdate locationPOSTReports the current position of a device under its device id; the device does not need to exist yet. The position is kept for location_data_retention_time minutes, or added to the device's history when enable_location_history is True.

Use Miataru from Claude Code, Cursor or Codex

Connect Miataru in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Miataru operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Miataru

Create your workspace
Sign up free. Nothing to install.
Connect Miataru once
Miataru needs no credential, so its tools work immediately.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.