Geomanic MCP Server

MCP bridge, skills, and configuration templates for Geomanic — your GPS tracking platform. The geomanic mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• create_waypoint — Create a new GPS waypoint
• update_waypoint — Update an existing waypoint by ID
• delete_waypoint — Delete a waypoint by ID
• get_waypoint — Get a single waypoint by ID
• list_waypoints — List waypoints with time range, pagination, sorting
• get_statistics — Aggregated stats: distance, speed, altitude, country breakdown
• get_date_range — Earliest and latest waypoint dates

Configuration

You will need 3 environment variables: GEOMANIC_TOKEN, YOUR_MCP_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the geomanic mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Geomanic MCP's toolset — create_waypoint, update_waypoint, delete_waypoint and 4 more — is a fair guide to whether it matches your workflow. It is maintained by monswyk; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.