create_waypointLABSCO SUMMARY
Track statistics without exporting anything.
get_statistics is the reason to connect this rather than open the web app: distance, speed, altitude and a country breakdown come back aggregated, so questions about a trip are answered in one call instead of a download and a spreadsheet.
What it is
The MCP bridge and client configuration for Geomanic, a GPS tracking platform. Seven tools cover creating, editing and listing waypoints, plus aggregated statistics over them.
What you get
- create_waypoint, update_waypoint and delete_waypoint by ID
- get_waypoint — one waypoint by ID
- list_waypoints — with a time range, pagination and sorting
- get_statistics — distance, speed, altitude and a country breakdown
- get_date_range — the earliest and latest waypoint dates on the account
- A skill file for Claude Desktop and OpenClaw, a Node bridge for Cursor, and a direct remote URL for clients that support one
Requirements
A Geomanic MCP API key, generated on the Geomanic data page. Clients that support remote MCP servers point at https://geomanic.com/api/v1/mcp with the key as a bearer token; the bridge is a plain Node script needing Node 18+ and no dependencies.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Summarising a trip you already recorded
Get aggregated distance, speed and altitude, with the breakdown by country.
02
Pulling the track for a specific window
List waypoints across a time range, sorted and paginated, rather than fetching everything.
03
Finding out what data exists at all
Read the earliest and latest waypoint dates before choosing a range to query.
04
Fixing a point that landed wrong
Fetch the waypoint by ID, correct it, or remove it.
7 tools
Listed in project docs. Your client may show a different list.
update_waypointdelete_waypointget_waypointlist_waypointsget_statisticsget_date_rangeBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
GEOMANIC_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
Setup
Generate an MCP API key on https://geomanic.com/data (MCP Integration tile)
Cursor (Bridge): Copy bridge/config/cursor/mcp.json into your Cursor MCP settings.
<YOUR_API_KEY> is your MCP API key.
Save and restart Cursor.
Hosted endpoint
ENDPOINT URL
https://geomanic.com/api/v1/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
OpenClaw — skill
OPENCLAW — SKILL · IN CLIENT
/skills install @weltspion/geomanic
/secrets set GEOMANIC_TOKEN <YOUR_MCP_KEY>Claude Desktop — skill
Download this repository (Code → Download ZIP) and extract it.
Open skills/claude/SKILL.md in a text editor and write your API key wherever the file says <YOUR_API_KEY>.
In Claude Desktop: Settings → Skills → Add → Upload Skill and select the edited SKILL.md.
Cursor — bridge
Copy bridge/config/cursor/mcp.json into your Cursor MCP settings (<YOUR_API_KEY> is your MCP API key), then save and restart Cursor.
CURSOR — BRIDGE · JSON
{
"mcpServers": {
"geomanic": {
"url": "https://geomanic.com/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Any MCP client — remote
URL: https://geomanic.com/api/v1/mcp
Header: Authorization: Bearer YOUR_MCP_KEY
