Integration

Cartes.io integration

Cartes.io hosts live, crowd-sourced maps. Browse and search public maps, create, update and delete your own maps, list, add, edit, flag as spam and delete markers with their category, position, elevation and custom metadata, record new positions for a moving marker, import markers from GPX or GeoJSON files or in bulk (bulk and file imports need an account approved by Cartes.io), search marker categories, and get a PNG image of a map. Not exposed: the anonymous per-resource edit tokens (maps and markers you create are tied to your account, so the API key is enough to edit them), claiming and un-claiming maps, sharing private maps with named users, public user profiles and updating your own profile; marker street addresses and map owner and contributor details are not returned. Apps using this API must credit Cartes.io visibly (and Icons8 when showing category icons) and must not index or publish unlisted or private maps. Creation routes are rate limited per minute (X-RateLimit headers, 429 with Retry-After). Authentication is a Cartes.io personal access token (account settings) sent as a Bearer token in the Authorization header.

Connect Cartes.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Cartes.io.Built from the 21 Cartes.io tools below, on the connection you add once.

What you can do with Cartes.io

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.

Map, 8 operations

create_mapCreate mapPOSTCreates a map owned by your account. privacy decides who sees it: public is listed for everyone, unlisted is visible to anyone with its link, private only to you.
create_map_from_fileCreate map from filePOSTCreates a map and its markers from a GPX file. Requires an account approved by Cartes.io for bulk marker creation.
delete_mapDelete mapDELETEDeletes a map owned by your account, for real.
get_mapGet mapGETReturns one map with its marker categories. A private map is returned only to its owner and invited users.
list_mapsList mapsGETLists public maps, newest first, 15 per page. Pass withMine true to list your own maps instead, or ids[] to fetch specific public or unlisted maps.
list_related_mapsList related mapsGETLists public maps related to a map.
search_mapsSearch mapsGETSearches public maps by text, 15 per page.
update_mapUpdate mapPUTUpdates a map owned by your account. Only the fields sent change.

Marker, 6 operations

create_markerCreate markerPOSTAdds a marker to a map, visible to everyone who can see that map. The map's users_can_create_markers setting decides who may add one. Pass category or category_name, plus lat and lng.
create_markers_bulkCreate markers bulkPOSTAdds many markers to a map in one call. Requires an account approved by Cartes.io for bulk marker creation.
create_markers_from_fileCreate markers from filePOSTAdds markers to a map from a GPX or GeoJSON file. Requires an account approved by Cartes.io for bulk marker creation.
delete_markerDelete markerDELETEDeletes a marker you created, for real.
list_markersList markersGETLists every marker on a map with its category, position and metadata. Expired markers are left out unless show_expired is true.
update_markerUpdate markerPUTChanges the description of a marker you created, or (with is_spam) lets the owner of the map flag or unflag a marker as spam.

Category, 3 operations

list_categoriesList categoriesGETLists every marker category on Cartes.io (a long list); prefer search_categories to find one by name.
list_related_categoriesList related categoriesGETLists categories often used together with a category.
search_categoriesSearch categoriesGETSearches marker categories by name.

Location, 2 operations

create_marker_locationCreate marker locationPOSTRecords a new position for a marker you created (for example to track something moving), which becomes its current position.
list_marker_locationsList marker locationsGETLists the recorded positions of a marker over time.

Map image, 1 operation

get_map_imageGet map imageGETReturns a rendered PNG image of the map, centered on the average of its markers. Images are cached for 6 hours.

User, 1 operation

get_current_userGet current userGETReturns the Cartes.io account the API key belongs to.

Use Cartes.io from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Cartes.io once
Add your Cartes.io 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.