Skip to main content
Glama
chris-page-gov

mcp-geo

by chris-page-gov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mcp-geo

No user-submitted related servers found.

    Related Servers

    • ontario-data-mcp

      sprine
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for discovering, downloading, querying, and analyzing datasets from Ontario's open data portals, allowing natural language questions and high-performance analytics via DuckDB.
      23
      1
      MIT

    • OpenStreetMap MCP Server

      GRABOSM
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.
      30
      251 npm
      5
      MIT

    • UK Parliament MCP Server

      ChrisBrooksbank
      A
      license
      B
      quality
      A
      maintenance
      An MCP server that gives AI assistants access to UK Parliament data. Query MPs, Lords, bills, votes, committees, debates, and more through AI assistants like Claude Desktop and VS Code Copilot.
      210
      5
      MIT

    • Open Emirates Intelligence

      ahmedvnabil
      A
      license
      Not graded
      quality
      B
      maintenance
      A comprehensive MCP server that makes official UAE open data queryable through natural language, offering tools for source discovery, dataset search, spatial joins, and intelligence recipes.
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 103 tools

    Disambiguation2/5

    While the provider prefixes (os_, ons_, landis_) help, there is considerable overlap between tools like os_places_search vs os_poi_search vs os_names_find, and os_map_export vs os_map_export_roads. The distinction between os_features_query and os_map_inventory is also unclear, making it easy for an agent to select the wrong tool.

    Naming Consistency3/5

    Most tools follow a {provider}_{resource}_{action} pattern, and each data source has a reasonably consistent style (e.g., os_places_*, os_poi_*, os_downloads_*). However, there are notable exceptions like os_linked_ids_* and os_mcp_* that mix nouns and verbs, and some tools like os_net_station_log use a noun instead of an action, creating uneven conventions.

    Tool Count1/5

    With 103 tools, this is far beyond the 50+ threshold for an extreme mismatch. Even though the server covers many geo data sources, the sheer number makes it unwieldy and hard for an agent to navigate efficiently. The tool count is the primary driver of low coherence.

    Completeness4/5

    The server provides broad read-only coverage across administrative boundaries, soil data, census/statistics, OS maps, places, points of interest, routes, and tile services. Minor gaps exist (e.g., no cache refresh or write operations), but for a data-lookup-centric geo server, the coverage is strong and well-suited to its purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources