Integration

Mapulus integration

Mapulus is a mapping platform for plotting and analysing locations. Through its Studio API, list the maps of an account and their layers, list locations with filters by map, layer or external id, find up to 24 nearest locations to a point or address by distance or travel time, and create, update or delete location pins with addresses, coordinates, travel-time contours and custom attributes. The separate Data API (Australian boundaries, census demographics, enrichment) is not exposed. Authentication is a Mapulus API key, managed under Profile > API Keys, sent as a Bearer token in the Authorization header.

Connect Mapulus How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Mapulus

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.

Location, 5 operations

create_locationCreate locationPOSTCreate a location pin on a layer. Needs layer_id (from list_maps with expand[]=layer) and either an address or lat and lon. New custom attribute names need create_or_update_custom_attributes=true.
delete_locationDelete locationDELETEPermanently delete a location pin. Returns its id and deleted=true.
get_locationGet locationGETGet one location by id: coordinates, address, title, external id, geocoding status, travel-contour settings, map and layer ids, and custom attributes.
list_locationsList locationsGETList the account's locations, paginated, filtered by map, layer or external id. With nearest[lat]/nearest[lon] or nearest[address], returns up to 24 closest locations by distance or travel time.
update_locationUpdate locationPUTUpdate a location. layer_id is required (a new one moves the location) and the location must still have an address or lat and lon. New custom attribute names need create_or_update_custom_attributes=true.

Map, 2 operations

get_mapGet mapGETGet one map by id (title and timestamps). Set expand[] to layer to include its layers.
list_mapsList mapsGETList the maps of the account (id, title, timestamps), paginated with pages metadata. Set expand[] to layer to include each map's layers, whose ids create_location needs.

Use Mapulus from Claude Code, Cursor or Codex

Connect Mapulus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Mapulus 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 Mapulus

Create your workspace
Sign up free. Nothing to install.
Connect Mapulus once
Add your Mapulus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.