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
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago