OpenStreetMap MCP Server for LlamaIndexGive LlamaIndex instant access to 33 tools to Close Changeset, Close Note, Comment Note, and more

Name: OpenStreetMap
Price: 29 USD
Availability: InStock
Rating: 2.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add OpenStreetMap as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Ask AI about this MCP Server for LlamaIndex

Open in ChatGPT Open in Claude Open in Perplexity

The OpenStreetMap MCP Server for LlamaIndex is a standout in the Data Management category — giving your AI agent 33 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to OpenStreetMap. "
            "You have 33 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in OpenStreetMap?"
    )
    print(response)

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

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.

The OpenStreetMap MCP Server exposes 33 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 33 OpenStreetMap tools available for LlamaIndex

When LlamaIndex connects to OpenStreetMap through Vinkius, your AI agent gets direct access to every tool listed below — spanning geospatial, map-data, cartography, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

Close changeset on OpenStreetMap

Close a changeset

Close note on OpenStreetMap

Close a map note

comment

Comment note on OpenStreetMap

Add a comment to an existing map note

create

Create changeset on OpenStreetMap

Create a new changeset

create

Create element on OpenStreetMap

Create a new node, way, or relation

create

Create note on OpenStreetMap

Create a new map note

delete

Delete element on OpenStreetMap

Delete a node, way, or relation

delete

Delete message on OpenStreetMap

Delete a message

download

Download changeset on OpenStreetMap

Download a changeset in OsmChange format

get

Get auth user details on OpenStreetMap

Get details for the authenticated user

get

Get changeset on OpenStreetMap

Read a changeset by ID

get

Get element on OpenStreetMap

Read a node, way, or relation by ID

get

Get element history on OpenStreetMap

Get the history of a node, way, or relation

get

Get elements on OpenStreetMap

Multi-fetch nodes, ways, or relations

get

Get gpx data on OpenStreetMap

Download data for a GPS trace

get

Get gpx metadata on OpenStreetMap

Read metadata for a GPS trace

get

Get inbox on OpenStreetMap

Get the authenticated user's message inbox

get

Get map data on OpenStreetMap

Get map data (nodes, ways, relations) within a bounding box

get

Get message on OpenStreetMap

Read a specific message

get

Get note on OpenStreetMap

Read a map note by ID

get

Get outbox on OpenStreetMap

Get the authenticated user's message outbox

get

Get permissions on OpenStreetMap

Get OAuth permissions for the authenticated user

get

Get user on OpenStreetMap

Get details for a specific user

get

Get user preferences on OpenStreetMap

Get preferences for the authenticated user

list

List notes on OpenStreetMap

List map notes within a bounding box

list

List user gpx on OpenStreetMap

List GPS traces for the authenticated user

query

Query changesets on OpenStreetMap

Query changesets with filters

Search notes on OpenStreetMap

Search for map notes

send

Send message on OpenStreetMap

Send a private message to another user

update

Update changeset on OpenStreetMap

Update tags of an open changeset

update

Update element on OpenStreetMap

Update an existing node, way, or relation

update

Update message status on OpenStreetMap

Update the read status of a message

upload

Upload gpx on OpenStreetMap

Upload a GPS trace (GPX)

Connect OpenStreetMap to LlamaIndex via MCP

Follow these steps to wire OpenStreetMap into LlamaIndex. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 33 tools from OpenStreetMap

Why Use LlamaIndex with the OpenStreetMap MCP Server

LlamaIndex provides unique advantages when paired with OpenStreetMap through the Model Context Protocol.

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 + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the OpenStreetMap MCP Server delivers measurable value.

Hybrid search: combine OpenStreetMap real-time data with embedded document indexes for answers that are both current and comprehensive

Data enrichment: query OpenStreetMap to augment indexed data with live information before generating user-facing responses

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying OpenStreetMap for fresh data

Analytical workflows: chain OpenStreetMap queries with LlamaIndex's data connectors to build multi-source analytical reports

Example Prompts for OpenStreetMap in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with OpenStreetMap immediately.

"Get map data for the bounding box -0.15, 51.50, -0.10, 51.52 (Central London)."

"Show me the history of way ID 4225123."

"Find the 5 most recent closed changesets by user 'JohnDoe'."

Troubleshooting OpenStreetMap MCP Server with LlamaIndex

Common issues when connecting OpenStreetMap to LlamaIndex through Vinkius, and how to resolve them.

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

OpenStreetMap + LlamaIndex FAQ

Common questions about integrating OpenStreetMap MCP Server with LlamaIndex.

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.