Dawarich MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAWARICH_URL | Yes | Base URL of the Dawarich instance. | |
| DAWARICH_API_KEY | Yes | API key for authenticating with the Dawarich instance. | |
| DAWARICH_AUTH_MODE | No | Authentication mode: 'query' (default, sends ?api_key=...) or 'bearer'. | query |
| DAWARICH_GEOCODER_URL | No | URL of a compatible reverse geocoder endpoint. | |
| DAWARICH_GEOCODER_USER_AGENT | No | User agent for the reverse geocoder (default is OpenStreetMap Nominatim). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dawarich_get_statsA | Returns aggregated Dawarich statistics such as total distance, tracked points, countries, cities, and yearly breakdowns. |
| dawarich_get_timelineA | Returns day-by-day timeline data with visits, tracks, and photos. Dawarich supports a maximum date range of 31 days. |
| dawarich_list_visitsA | Lists visits from Dawarich. Optional filters are passed through as query parameters when provided. |
| dawarich_list_pointsA | Lists raw tracked location points for a date range. Use this for today's activity when timeline or visits are empty. |
| dawarich_get_track_pointsA | Returns location points for a specific Dawarich track, ordered by timestamp ascending. |
| dawarich_get_track_detailA | Returns a compact detail for one Dawarich journey: start/end points, endpoint labels, bounding box, duration, and optional sampled points. |
| dawarich_export_trackA | Downloads one Dawarich journey and returns it as compact JSON, GeoJSON LineString, or CSV. |
| dawarich_reverse_geocodeA | Converts GPS coordinates to an address using the configured reverse geocoder. Defaults to OpenStreetMap Nominatim unless DAWARICH_GEOCODER_URL is set. |
| dawarich_summarize_journeysA | Returns a simple human-readable trip table for a date range, including weekday, from-to places, time, distance, mode, and track ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct data type or operation: stats aggregates, timeline summarizes days, visits identifies places, track points and list points differ by scope, track detail is a compact overview, export transforms, reverse geocode converts coordinates, and summarize_journeys creates a trip table. Even the two point-related tools are clearly separated by whether they target a specific track or a date range.
All tools follow the consistent pattern dawarich_<verb>_<noun>. Verbs are either get, list, export, reverse, or summarize, making the action easy to predict. No camelCase or mixed conventions are present.
With 9 tools, the server is well-scoped for a location history integration. Each tool covers a meaningful query or export need without unnecessary redundancy or bloat.
The server covers the main read-side workflows: overview stats, timelines, visits, raw points, track details, export in multiple formats, geocoding, and journey summaries. A minor gap is the lack of a direct photo retrieval tool despite timeline mentioning photos, and no write operations, but that appears outside the intended read-only scope.