How to integrate Google Maps MCP with OpenCode

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Google Maps logo
OpenCode logo
divider

How to integrate Google Maps MCP with OpenCode

This guide explains how to connect Google Maps MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Google Maps with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Google Maps with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Google Maps

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Google Maps Composio".
  3. Complete the authentication and authorization flow, and your Google Maps integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Google Maps to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Google Maps with OpenCode

Now, in the chat, ask the agent to connect to Google Maps or give it any Google Maps-related task.

For example, ask it to:

  • "Find walking directions from your hotel to conference center"
  • "Show top-rated coffee shops near your location"
  • "Embed a map of downtown restaurants on your website"

It will prompt you to authenticate and authorize access to Google Maps.

That is it. Composio tools are now available in OpenCode, and your Google Maps account is ready to use.

Supported Tools & Triggers

Tools
Autocomplete Place PredictionsReturns place and query predictions for text input.
Compute Route MatrixCalculates travel distance and duration matrix between multiple origins and destinations using the modern Routes API; supports OAuth2 authentication and various travel modes.
Geocode Address With QueryTool to map addresses to geographic coordinates with query parameter.
Geocode DestinationsTool to perform destination lookup and return detailed destination information including primary place, containing places, sub-destinations, landmarks, entrances, and navigation points.
Reverse Geocode LocationTool to convert geographic coordinates (latitude and longitude) to human-readable addresses using reverse geocoding.
Geocode Place by IDTool to perform geocode lookup using a place identifier to retrieve address and coordinates.
Geocoding APIConvert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a Place ID.
Geolocate DeviceTool to determine location based on cell towers and WiFi access points.
Get 2D Map TileTool to retrieve a 2D map tile image at specified coordinates for building custom map visualizations.
Get 3D Tiles RootTool to retrieve the 3D Tiles tileset root configuration for photorealistic 3D map rendering.
Get Place DetailsRetrieves comprehensive details for a place using its resource name (places/{place_id} format).
Get RouteCalculates one or more routes between two specified locations.
Lookup Aerial VideoTool to look up an aerial view video by address or video ID.
Embed Google MapTool to generate an embeddable Google Map URL and HTML iframe code.
Nearby searchSearches for places (e.
Get Place PhotoRetrieves high quality photographic content from the Google Maps Places database.
Render Aerial VideoStarts rendering an aerial view video for a US postal address.
Text SearchSearches for places on Google Maps using a textual query (e.
Create Tiles SessionTool to create a session token required for accessing 2D Tiles and Street View imagery.

Way Forward

Now that Google Maps is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Google Maps MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Google Maps MCP?

With a standalone Google Maps MCP server, the agents and LLMs can only access a fixed set of Google Maps tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Maps and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Maps tools.

Can I manage the permissions and scopes for Google Maps while using Tool Router?

Yes, absolutely. You can configure which Google Maps scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Maps data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.