OpenStreetMap MCP Server

Created By
NERVsystemsa year ago
OpenStreetMap MCP server providing precision geospatial tools for LLMs via Model Context Protocol. Features geocoding, routing, nearby places, neighborhood analysis, EV charging stations, and more.
Overview

What is OpenStreetMap MCP Server?

OpenStreetMap MCP Server is a geospatial tool that provides precision geospatial capabilities for large language models (LLMs) via the Model Context Protocol. It allows users to interact with OpenStreetMap data for various applications.

How to use OpenStreetMap MCP Server?

To use the server, you can either download the pre-built binaries or build it from source using Go. Once set up, you can run the server and integrate it with compatible clients like Claude Desktop Client.

Key features of OpenStreetMap MCP Server?

  • Geocoding and reverse geocoding capabilities
  • Finding nearby points of interest and EV charging stations
  • Route directions and analysis of commute options
  • Neighborhood livability analysis
  • Composable tool design for complex workflows

Use cases of OpenStreetMap MCP Server?

  1. Finding optimal meeting points for groups.
  2. Analyzing transportation options between home and work.
  3. Exploring areas for real estate decisions.
  4. Locating EV charging stations along a route.

FAQ from OpenStreetMap MCP Server?

  • What programming language is used?

    The server is built using Go.

  • Is there an API key required?

    No API keys are required, but usage policies apply.

  • Can it be used for real-time applications?

    Yes, it is designed for high performance and can be integrated into real-time applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NERVsystems
Star
1
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago