OpenStreetMap MCP Server

Created By
Subhashnaidudullaa year ago
OpenStreetMap MCP Server Implementation
Overview

what is OpenStreetMap MCP Server?

OpenStreetMap MCP Server is a Map Control Protocol (MCP) server implementation designed for integrating OpenStreetMap data.

how to use OpenStreetMap MCP Server?

To use the server, install the necessary dependencies, configure the environment variables, and start the server using npm commands.

key features of OpenStreetMap MCP Server?

  • OpenStreetMap data integration
  • MCP protocol implementation
  • RESTful API endpoints
  • Map tile serving capabilities

use cases of OpenStreetMap MCP Server?

  1. Integrating OpenStreetMap data into applications.
  2. Serving map tiles for web and mobile applications.
  3. Implementing custom mapping solutions using the MCP protocol.

FAQ from OpenStreetMap MCP Server?

  • What is the MCP protocol?

The MCP protocol is a standard for map control that allows for efficient communication between map clients and servers.

  • Is there documentation available?

Yes! API documentation is available at /api-docs when the server is running.

  • What license is the project under?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Subhashnaidudulla
Star
0
Language
JavaScript
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