Skip to main content
Glama
urbanis

street-generator-mcp

by urbanis
OverviewSchemaSourceRelated ServersScoreDiscussions
TypeScript
Remote

street-generator-mcp

An MCP server that lets Claude design and render urban street cross-sections from natural language, in the visual style of the Street Generator app, figures and all. It can also read a real street from an address via OpenStreetMap.

Example street cross-section

The idea

Claude does the open-ended reasoning (designing the street). The server does the deterministic work (drawing it).

The server holds no LLM, no API keys, and no secrets. It keeps the model's output small (a compact StreetConfig instead of thousands of tokens of hand-drawn SVG) and moves the heavy, exact rendering into code. The result is faster, cheaper, and reliable: every street is drawn by the same renderer, identical every time.

User: "a calm residential street, wide sidewalks, trees, protected bike lanes"
   |
   v
Claude -> StreetConfig (JSON), guided by the tool schema
   |
   |-- render_street(config, style)   -> server draws an illustrated SVG
   |-- build_share_url(config)        -> streetgenerator.com/?s=...
   |
   v
Claude shows the image and the link

Related MCP server: minecraft-schematic-lab

Tools

render_street(config, style?)

Renders a StreetConfig to an illustrated SVG cross-section (buildings as floor stacks, sidewalks with pedestrians, planting strips with trees, lanes with cars).

style (optional): colorMode "outline" (default) or "color", plus showLabels, showMeasurements, showFigures (all default true).

import_street_from_osm(street, houseNumber, city, postcode, country, style?)

Reads a real street from OpenStreetMap and renders it. Give a full address (street, house number, city, postcode, country). If any part is missing or unclear, Claude asks first. When several places match, the tool returns lettered candidates (A, B, C) so you can pick one, then it renders the chosen street.

Under the hood: geocode the address (Nominatim), read the nearest street's tags (Overpass), interpret and map them to a StreetConfig, then render. This tool needs internet access; the other two do not.

build_share_url(config)

Returns a streetgenerator.com link that opens the design in the live app, where you can keep editing and export it.

What you get back

Every render returns the cross-section as SVG (which you can save) together with a streetgenerator.com link that opens the same design in the app, where the app's own PNG, SVG, and JSON exports are available. Native PNG output from the server is on the roadmap (see Future work).

Examples

From simple to more complex. You type these to Claude; it calls the tools and shows the result.

Prompt

What you get

"Render a two-lane street with sidewalks on both sides."

A simple SVG cross-section (two traffic lanes, two sidewalks) and a share link.

"Design a calm residential street with wide sidewalks, street trees, and a protected bike lane on each side."

A fuller illustrated SVG with pedestrians, trees, and buffered cycle lanes, plus a share link.

"Draw a boulevard with a central median, bus lanes, and buildings, in colour."

A wide coloured cross-section with a median, bus lanes, and building floor stacks.

"Design a one-way street with parking, and hide the width numbers."

An SVG with labels but no measurements (a style option), plus a share link.

"Show me the street at Unter den Linden 77, 10117 Berlin, Germany."

The real street read from OpenStreetMap and rendered, plus a share link.

"Load the street at Hauptstrasse 1, Germany." (ambiguous address)

A lettered list of candidate places (A, B, C) to choose from; pick one and it renders.

Usage and external services

import_street_from_osm queries two free OpenStreetMap services: Nominatim (geocoding) and Overpass (map data). It is meant for occasional, interactive lookups, not bulk downloading. Please stay within their public usage policies:

  • Nominatim: at most 1 request per second, an identifying User-Agent (already set by this server), results cached where possible, and no automated or bulk querying. See the Nominatim usage policy.

  • Overpass: fair use only, roughly up to 10,000 requests and 1 GB of data per day per IP, with rate limiting under load and a 180 second per-request timeout. See the Overpass usage guidance.

For heavy or automated use, run your own Nominatim or Overpass instance instead of the public servers. Map data is copyright OpenStreetMap contributors, available under the ODbL; displayed results should attribute OpenStreetMap accordingly.

Install (Claude Desktop)

{
  "mcpServers": {
    "street-generator": {
      "command": "node",
      "args": ["/absolute/path/to/street-generator-mcp/dist/index.js"]
    }
  }
}

Then ask Claude to design or import a street and it calls the tools automatically.

Develop

npm install
npm test          # unit, mocked-network, and fidelity tests
npm run build     # compile to dist/ and copy figure assets
npm run dev       # run the server from source

How the rendering stays faithful to the app

The layout math, element data, figure art, and the OSM interpreter/mapper are ported value-for-value from the Street Generator app (the interpreter and mapper come with their original unit tests). Fidelity is checked with structural tests in test/.

Future work

  • PNG output from the server (SVG to raster).

  • validate_street against Berlin RASt rules (the engine already exists in the app).

  • Nearest-way selection for OSM import (v1 takes the first street within a radius of the geocoded point).

  • Figures for cycle and bus lanes once art exists.

Available Tools

3 tools
build_share_urlBuild share linkA

Return a streetgenerator.com link that opens this StreetConfig in the live Street Generator app.

ParametersJSON Schema
NameRequiredDescriptionDefault
configYes

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It only states the output is a link, but does not disclose any side effects, authorization needs, or other behavioral traits beyond what is minimally inferred.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no extraneous information. Every word serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately states the tool's function but does not specify the exact format of the return link, mention validation, or address potential limitations. Given the complexity of the input (nested object) and lack of output schema, more detail would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema defines the 'config' parameter with nested structure, but schema description coverage is 0% (no descriptions in schema for top-level config). The description adds no additional meaning about the parameter beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the verb 'return' and the resource 'streetgenerator.com link', and specifies that it opens the StreetConfig in the live app. This clearly differentiates it from sibling tools like import_street_from_osm and render_street.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for generating share links, but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

import_street_from_osmImport a real street from an addressA

Render a real street cross-section by reading its layout from OpenStreetMap. Requires a COMPLETE address: street, house number, city, postcode, and country. If the user hasn't provided all of these, or the address is unclear, ASK them for the missing parts before calling. If several places match, the tool returns lettered candidates (A, B, C…); show them to the user, then call again with the chosen candidate's lat and lng.

ParametersJSON Schema
NameRequiredDescriptionDefault
latNoLatitude — provide ONLY when re-rendering a disambiguation candidate the user picked; skips geocoding
lngNoLongitude — provide together with lat
cityYesCity (required)
styleNo
streetYesStreet name (required)
countryYesCountry name or code (required)
postcodeYesPostal / ZIP code (required)
houseNumberYesHouse number (required)

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full burden. It discloses the two-step flow, disambiguation with lettered candidates, and that lat/lng skips geocoding. However, it does not mention error handling (e.g., address not found) or the output format, which would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the purpose, then requirements, then the disambiguation process. Every sentence adds critical information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite covering the input and flow well, the description does not specify the output of the tool (e.g., image, data model). Since there is no output schema, this omission reduces completeness. The style parameter defaults are in the schema but not summarized.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (88%), so baseline is 3. The description adds value by explaining the special role of lat/lng in the disambiguation flow and emphasizing completeness of address parameters. Style parameters are not mentioned but are covered in schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool renders a real street cross-section by reading from OpenStreetMap, specifying the required complete address. It effectively distinguishes from sibling tools by detailing the unique two-step process involving address input and optional lat/lng for disambiguation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool (complete address required) and when to ask the user for missing parts or present candidates. It explains the disambiguation flow but does not compare this tool to its siblings (build_share_url, render_street), reducing its helpfulness for alternative selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

render_streetRender street cross-sectionA

Render a StreetConfig as an illustrated SVG cross-section (people, cars, trees included). Claude produces the StreetConfig from the user's description; this tool draws it deterministically in the Street Generator visual style.

ParametersJSON Schema
NameRequiredDescriptionDefault
styleNo
configYes

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It states the tool renders deterministically, suggesting a read-only, pure output operation. However, it lacks explicit statements about side effects, idempotency, or resource usage, which would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with purpose, and contains no wasted words. It efficiently conveys the tool's role and context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (nested parameters, no output schema, no annotations), the description is too brief. It omits return value format (e.g., SVG URL or data), prerequisites, and details about the 'Street Generator visual style', leaving the agent with insufficient guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not explain any parameters or their meanings beyond what the schema structure provides. The complex nested schema (e.g., config, style) is left for the agent to interpret without added guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it renders a StreetConfig as an illustrated SVG cross-section, specifying included elements (people, cars, trees). It also distinguishes from sibling tools (build_share_url and import_street_from_osm) by noting this tool draws the config deterministically in a visual style.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context by stating that Claude produces the StreetConfig and this tool draws it, implying use after obtaining a config. However, it does not explicitly state when not to use this tool or mention alternatives to siblings, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv0.1.0
    • First observedbuild_share_url
    • First observedimport_street_from_osm
    • First observedrender_street
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
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

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • OSM-GeoJSON-MCP-Server

    shimizu
    F
    license
    A
    quality
    C
    maintenance
    Enables querying OpenStreetMap data (buildings, roads, amenities, etc.) via Overpass API and converts them to GeoJSON format for GIS analysis and visualization.
    8
    6
    -

  • Civil 3D MCP Server

    DaniGhosy
    A
    license
    A
    quality
    B
    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
    2
    MIT

  • osm-mcp

    a-tsitanov
    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
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/urbanis/street-generator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server