Pelias Geocoder MCP Server for Google ADK 10 tools — connect in under 2 minutes
Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Pelias Geocoder as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
StreamableHTTPConnectionParams,
)
# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
connection_params=StreamableHTTPConnectionParams(
url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
)
)
agent = Agent(
model="gemini-2.5-pro",
name="pelias_geocoder_agent",
instruction=(
"You help users interact with Pelias Geocoder "
"using 10 available tools."
),
tools=[mcp_tools],
)
* 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 Pelias Geocoder MCP Server
Empower your logical AI generative environments extracting robust structural limits across the Pelias Geocoding Platform. Execute formal explicitly bounded parameter checks natively identifying coordinates logically structuring text into GPS metrics via Search/Autocomplete arrays implicitly evaluating point-of-interests securely mapped seamlessly.
Google ADK natively supports Pelias Geocoder as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.
What you can do
- Geocoding Pipelines — Execute logical bounded structures checking human-readable address parameters seamlessly natively resolving to structured bounding coordinates dynamically
- Reverse Geocoding — Dispatch explicit strict positional bounds (Lat/Long) parsing logic pulling real-world place arrays locally checking limits internally gracefully
- Structural Autocompletion — Query dynamic bounding nodes checking continuous input logs mapping explicit native POIs parsing geographic records securely
- Place Queries — Map formal instances determining the exact JSON limits corresponding to specific GID properties returned seamlessly
The Pelias Geocoder MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK 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 Pelias Geocoder to Google ADK via MCP
Follow these steps to integrate the Pelias Geocoder MCP Server with Google ADK.
Install Google ADK
Run pip install google-adk
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Create the agent
Save the code above and integrate into your ADK workflow
Explore tools
The agent will discover 10 tools from Pelias Geocoder via MCP
Why Use Google ADK with the Pelias Geocoder MCP Server
Google ADK provides unique advantages when paired with Pelias Geocoder through the Model Context Protocol.
Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution
Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Pelias Geocoder
Production-ready features like session management, evaluation, and deployment come built-in. not bolted on
Seamless integration with Google Cloud services means you can combine Pelias Geocoder tools with BigQuery, Vertex AI, and Cloud Functions
Pelias Geocoder + Google ADK Use Cases
Practical scenarios where Google ADK combined with the Pelias Geocoder MCP Server delivers measurable value.
Enterprise data agents: ADK agents query Pelias Geocoder and cross-reference results with internal databases for comprehensive analysis
Multi-modal workflows: combine Pelias Geocoder tool responses with Gemini's vision and language capabilities in a single agent
Automated compliance checks: schedule ADK agents to query Pelias Geocoder regularly and flag policy violations or configuration drift
Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Pelias Geocoder
Pelias Geocoder MCP Tools for Google ADK (10)
These 10 tools become available when you connect Pelias Geocoder to Google ADK via MCP:
lookup_place_id
Irreversibly vaporize explicit validations extracting rich schema properties
reverse_distance_limit
circle.radius` checking exactly how far from the point Pelias should search. Retrieve the exact structural matching verifying Reverse alternatives
reverse_geocode
Perform structural extraction of properties driving active OSM Pins
search_autocomplete
Retrieve explicit Cloud logging tracing explicit Keypress constraints
search_bounding_box
rect` figuring out what geometries strictly fall inside the map coordinate rectangle. Dispatch an automated validation check routing explicit Box arrays
search_country_filter
country` fetching localized boundaries matching ISO 3166 limits. Identify explicit tracking networks dropping extraneous international domains
search_focus_bias
point` enforcing Pelias to prioritize results physically closer to the GPS trace. Inspect deep internal arrays mitigating specific Center biases
search_geocode
Identify bounded routing spaces inside the Headless Pelias Maps
search_layer_filter
Enumerate explicitly attached structured rules exporting active GIS datasets
structured_geocoding
g address=X region=Y safely isolating terms. Identify precise active arrays spanning native Location limits
Example Prompts for Pelias Geocoder in Google ADK
Ready-to-use prompts you can give your Google ADK agent to start working with Pelias Geocoder immediately.
"Log natively bounding coordinates logically extracted seamlessly for the explicit address '10 Downing St, London'."
"Reverse query the explicit structure gracefully checking logical metadata coordinates lat `40.7484` and lon `-73.9856` natively limits."
"Check suggestions validating autocompletion logs evaluating string inputs structurally starting with bounds 'Statue of L'."
Troubleshooting Pelias Geocoder MCP Server with Google ADK
Common issues when connecting Pelias Geocoder to Google ADK through the Vinkius, and how to resolve them.
McpToolset not found
pip install --upgrade google-adkPelias Geocoder + Google ADK FAQ
Common questions about integrating Pelias Geocoder MCP Server with Google ADK.
How does Google ADK connect to MCP servers?
Can ADK agents use multiple MCP servers?
Which Gemini models work best with MCP tools?
Connect Pelias Geocoder with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Pelias Geocoder to Google ADK
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.