Compatible with every major AI agent and IDE
What is the OpenStreetMap MCP Server?
Connect your AI agent to the world's largest open geographic database. This server enables full interaction with the OpenStreetMap API (v0.6), allowing you to query, create, and update geospatial data through natural conversation.
What you can do
- Map Data Retrieval — Fetch raw OSM data (nodes, ways, relations) within specific bounding boxes for analysis or visualization.
- Element Management — Create, read, update, or delete map elements including points of interest (nodes), roads (ways), and complex boundaries (relations).
- Changeset Workflows — Open, update, and close changesets to group your edits and provide meaningful metadata to the OSM community.
- Historical Analysis — Retrieve the full version history of any map element to track changes over time.
- Advanced Querying — Filter changesets by user, time range, or geographic area to monitor local mapping activity.
How it works
- Subscribe to this server
- Enter your OpenStreetMap OAuth Token
- Start exploring and editing the map from Claude, Cursor, or any MCP-compatible client
Your AI can now act as a GIS specialist, helping you audit map data or contribute to open-source geography without leaving your workspace.
Who is this for?
- GIS Analysts — quickly extract raw map data for specific regions without manual exports
- Open Source Contributors — automate the creation of map elements and manage changesets via chat
- Developers — inspect map element metadata and history directly while building location-based services
Built-in capabilities (33)
Close a changeset
Close a map note
Add a comment to an existing map note
Create a new changeset
Create a new node, way, or relation
Create a new map note
Delete a node, way, or relation
Delete a message
Download a changeset in OsmChange format
Get details for the authenticated user
Read a changeset by ID
Read a node, way, or relation by ID
Get the history of a node, way, or relation
Multi-fetch nodes, ways, or relations
Download data for a GPS trace
Read metadata for a GPS trace
Get the authenticated user's message inbox
Get map data (nodes, ways, relations) within a bounding box
Read a specific message
Read a map note by ID
Get the authenticated user's message outbox
Get OAuth permissions for the authenticated user
Get details for a specific user
Get preferences for the authenticated user
List map notes within a bounding box
List GPS traces for the authenticated user
Query changesets with filters
Search for map notes
Send a private message to another user
Update tags of an open changeset
Update an existing node, way, or relation
Update the read status of a message
Upload a GPS trace (GPX)
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with OpenStreetMap through native MCP adapters. Connect 33 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine OpenStreetMap MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across OpenStreetMap queries for multi-turn workflows
OpenStreetMap in LangChain
OpenStreetMap and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenStreetMap to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OpenStreetMap in LangChain
The OpenStreetMap MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 33 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
OpenStreetMap for LangChain
Every tool call from LangChain to the OpenStreetMap MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I download map data for a specific region?
Use the get_map_data tool by providing a bounding box string (left, bottom, right, top). The agent will retrieve all nodes, ways, and relations within those coordinates.
Can I see who edited a specific road or building?
Yes! Use the get_element_history tool with the element type (node, way, or relation) and its ID. It will return the full version history, including timestamps and user information.
Is it possible to search for recent map updates in a city?
You can use query_changesets with a bbox (bounding box) parameter. This will list all changesets that intersect with that area, allowing you to inspect recent mapping activity.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Mention
12 toolsMonitor brand mentions across the web, social media, and news in real time to protect your reputation and spot trends early.

MINDBODY Health & Wellness
10 toolsManage your wellness business via MINDBODY — track class schedules, client profiles, and visit history directly via AI.

Keap
11 toolsManage CRM contacts, marketing campaigns, and sales automation via Keap.

Calendly Alternative
12 toolsManage meetings and scheduling via Calendly — list event types, track scheduled events, inspect invitees and manage webhooks from any AI agent.
