# TomTom MCP > TomTom equips your AI agent with global mapping, routing, and real-time traffic data. Convert any address to precise coordinates, calculate driving times between two points, or map live accidents within a specific area using this MCP. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** mapping, routing, geocoding, traffic-data, location-services, logistics ## Description This connector lets you bring enterprise-grade location intelligence directly into your chat workflow. You can turn messy physical addresses into exact latitude/longitude pairs, and vice versa, so your agent always knows precisely where something is. Need to plan a trip? Input two coordinates, and the tool calculates the optimal route polyline, total distance, and estimated travel time, factoring in current conditions. It even maps out live traffic incidents—like accidents or construction zones—within any bounding box you define. If you're managing assets, you can figure out exactly how far your fleet can drive given a set time limit. Connecting this MCP through Vinkius gives your AI client immediate access to thousands of location services, making complex logistics questions simple chat queries. ## Tools ### calculate_reachable_range Determines the full area that can be covered, given a starting point and maximum travel time in seconds. ### calculate_route Calculates the direct route polyline, total distance, and estimated driving time between two specific coordinates. ### search_poi_by_category Locates points of interest (POIs) near a coordinate by specifying a category like 'hospitals' or 'fuel'. ### fuzzy_geocoding Converts an address string into precise coordinates, even if the input address has minor spelling errors. ### get_poi_details Retrieves detailed information and rich metadata for a specific point of interest ID found earlier. ### get_traffic_incidents Pulls real-time details on traffic incidents, like accidents or construction, within any defined map boundaries. ### get_traffic_flow_segment Retrieves the current speed and overall quality of travel for a specific segment of road at a given coordinate. ### reverse_geocoding Converts geographic coordinates back into a readable, formatted street address string. ### autocomplete_place_search Offers predictive location suggestions as you type a partial place name or address segment. ### structured_geocoding Converts an address into coordinates using required components like the country code and postal zip code for accuracy. ## Prompt Examples **Prompt:** ``` Convert these coordinates into an address: Lat 40.7128, Lon -74.0060. ``` **Response:** ``` The coordinates return an address explicitly linked to the parameter grid: - Broad St, New York, NY 10004, United States ``` **Prompt:** ``` Check for any traffic incidents on the 101 freeway bounded roughly by these dimensions. ``` **Response:** ``` A real-time scan revealed 1 active traffic incident in that bounding box: - Type: Accident/Lane blocked - Severity: Major delay expected - Center: Lat 34.05, Lon -118.25 ``` ## Capabilities ### Convert Addresses and Coordinates Translate any street address into accurate geographic coordinates or reverse the process to find a street name from given coordinates. ### Plan Optimal Routes Calculate the necessary route, distance, and time needed for travel between two precise points using this MCP. ### Monitor Real-Time Traffic Scan a defined area to identify live traffic incidents or assess the current speed and quality of a specific road segment. ### Find Local Points of Interest Search for categories like hospitals or gas stations near a location, retrieving key contact details along the way. ### Determine Operational Boundaries Calculate the maximum area (polygonal limit) your agents or vehicles can reach within a given time budget. ## Use Cases ### Dispatching a repair crew after an accident. The manager asks: 'Check for traffic incidents near Lat 34.05, Lon -118.25.' The agent uses get_traffic_incidents to confirm an accident and then uses calculate_reachable_range to see if the crew can reach it within a two-hour window. ### Mapping out service zones for expansion. A developer asks: 'What area around this warehouse can we serve in 4 hours?' The agent calls calculate_reachable_range, providing the precise polygonal limit of potential new territory. ### Validating customer-provided addresses. The user inputs a handwritten address. The agent uses fuzzy_geocoding to convert it into validated coordinates, and then reverse_geocoding confirms the exact street name for billing records. ### Optimizing delivery schedules in a new city. The planner asks: 'What is the fastest route between these three points?' The agent uses calculate_route multiple times and compares results, factoring in current real-time traffic data for maximum efficiency. ## Benefits - Stop guessing addresses. Use fuzzy_geocoding or structured_geocoding to guarantee precise coordinates from any input string, even if it's messy. - Get immediate route planning by calling calculate_route. You get the polyline geometry and travel time summary in one query, skipping multiple API calls. - Monitor road conditions instantly. Use get_traffic_incidents to map live accidents or use get_traffic_flow_segment to check if a specific avenue is backed up. - Never lose track of resources. The calculate_reachable_range tool tells you exactly how far your vehicles can go based on time and starting point. - Discover local services without leaving the chat. Search for POIs using search_poi_by_category, then get all the contact info via get_poi_details. ## How It Works The bottom line is, you stop writing complex API calls and start asking natural questions about geography and logistics. 1. First, add this marketplace component to your workflow. Then, grab a secure API token from the TomTom Developer Portal. 2. Plug that key into the MCP and let your agent know what coordinates or addresses it needs to process. 3. Your AI client processes the request and returns structured data like polyline routes, traffic reports, or specific location metadata. ## Frequently Asked Questions **How does TomTom MCP handle bad addresses?** It uses fuzzy_geocoding and structured_geocoding. These tools can convert physical address strings into accurate coordinates even if the input is messy or incomplete. **Can I find traffic information for a whole region?** Yes, you use get_traffic_incidents by providing minimum and maximum latitude/longitude boundaries. This gives you an overview of accidents and jams in that entire box. **Is calculate_route just straight-line distance?** No. calculate_route calculates the actual polyline geometry, total distance, and estimated travel time based on typical road networks, not just a straight line through space. **How do I get contact information for a business near me?** First, use search_poi_by_category to locate the point of interest. Then, call get_poi_details using its unique ID to pull out rich metadata like phone numbers and hours. **Does TomTom MCP account for travel time limitations?** Yes. The calculate_reachable_range tool determines the exact polygonal area you can reach given a specific time budget in seconds.