How do I get a Google Maps API Key?

Go to the Google Cloud Console, create a project, enable the Maps APIs (Geocoding, Places, Directions, etc.), and generate an API Key in the Credentials section.

A Place ID is a unique text identifier for a place (e.g., 'ChIJN1t_tDeuEmsRUsoyG83frY4'). You can get it using the 'search_nearby_places' or 'find_place_from_text' tools, and use it to get detailed info via 'get_place_details'.

Can I get travel times for public transit?

Yes! Use 'get_directions' or 'get_distance_matrix' with mode set to 'transit'. Note that transit data availability depends on the city and Google's coverage.

Google Maps Platform MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Google Maps Platform
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Google Maps Platform through the Vinkius — pass the Edge URL in the `mcps` parameter and every Google Maps Platform tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Google Maps Platform Specialist",
    goal="Help users interact with Google Maps Platform effectively",
    backstory=(
        "You are an expert at leveraging Google Maps Platform tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Google Maps Platform "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Google Maps Platform MCP Server

Connect Google Maps Platform to any AI agent and access the world's most accurate location intelligence — from turn-by-turn directions and distance matrices to rich place details and timezone data.

When paired with CrewAI, Google Maps Platform becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Google Maps Platform tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Geocoding — Convert any address into precise latitude/longitude coordinates
Place Details — Get comprehensive info for any business (hours, phone, ratings, reviews)
Directions & Routing — Calculate routes for driving, walking, cycling, or public transit
Distance Matrix — Compare travel times and distances between multiple locations
Nearby Search — Find businesses or points of interest around a specific location
Elevation & Timezone — Get altitude data and timezone info for any coordinate

The Google Maps Platform MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Google Maps Platform to CrewAI via MCP

Follow these steps to integrate the Google Maps Platform MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 9 tools from Google Maps Platform

Why Use CrewAI with the Google Maps Platform MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Google Maps Platform through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Google Maps Platform + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Google Maps Platform MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Google Maps Platform for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Google Maps Platform, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Google Maps Platform tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Google Maps Platform against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Google Maps Platform MCP Tools for CrewAI (9)

These 9 tools become available when you connect Google Maps Platform to CrewAI via MCP:

find_place_from_text

Useful to get the Place ID or location before getting details. Find a place based on a text query

geocode_address

g., "1600 Amphitheatre Parkway, Mountain View, CA") and need the exact GPS coordinates. Returns the formatted address and the place_id. Convert a physical address into geographic coordinates (latitude/longitude)

get_directions

Supports modes: "driving" (default), "walking", "bicycling", "transit". Get travel directions between two points

get_distance_matrix

Origins and destinations can be single or multiple addresses/coordinates separated by pipe (|). Calculate travel distance and time for multiple origins and destinations

get_elevation

Input can be single "lat,lng" or multiple locations. Get elevation data for locations on the earth

get_place_details

Requires a valid Place ID obtained from other search tools. Get detailed information about a specific place using its Place ID

get_timezone

Essential for scheduling across time zones. Get timezone information for a specific location

reverse_geocode

Useful for identifying locations from GPS data. Convert GPS coordinates back into a physical address

search_nearby_places

You can filter by "type" (e.g., "restaurant", "gas_station") or "keyword". Radius is in meters. Search for places of interest near a specific coordinate

Example Prompts for Google Maps Platform in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Google Maps Platform immediately.

"Find the address for 'Statue of Liberty'."

"Get directions from Times Square to Central Park."

"Find coffee shops near 'Pike Place Market'."

Troubleshooting Google Maps Platform MCP Server with CrewAI

Common issues when connecting Google Maps Platform to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Google Maps Platform + CrewAI FAQ

Common questions about integrating Google Maps Platform MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.