CHGIS MCP Server
Related Servers
Alternatives to CHGIS MCP Server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceProvides structured access to a temporal knowledge platform for searching historical events and browsing a causal graph of over 2,000 years of history. It enables users to generate rich historical scenes, interact with period-appropriate characters, and run complex temporal simulations.-- 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.6-
- FlicenseNot gradedqualityDmaintenanceProvides comprehensive geographic information services and route planning for AI agents via the Amap (Gaode Maps) API. It supports geocoding, multi-modal navigation, POI searches, and administrative region queries.3-
- AlicenseAqualityCmaintenanceEnables location-based services through AMap/AutoNavi Maps API including geocoding, weather information, route planning, and POI searches. Supports multiple transportation modes and provides detailed geographic data for Chinese locations.123Mulan Permissive Software , Version 2
- FlicenseNot gradedqualityDmaintenanceProvides a suite of tools for location retrieval and multi-modal route planning within China using the Baidu Maps API. It enables AI agents to perform address-to-coordinate conversions, nearby place searches, and calculate directions for driving, transit, walking, and cycling.-
- FlicenseNot gradedqualityCmaintenanceEnables natural-language Chinese queries across MySQL, Dameng DM, and KingbaseES databases, with safe SQL generation, schema exploration, and read-only query execution.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_place_historical_context retrieves context and relationships, search_place_by_id queries by ID, and search_places searches by multiple criteria. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with snake_case: get_place_historical_context, search_place_by_id, and search_places. The naming is predictable and uniform throughout the set.
With only 3 tools, the server feels thin for a historical geographic information system domain. While the tools cover core querying functions, the scope suggests potential gaps in operations like data creation, updates, or more specialized analyses.
The toolset is severely incomplete for a CHGIS server, lacking any CRUD operations beyond querying. There are no tools for creating, updating, or deleting place data, and no lifecycle coverage, which will likely cause agent failures in broader workflows.