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 CrewAI 16 tools — connect in under 2 minutes

Name: Alexa Smart Home
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 16 Tools Framework

Connect your CrewAI agents to Alexa Smart Home through the Vinkius — pass the Edge URL in the `mcps` parameter and every Alexa Smart Home tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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 crewai import Agent, Task, Crew

agent = Agent(
    role="Alexa Smart Home Specialist",
    goal="Help users interact with Alexa Smart Home effectively",
    backstory=(
        "You are an expert at leveraging Alexa Smart Home tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Alexa Smart Home "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Alexa Smart Home becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Alexa Smart Home tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the Alexa Smart Home MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 16 tools from Alexa Smart Home

Why Use CrewAI with the Alexa Smart Home MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Alexa Smart Home through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Alexa Smart Home + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Alexa Smart Home for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Alexa Smart Home, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Alexa Smart Home tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Alexa Smart Home against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Alexa Smart Home MCP Tools for CrewAI (16)

These 16 tools become available when you connect Alexa Smart Home to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Alexa Smart Home + CrewAI FAQ

Common questions about integrating Alexa Smart Home MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.