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
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago