MapQuest MCP. Get routes and pinpoint any location with coordinates.

This MapQuest MCP Server gives your agent location intelligence—it's basically an entire atlas bolted right onto the toolset. You use it whenever you need to know where something is or how to get there. It handles coordinates, full street addresses, points of interest (POIs), and static map images.

If you start with a physical address, your agent uses geocode_address to convert that full street name into precise latitude and longitude pairs. That's the first thing it does: pinpointing where an address is on the globe. Conversely, if all you've got are raw GPS coordinates—say, from a sensor reading—you run reverse_geocode.

This tool takes those numbers and spits out the most probable, human-readable street address for that exact spot.

When it comes to figuring out where people actually go, your agent can search for local spots using search_points_of_interest. You tell it what kind of business you're looking for—maybe a coffee shop or a gas station—and the tool returns specific nearby locations around a given point. It doesn’t just guess; it finds real types of businesses in an area.

For trip planning, get_directions is your go-to function. This calculates full travel routes between two points and gives you more than just a straight line—it provides turn-by-turn instructions for driving, walking, or biking. It also tells you the estimated distance and how long the whole thing'll take. You can calculate multi-modal routes; it works whether your agent is operating in a car, on foot, or by bike.

If you need to show someone exactly where something is, even if you don't want them to use a live map service, get_static_map_url generates that URL. You feed the coordinates into this tool, and it hands you an image URL ready for display—a static picture of the map centered right on those specific points.

It’s perfect for embedding location data directly into reports or messages without needing a live map connection.

You'll use these tools together all the time. For instance, if you need to plan a route (using get_directions), but you only have an address instead of two sets of coordinates, you first run that address through geocode_address to get your starting and ending latitude/longitude pairs. Then, you pass those resulting coordinates into get_directions.

If the trip involves finding the nearest car wash along the way, you use search_points_of_interest near a point on the calculated route. Finally, if someone needs a visual confirmation of the entire path, you feed the key coordinate points into get_static_map_url to generate the final image link.

Don't think of it as just five separate buttons. Think of it as a complete location stack for your agent. You can verify an address (using geocode_address), then figure out what that spot is called in plain English (using reverse_geocode). You can find the nearest service station nearby (via search_points_of_interest) and calculate how long you'll take to get there, whether you drive or walk (get_directions).

If you need to share a picture of the neighborhood map, get_static_map_url handles that. It’s reliable infrastructure for any task involving geography.