Skip to main content
Glama
urbanis

street-generator-mcp

by urbanis

Related Servers

Alternatives to street-generator-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      OSM-backed multimodal navigation MCP server enabling geocoding, route planning, POI discovery, and urban layout analysis. It provides a structured city graph to LLM apps without proprietary map APIs.
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that lets Claude Desktop or Claude Code drive a 3DStreet scene running in your browser, enabling scene creation, editing, and geospatial features.
      43 npm
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to geocode and reverse geocode places, find nearby points of interest, search categories within an area, get turn-by-turn routing, suggest meeting points, and analyze neighborhoods, commutes, schools, EV charging, and parking through OpenStreetMap data services. It also serves place and map tile resources over stdio, SSE, or Streamable HTTP transports.
      12
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Autodesk Civil 3D through natural language, supporting tools for surfaces, alignments, profiles, corridors, pipe networks, COGO points, and AutoCAD geometry.
      9
      3
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Provides read-only query tools over OpenStreetMap data in PostGIS, enabling natural language queries for features, categories, and spatial analysis.
      7
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a unique purpose: build_share_url creates a sharing link, import_street_from_osm fetches real-world data, and render_street visualizes a config. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: build_share_url, import_street_from_osm, render_street.

    Tool Count4/5

    With only 3 tools, the set is slightly minimal but covers the core workflow of import, render, and share for street generation. The count is reasonable for a focused domain.

    Completeness3/5

    The tools cover import, render, and share, but lack any editing or querying capabilities for generated configurations. The user must rely on Claude to produce the StreetConfig, which may be a gap for manual adjustments.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues