io.github.CloudCorpRecords/streetmap-port
Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@reneturcios/streetmap-portclaude mcp add streetmap-port -- npx -y @reneturcios/streetmap-port@0.1.0 mcp
{
"mcpServers": {
"streetmap-port": {
"command": "npx",
"args": [
"-y",
"@reneturcios/streetmap-port@0.1.0",
"mcp"
]
}
}
}
ghcr.io/cloudcorprecords/streetmap-port:0.1.0claude mcp add streetmap-port -- docker run -i --rm ghcr.io/cloudcorprecords/streetmap-port:0.1.0 mcp
{
"mcpServers": {
"streetmap-port": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cloudcorprecords/streetmap-port:0.1.0",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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
npx -y @reneturcios/streetmap-port mcp
CLI
streetmap-port mcp
streetmap-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
| Tool | Purpose |
|---|---|
geocode_address | Geocode a free-form address or place name to coordinates via the OSM Nominatim API |
reverse_geocode | Reverse geocode coordinates to the nearest address via the OSM Nominatim API |
search_places | Search for places by name via the OSM Nominatim API |
find_nearby | Find places of a category near coordinates via the OSM Overpass API |
get_place_details | Get details of one OSM object (node, way or relation) via the Nominatim lookup API |
distance_between | Compute the great-circle distance in kilometres between two coordinate pairs (local, no API call) |
MCP client config:
{
"mcpServers": {
"streetmap-port": {
"command": "npx",
"args": ["-y", "@reneturcios/streetmap-port", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/streetmap-port # MCP server
docker run --rm ghcr.io/cloudcorprecords/streetmap-port --version
Development
npm install
npm run build
npm test
Data © OpenStreetMap contributors (ODbL). MIT license for the code.
Frequently asked questions
What is io.github.CloudCorpRecords/streetmap-port?
Geocode, reverse geocode and find nearby places with the public OpenStreetMap APIs.
How do I install io.github.CloudCorpRecords/streetmap-port?
It runs on your machine. In Claude Code: claude mcp add streetmap-port -- npx -y @reneturcios/streetmap-port@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.CloudCorpRecords/streetmap-port need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.CloudCorpRecords/streetmap-port open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.CloudCorpRecords/streetmap-port?
It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.