4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to OpenStreetMap through Vinkius, pass the Edge URL in the `mcps` parameter and every OpenStreetMap tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The OpenStreetMap MCP Server for CrewAI 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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="OpenStreetMap Specialist",
    goal="Help users interact with OpenStreetMap effectively",
    backstory=(
        "You are an expert at leveraging OpenStreetMap tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in OpenStreetMap "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 33 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
OpenStreetMap
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.

When paired with CrewAI, OpenStreetMap becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenStreetMap tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI

When CrewAI 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

Close changeset on OpenStreetMap

Close a changeset

close

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

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 CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 33 tools from OpenStreetMap

Why Use CrewAI with the OpenStreetMap MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with OpenStreetMap through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

OpenStreetMap + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries OpenStreetMap for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries OpenStreetMap, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain OpenStreetMap tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries OpenStreetMap against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for OpenStreetMap in CrewAI

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

01

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

02

"Show me the history of way ID 4225123."

03

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

Troubleshooting OpenStreetMap MCP Server with CrewAI

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

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

OpenStreetMap + CrewAI FAQ

Common questions about integrating OpenStreetMap MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →