myDevices MCP Server for Google ADK 8 tools — connect in under 2 minutes
Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add myDevices as an MCP tool provider through the 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="mydevices_agent",
instruction=(
"You help users interact with myDevices "
"using 8 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 myDevices MCP Server
Connect your myDevices Cayenne account to empower your AI agents with IoT capabilities. This server allows for real-time monitoring and control of connected sensors and actuators.
Google ADK natively supports myDevices as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 8 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
- Device Visibility — List and inspect all connected IoT devices and their metadata
- Telemetry Monitoring — Access real-time sensor data and historical telemetry records
- Remote Control — Send commands to actuators and control hardware programmatically
- Alert Management — Monitor and track IoT system alerts and notifications
The myDevices MCP Server exposes 8 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 myDevices to Google ADK via MCP
Follow these steps to integrate the myDevices 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 8 tools from myDevices via MCP
Why Use Google ADK with the myDevices MCP Server
Google ADK provides unique advantages when paired with myDevices 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 myDevices
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 myDevices tools with BigQuery, Vertex AI, and Cloud Functions
myDevices + Google ADK Use Cases
Practical scenarios where Google ADK combined with the myDevices MCP Server delivers measurable value.
Enterprise data agents: ADK agents query myDevices and cross-reference results with internal databases for comprehensive analysis
Multi-modal workflows: combine myDevices tool responses with Gemini's vision and language capabilities in a single agent
Automated compliance checks: schedule ADK agents to query myDevices regularly and flag policy violations or configuration drift
Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including myDevices
myDevices MCP Tools for Google ADK (8)
These 8 tools become available when you connect myDevices to Google ADK via MCP:
get_device
Get device details
get_sensor_data
Get current sensor value
get_sensor_history
Get historical sensor data
list_alerts
List IoT alerts
list_applications
List all applications
list_devices
List all IoT devices
list_sensors
List sensors for a device
send_command
Send command to device
Example Prompts for myDevices in Google ADK
Ready-to-use prompts you can give your Google ADK agent to start working with myDevices immediately.
"List all my connected IoT devices."
"What is the current temperature reading from 'Sensor #1'?"
Troubleshooting myDevices MCP Server with Google ADK
Common issues when connecting myDevices to Google ADK through the Vinkius, and how to resolve them.
McpToolset not found
pip install --upgrade google-adkmyDevices + Google ADK FAQ
Common questions about integrating myDevices 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 myDevices 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 myDevices to Google ADK
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.
