MCP AI Agent with Google ADK, Google Maps, and Opik

Created By
luuisotorresa year ago
AI Agent built with Google ADK that leverages Google Maps MCP Server to answer real-world location questions with tool usage and traceable execution via Opik.
Overview

What is MCP AI Agent?

MCP AI Agent is an AI-driven application built using the Google Agent Development Kit (ADK) that utilizes the Google Maps MCP Server to answer real-world location queries through tool usage and traceable execution via Opik.

How to use MCP AI Agent?

To use the MCP AI Agent, clone the repository, set up the required environment variables with your API keys, and run the ADK web UI to interact with the agent through a web interface.

Key features of MCP AI Agent?

  • Integration with Google Maps for real-time location queries.
  • Utilizes OpenAI's GPT-4o model for natural language processing.
  • Observability and tracing of agent interactions using Opik and CometML.

Use cases of MCP AI Agent?

  1. Providing driving, walking, or cycling directions.
  2. Fetching place details and reviews for landmarks.
  3. Calculating travel times and distances between locations.

FAQ from MCP AI Agent?

  • Can MCP AI Agent answer all location-related questions?

Yes! It can handle various queries related to directions, place details, and more using Google Maps APIs.

  • Is there a cost to use the MCP AI Agent?

The agent itself is free to use, but you may incur costs based on the usage of Google Maps and OpenAI APIs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
luuisotorres
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago