Live map example
Loading the Mapsource map…
Request / Response
Call a geographic MCP tool
Invoke registry-backed place lookup and read the REST-shaped data from structured content.
API call
const result = await client.callTool({
name: "geo_search",
arguments: { operation: "lookup", q: "coffee", lat: 45.52, lon: -122.68, limit: 3 }
});Example response
{"isError":false,"structuredContent":{"status":200,"quotaRemaining":"49999","retryAfter":null,"data":{"schema":"mapsource-lookup.v1","query":"coffee","ambiguous":false,"results":[{"id":"openstreetmap:node/1234567890","name":"Example Coffee","coordinate":{"lat":45.5212,"lon":-122.6794}}]}}}Ground answers in service results
Agents can request current places, OSM features, routes, elevation and spatial calculations rather than inventing coordinates or treating model memory as a geographic database.
Use one contract across REST and MCP
The hosted server exposes registry-backed tools with the same API key, quotas, errors and provenance as the REST operations beneath them.
Service details
Built around a published contract
Inputs, outputs and limits remain inspectable in the generated API reference.
- Transport
- Streamable HTTP at /mcp
- Discovery
- MCP tools/list and /mcp.json
- Families
- Search, data, navigation, analysis and render
- Authentication
- Bearer API key