Map Traveler MCP
Related Servers
Alternatives to Map Traveler MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for intelligent travel planning that integrates 16 tools, live APIs, and a gamification system to help users plan trips, track expenses, and discover events.14 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server offering travel planning tools such as destination search, weather lookup, attraction discovery, and budget estimation.-
- AlicenseNot gradedqualityBmaintenanceMCP server for Japanese public transit journey planning with interactive map UI, enabling station search, route planning, and departure lookups via natural language.MIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the Google Maps API.11,868 npm90,399MIT
- FlicenseNot gradedqualityBmaintenanceA general-purpose Google Maps MCP server that provides geocoding, place search, directions, distance matrices, and time zone lookup over the Model Context Protocol.-
- FlicenseNot gradedqualityCmaintenanceMCP server for generating interactive 3D Earth visualizations with annotated news from multiple global sources.-
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap between get_traveler_info and get_setting, and get_traveler_location and get_traveler_view_info share similar location-related functions. The descriptions help clarify differences, but an agent might occasionally misselect between these pairs.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as get_traveler_info and set_traveler_info. The only minor deviation is 'tips', which is a noun rather than a verb_noun pattern, but it fits the overall style and does not break consistency severely.
With 8 tools, the count is well-scoped for a travel or mapping server. Each tool appears to serve a specific function in managing traveler settings, location, and journey control, making the set neither too sparse nor overloaded.
The tool set covers core operations like getting/setting traveler info, location, and journey control, but there are notable gaps. For example, there is no tool for updating journey details mid-travel or handling multiple travelers, which could limit agent workflows in a travel domain.