Developer Tools
mapsource.io
Provides geospatial data queries for map features, elevation, and basemap tiles from OpenStreetMap and CARTO.
ENDPOINT 1
https://mapsource.io/mcp
MCP server metadata
- Name
- mapsource-overpass
- Version
- 0.2.0
Known tools 5
service_statusCheck engine readiness, fixture versus planet data, freshness, and payment mode.
Potential side effectsbasemap_catalogDiscover CARTO Dark Matter and Positron raster tile templates, snapshot date, attribution, and header authentication.
Inferred read-onlyoverpass_queryExecute Overpass QL over OSM nodes, ways, and relations with bounded output.
Potential side effectsfind_featuresFind cafes, restaurants, buildings, parks, schools, hospitals, transit stops, drinking water, or trails in an explicit small bounding box.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mapsource-overpass]
url = "https://mapsource.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mapsource-overpass": {
"type": "http",
"url": "https://mapsource.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mapsource-overpass
Remote MCP URL: https://mapsource.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mapsource-overpass": {
"url": "https://mapsource.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mapsource-overpass": {
"type": "http",
"url": "https://mapsource.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mapsource-overpass",
"transport": "streamable-http",
"url": "https://mapsource.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.