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 LlamaIndex?
LlamaIndex agents combine OpenStreetMap tool responses with indexed documents for comprehensive, grounded answers. Connect 33 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine OpenStreetMap tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain OpenStreetMap tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query OpenStreetMap, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what OpenStreetMap tools were called, what data was returned, and how it influenced the final answer
OpenStreetMap in LlamaIndex
OpenStreetMap and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenStreetMap to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query OpenStreetMap tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
Plex
15 toolsManage your Plex Media Server — browse libraries, search media, check active streams and control playback from any AI agent.

NOAA Alerts — US Severe Weather Warnings
4 toolsReal-time NWS severe weather alerts: tornado warnings, hurricane watches, flood advisories, winter storms, and 120+ alert types filtered by state, zone, or exact location across the United States.

Google Play Developer
12 toolsManage your Android apps - respond to reviews and check subscriptions via AI.

Lemlist
8 toolsEquip your AI agent with direct access to Lemlist — manage cold email campaigns, track lead engagement, and automate outreach without opening the Lemlist dashboard.
