Skip to main content
Glama

Related Servers

Alternatives to atlaspi-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying 10,000 years of historical social-complexity data from the Seshat Global History Databank through 9 tools, allowing counterfactual analysis and comparison of polities in natural language.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides complete world location data (countries, states, cities) as an MCP server for AI assistants, enabling search and retrieval of geographic information through 11 tools and 5 resources.
      290 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP-compatible AI assistants to Azgaar's Fantasy Map Generator so they can view, inspect, edit, and export fantasy maps in a live local browser, including borders, states, terrain, layers, and files. It runs locally and offline after installation, supports collaborative manual editing, undo, autosave, and text-only map output for models that cannot see images.
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.
      8
      13 npm
      7
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 32 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose. Tools covering similar domains (e.g., events) are split into search, detail, entity-specific, map-optimized, date-specific, and coverage metadata, each with unique functionality and inputs. No two tools serve the same role.

    Naming Consistency5/5

    All 32 tools follow a consistent verb_noun pattern in snake_case, such as get_route, search_events, list_feedback. Naming is predictable and descriptive, making it easy to infer a tool's function from its name without ambiguity.

    Tool Count4/5

    32 tools is slightly high but well justified by the comprehensive and multi-faceted domain (entities, events, cities, routes, chains, feedback). Each tool serves a specific need, and the set covers exploration, search, detail, comparison, and metadata operations without unnecessary redundancy.

    Completeness5/5

    The tool surface is remarkably complete for a historical atlas: CRUD-like operations for entities, events, cities, routes, and chains are present, along with specialized tools for timeline, comparison, fuzzy search, feedback, and dataset statistics. No obvious gaps for standard historical queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues