What Alexa-connected devices are supported by this API?

The Alexa Smart Properties API supports: smart lights (on/off, brightness, color), smart plugs and switches, thermostats (mode and temperature monitoring), temperature sensors, Echo devices and speakers (volume control), security sensors, and other Alexa-connected endpoints. Each device exposes specific features (power, brightness, speaker, thermostat, etc.) that can be queried and controlled.

How do I get an OAuth 2.0 access token for the Alexa API?

Visit the [**Alexa Developer Console**](https://developer.amazon.com/alexa/console/ask) and create a Smart Home Skill. Set up Login with Amazon (LWA) credentials in your Amazon Developer account. Complete the OAuth 2.0 authorization flow to obtain an access token. The token must be refreshed periodically as it expires after a set duration.

Can I control devices in different rooms or properties?

Yes! The API returns all devices across all properties and rooms in your Alexa Smart Properties account. Use `list_alexa_devices` to see all devices with their room assignments, then use each device's unique endpoint ID to control them individually. You can also reassign devices to different rooms using the `update_device_room` action.

What's the difference between deregister and forget a device?

`Deregister` removes the device from your Alexa Smart Properties account but keeps it available for re-discovery. The device itself remains configured. `Forget` completely removes the device from Alexa — it will need to be re-discovered and set up again as if it were a new device. Use deregister for temporary removal and forget for permanent removal.

Alexa Smart Home MCP Server for Google ADK 16 tools — connect in under 2 minutes

Name: Alexa Smart Home
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 16 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Alexa Smart Home as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

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="alexa_smart_home_agent",
    instruction=(
        "You help users interact with Alexa Smart Home "
        "using 16 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 Alexa Smart Home MCP Server

Connect to Alexa Smart Home devices via the Alexa Smart Properties API and control your smart home from any AI agent. Manage lights, thermostats, speakers, and sensors across your connected endpoints.

Google ADK natively supports Alexa Smart Home as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 16 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

List Devices — See all your Alexa-connected smart home devices with names, manufacturers, and features
Device Details — Get full device information including serial numbers, connections, and capabilities
Power Control — Turn devices on and off (lights, plugs, switches)
Light Control — Get and set brightness levels, adjust brightness relatively
Speaker Control — Get and set speaker volume on Alexa devices
Thermostat Monitoring — View thermostat state including mode and target temperatures
Temperature Sensors — Read current temperature from connected sensors
Rename Devices — Update friendly names for your devices
Room Management — Assign devices to specific rooms/units
Device Management — Deregister or forget devices from your Alexa account

The Alexa Smart Home MCP Server exposes 16 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 Alexa Smart Home to Google ADK via MCP

Follow these steps to integrate the Alexa Smart Home 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 16 tools from Alexa Smart Home via MCP

Why Use Google ADK with the Alexa Smart Home MCP Server

Google ADK provides unique advantages when paired with Alexa Smart Home 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 Alexa Smart Home

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 Alexa Smart Home tools with BigQuery, Vertex AI, and Cloud Functions

Alexa Smart Home + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Alexa Smart Home MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Alexa Smart Home and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Alexa Smart Home tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Alexa Smart Home regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Alexa Smart Home

Alexa Smart Home MCP Tools for Google ADK (16)

These 16 tools become available when you connect Alexa Smart Home to Google ADK via MCP:

adjust_brightness

Positive values increase brightness, negative values decrease it. Adjust the brightness of an Alexa-connected light relatively

deregister_alexa_device

This removes the device from your account but does not reset the device itself. Deregister an Alexa-connected device from your account

forget_alexa_device

The device will need to be re-discovered and set up again to be used with Alexa. Remove (forget) an Alexa-connected device from Alexa

get_alexa_device

Use endpoint ID from list_alexa_devices. Get detailed information for a specific Alexa-connected device

get_brightness_state

Use endpoint ID from list_alexa_devices. Get the current brightness level of an Alexa-connected light

get_power_state

Use endpoint ID from list_alexa_devices. Get the current power state of an Alexa-connected device

get_speaker_state

Use endpoint ID from list_alexa_devices. Get the current speaker volume state of an Alexa device

get_temperature_sensor

Use endpoint ID from list_alexa_devices. Get the current temperature reading from an Alexa-connected sensor

get_thermostat_state

Use endpoint ID from list_alexa_devices. Get the current state of an Alexa-connected thermostat

list_alexa_devices

Shows device names, manufacturers, models, features, and display categories. USE WHEN: - User wants to see all their Alexa-connected smart devices - User needs to find endpoint IDs for other commands - User is exploring their smart home setup - User asks "what Alexa devices do I have" PARAMETERS: - max_results (OPTIONAL): Number of results (1-50, default: 10) - next_token (OPTIONAL): Pagination token from previous response EXAMPLES: - "List all my Alexa devices" → call with no params - "Show my smart home devices" → call with no params - "What Alexa devices are connected?" → call with no params List all Alexa-connected smart home devices and endpoints

set_brightness

Use endpoint ID from list_alexa_devices. Set the brightness level of an Alexa-connected light

set_volume

Use endpoint ID from list_alexa_devices. Set the speaker volume of an Alexa device

turn_off_alexa_device

Works for lights, switches, plugs, and other power-controllable devices. Turn off an Alexa-connected device

turn_on_alexa_device

Works for lights, switches, plugs, and other power-controllable devices. Turn on an Alexa-connected device

update_alexa_device_name

Use endpoint ID from list_alexa_devices. Update the friendly name of an Alexa-connected device

update_device_room

Use endpoint ID from list_alexa_devices and unit ID from your Alexa Smart Properties account. Update the room/unit assignment for an Alexa-connected device

Example Prompts for Alexa Smart Home in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Alexa Smart Home immediately.

"List all my Alexa-connected smart home devices."

"Turn on the living room lamp and set brightness to 70%."

"What's the current temperature in the bedroom and what mode is the thermostat in?"

Troubleshooting Alexa Smart Home MCP Server with Google ADK

Common issues when connecting Alexa Smart Home to Google ADK through the Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Alexa Smart Home + Google ADK FAQ

Common questions about integrating Alexa Smart Home MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.