Dawarich MCP
Related Servers
Alternatives to Dawarich MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to query exported on-device location history data, with tools for finding where you were at a time, summarizing visits and trips, searching visited places, and enriching coordinates with addresses and place names.13 npmMIT
- FlicenseAqualityDmaintenanceExposes Foursquare/Swarm check-in data and user activity through 13 tools, enabling user management, check-in history, venue details, mayorships, lists, and cross-user search.13-
- AlicenseAqualityCmaintenanceEnables querying an OwnTracks Recorder for current and historical location data, including addresses, stays, distances, devices, and status, through read-only MCP tools. It supports natural-language questions about where someone is or was and how far they are from home.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables geographic utilities from public APIs: geocoding addresses and places, reverse geocoding coordinates, retrieving country details, timezone data, and sunrise/sunset times through natural language requests.282 npm1MIT
- AlicenseAqualityBmaintenanceProvides location-based services and geospatial data from OpenStreetMap, enabling geocoding, route directions, nearby place search, and neighborhood analysis through natural language.12MIT
- FlicenseNot gradedqualityDmaintenanceEnables exploration of geographical data including countries, cities, states/provinces, and regions through a SQLite database. Supports searches by name, location coordinates, currency, and regional groupings with comprehensive statistical queries.7-
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.