Dawarich MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | default 127.0.0.1 | 127.0.0.1 |
| MCP_PORT | No | default 8000 | 8000 |
| MCP_TRANSPORT | No | stdio or http, default stdio outside the container | stdio |
| DAWARICH_API_KEY | Yes | Dawarich user API key | |
| DAWARICH_BASE_URL | Yes | Dawarich base URL, for example http://dawarich.dawarich.svc.cluster.local:3000 | |
| DAWARICH_AUTH_MODE | No | bearer or query, default bearer | bearer |
| DAWARICH_HOST_HEADER | No | optional HTTP Host header for deployments that call an internal service URL while Dawarich only allows the public app host | |
| DAWARICH_MAX_PAGE_SIZE | No | default 500 | 500 |
| DAWARICH_FORWARDED_PROTO | No | optional X-Forwarded-Proto header, for example https when Dawarich forces HTTPS behind a proxy | |
| DAWARICH_TIMEOUT_SECONDS | No | default 30 | 30 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dawarich_get_statsB | Get aggregate Dawarich travel stats, optionally filtered to one year. |
| dawarich_search_placesC | Search saved and nearby Dawarich places. |
| dawarich_find_visitsA | Find Dawarich visits by time and status. |
| dawarich_get_timelineC | Get day-by-day Dawarich timeline context for a date range. |
| dawarich_get_map_contextA | Get map bounds and optional capped hexagon/fog context. |
| dawarich_find_pointsA | Find raw Dawarich points. Prefer timeline/map context unless point evidence is needed. |
| dawarich_create_placeC | Create a manual Dawarich place. |
| dawarich_update_placeB | Update a Dawarich place after reading its current value. |
| dawarich_delete_placeB | Delete a Dawarich place. Defaults to dry-run. |
| dawarich_create_visitC | Create a Dawarich visit and matching/manual place if needed. |
| dawarich_update_visitC | Update a Dawarich visit after reading its current value. |
| dawarich_select_visit_placeC | Select one of Dawarich's possible places for a visit. |
| dawarich_merge_visitsC | Merge Dawarich visits. Defaults to dry-run because merge is destructive. |
| dawarich_bulk_update_visit_statusA | Bulk update Dawarich visit status. Defaults to dry-run. |
| dawarich_create_tripB | Create a Dawarich trip when /api/v1/trips exists; currently reports that API gap. |
| dawarich_update_tripC | Update a Dawarich trip when /api/v1/trips exists; currently reports that API gap. |
| dawarich_delete_tripC | Delete a Dawarich trip when /api/v1/trips exists; currently reports that API gap. |
| dawarich_add_pointsA | Add raw Dawarich points. Prefer visit/timeline tools unless raw samples are needed. |
| dawarich_recalculateC | Queue supported Dawarich recalculations. Defaults to dry-run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_suggested_visits | |
| create_trip_from_dates | |
| monthly_travel_summary |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stats_summary | |
| profile |
TDQS
Scored across 19 tools
Most tools are clearly distinct: places, visits, points, timeline, stats, and recalculate all have separate purposes. However, the three trip tools (create/update/delete) are functionally identical stubs that all report an API gap, making them hard to distinguish by action despite different names.
All tools follow a consistent dawarich_<verb>_<noun> pattern in snake_case, with verbs like search, find, create, update, delete, add, merge, and bulk_update. This is highly predictable and readable.
At 19 tools, the server is slightly over the ideal 3-15 range but still reasonable for a domain covering places, visits, points, trips, stats, timeline, and map context. The three non-functional trip tools could be trimmed, but the count is not excessive.
Core place/visit/point operations are well represented, plus useful extras like timeline, stats, and map context. However, trip tools are non-functional stubs that only report an API gap, creating dead ends for trip workflows, and there is no delete_visit tool. These are notable gaps.