Streetmap Port

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs.

The publisher's own server: Port

Overview

AI-generated overview

Local stdio MCP server that gives an assistant OpenStreetMap geocoding, place search, nearby lookup and distance tools.

What you can do
  • Convert addresses or place names into coordinates, and coordinates back into the nearest address
  • Search places by name and fetch details of a single OSM node, way or relation
  • Find places of a given category near a coordinate pair
  • Compute great-circle distance in kilometres between two coordinate pairs, locally without any API call
When to use it
Useful when an assistant needs to resolve addresses to coordinates, look up OpenStreetMap places, explore what is near a location, or measure distances between points, without building its own geocoding integration.
Requirements
Runs as a local process via npx (Node.js) or Docker. No account, API key or environment variable is declared. Network access to the public Nominatim and Overpass APIs is needed for all tools except the local distance calculation.
Before you install
Queries are sent to the public OpenStreetMap Nominatim and Overpass services, so searched addresses and coordinates leave the machine. Those public APIs have usage policies and rate limits; heavy or automated use may be throttled or blocked. Results depend on OpenStreetMap data (ODbL) and may be incomplete or inaccurate.

Installation

In SourceWeft

  1. Open Streetmap Port in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

streetmap-port

OpenStreetMap geography as a CLI and a stdio MCP server in one bin: geocode a name to coordinates, reverse geocode coordinates to an address, search places, look up an OSM object by type and id, find places of a category near a point, and compute great-circle distances locally.

Geocoding, reverse geocoding and lookup use the public Nominatim API (with the descriptive User-Agent its usage policy requires); nearby search uses the public Overpass API. All requests go through an injectable fetch function, coordinates are validated before any request is built, and API error payloads are surfaced as errors — never replaced with invented places. distance_between is a pure local haversine computation and makes no API call.

Install

bash
npx -y @reneturcios/streetmap-port mcp

CLI

bash
streetmap-port mcpstreetmap-port geocode <query...>streetmap-port reverse <lat> <lon>streetmap-port search <query...>streetmap-port nearby <lat> <lon> [category] [radius-m]streetmap-port distance <lat1> <lon1> <lat2> <lon2>streetmap-port --version

Exit codes: 0 success, 1 API/validation error, 2 usage error.

MCP tools

ToolPurpose
geocode_addressGeocode a free-form address or place name to coordinates via the OSM Nominatim API
reverse_geocodeReverse geocode coordinates to the nearest address via the OSM Nominatim API
search_placesSearch for places by name via the OSM Nominatim API
find_nearbyFind places of a category near coordinates via the OSM Overpass API
get_place_detailsGet details of one OSM object (node, way or relation) via the Nominatim lookup API
distance_betweenCompute the great-circle distance in kilometres between two coordinate pairs (local, no API call)

MCP client config:

json
{  "mcpServers": {    "streetmap-port": {      "command": "npx",      "args": ["-y", "@reneturcios/streetmap-port", "mcp"]    }  }}

Docker

bash
docker run -i ghcr.io/cloudcorprecords/streetmap-port          # MCP serverdocker run --rm ghcr.io/cloudcorprecords/streetmap-port --version

Development

bash
npm installnpm run buildnpm test

Data © OpenStreetMap contributors (ODbL). MIT license for the code.

Source: README.md at commit 008e6f6

Tools

6

geocode_address

Geocode a free-form address or place name to coordinates via the OSM Nominatim API

Parameterslimitqueryrequired

reverse_geocode

Reverse geocode coordinates to the nearest address via the OSM Nominatim API

Parameterslatituderequiredlongituderequired

search_places

Search for places by name via the OSM Nominatim API

Parameterslimitqueryrequired

find_nearby

Find places of a category near coordinates via the OSM Overpass API

Parameterslimitradiuscategorylatituderequiredlongituderequired

get_place_details

Get details of one OSM object (node, way or relation) via the Nominatim lookup API

Parametersosm_idrequiredosm_typerequired

distance_between

Compute the great-circle distance in kilometres between two coordinate pairs (local, no API call)

Parametersto_latituderequiredto_longituderequiredfrom_latituderequiredfrom_longituderequired

Version history

1
  1. v0.1.0LatestOct 31, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Port integrations