developer portalaccounts.geodynamics.eu) the first time your client connects. Every tool call is then scoped to the company you picked, and tools never take a companyId parameter. Superadmin accounts are refused here, they belong on the Admin MCP.The Model Context Protocol server puts your own GeoDynamics data in front of an AI tool: people, clockings, timesheet totals, vehicles, and geofenced sites. Point a client at the transport URL below and the five tools appear in its tool list.
Every tool is annotated read-only. There are no write tools on this server: no clocking inserts, no timesheet approvals, no configuration changes. Reports as structured JSON are planned separately and will stay read-only as well.
One transport URL serves every client: https://mcp.geodynamics.dev/mcp. Clients that speak remote MCP take it directly. Clients that only spawn a local process reach it through the mcp-remote bridge.
Add a remote server entry that points at the hosted URL. Claude opens the GeoDynamics login in your browser the first time you connect.
{
"mcpServers": {
"geodynamics": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.geodynamics.dev/mcp"
]
}
}
}Create or edit .cursor/mcp.json in your project, or the global Cursor MCP config, with the same remote URL.
{
"mcpServers": {
"geodynamics": {
"url": "https://mcp.geodynamics.dev/mcp"
}
}
}Anything that can spawn a local stdio bridge reaches the same URL throughmcp-remote.
npx -y mcp-remote https://mcp.geodynamics.dev/mcp
Five tools, all reads. Company scope comes from the auth session, so no tool takes a company parameter. Ids that one tool returns are the ids the next one accepts.
People in your company. Start here: the id it returns is theuserId that getClockings andgetTimesheetSummary take.
| Name | Type | Required | Notes |
|---|---|---|---|
search | string | optional | Filter by name fragment. |
One row per user with id, name, code, and dayProgramId.
Clock-in and clock-out events over a date range. Raw events, so usegetTimesheetSummary when you need hours someone can sign off on.
| Name | Type | Required | Notes |
|---|---|---|---|
from | string | required | Start of the range, ISO 8601. 2025-03-01T00:00:00Z |
to | string | required | End of the range, ISO 8601. Max 31 days. |
userId | uuid | optional | One person, from listUsers. |
A total and the matching items, oldest first.
Worked hours for one person over a period, straight from the post-calculation engine. These totals are the authoritative ones. Summing raw clockings yourself gives a different, wrong answer.
| Name | Type | Required | Notes |
|---|---|---|---|
userId | uuid | required | From listUsers. |
from | string | required | Start date, YYYY-MM-DD. |
to | string | required | End date, YYYY-MM-DD. Max 31 days from the start. |
Period totals per day type, as the timesheet reports them.
Vehicles in your company that carry a tracking device.
| Name | Type | Required | Notes |
|---|---|---|---|
search | string | optional | Filter by name, such as truck or van 12. |
One row per vehicle with id, name, and code.
Geofenced locations: work sites, offices, and depots. These are the places clockings and vehicle movements are matched against.
| Name | Type | Required | Notes |
|---|---|---|---|
search | string | optional | Filter by name. |
One row per location with its name and identifiers.
Once the client is connected, ask it things like:
Agents that would rather not read this page can fetch the MCP Server Card athttps://build.geodynamics.eu/.well-known/mcp/server-card.json. It names the transport, the OAuth endpoints, and the same five tools.