Provides tools for address autocomplete, forward and reverse geocoding, IP-based geolocation, and place/geofence/region context using the Radar Geocoding / Search API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-radar Geocode 841 Broadway, New York, NY"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Radar MCP — wraps the Radar Geocoding / Search API (radar.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tool | Description |
| Autocomplete an address/place from partial text using Radar. Returns ranked address/place suggestions with coordinates. Optionally bias results near a lat,lng. Example: radar_autocomplete({ query: "841 broadway new", near: "40.73,-73.99", apiKey: "prj_live_sk..." }) |
| Geocode an address to coordinates using Radar (forward geocoding). Returns the best-match formatted address with latitude/longitude. Example: radar_geocode({ query: "841 Broadway, New York, NY", apiKey: "prj_live_sk..." }) |
| Reverse geocode coordinates to an address using Radar. Returns the formatted address for a lat/lng. Example: radar_reverse_geocode({ lat: 40.70390, lon: -73.98670, apiKey: "prj_live_sk..." }) |
| Geolocate an IP address to city/state/country and approximate coordinates using Radar. Omit |
| Get place/geofence/region context for coordinates using Radar. Returns geofences, the containing place, and administrative region (country/state/postal code) for a lat/lng. Example: radar_context({ lat: 40.70390, lon: -73.98670, apiKey: "prj_live_sk..." }) |
Related MCP server: Google Maps MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"radar": {
"url": "https://gateway.pipeworx.io/radar/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/radar/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1576+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"radar": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-radar"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-radarIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Radar data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Geolocate Me turns your phone into location context for any AI assistant. Install the iOS or Android app, connect once with OAuth, and your GPS is queryable in natural language. Ask where you are, where you parked, where you were yesterday at 3pm, or how long you were at the office — the assistant calls the tool and answers with a real street address. https://geolocateme.app
The location engine for AI agents: one verified coordinate from where a user means. Beta: US.
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment
