Alexa Smart Home MCP. Control every light, sensor, and speaker in your house.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Alexa Smart Home MCP Server connects your AI client to over 16 tools for managing all Alexa-connected devices. You can list every device, check current power or temperature states, and send immediate commands—like setting brightness levels via `set_brightness` or adjusting the volume with `set_volume`.
This server lets you run full smart home routines directly from your agent without needing multiple apps or complex automations.
What your AI agents can do
Adjust brightness
Changes the brightness of an Alexa light by a relative amount (positive or negative value).
Deregister alexa device
Removes a specific device from your account without affecting the physical device itself.
Forget alexa device
Completely removes (forgets) an Alexa-connected device, requiring it to be set up and rediscovered later.
Retrieves a full list of all connected Alexa devices, along with detailed information like model and manufacturer.
Turns specific devices (lights, plugs, switches) on or off using defined tools.
Reads current light brightness and sets new absolute or relative brightness levels for connected lamps.
Checks the mode, target temperature, and current ambient reading of thermostats and dedicated sensors.
Reads or sets the volume level on any Alexa-enabled speaker.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Alexa Smart Home: 16 Tools for Full Device Control
These tools let your agent read current states (brightness, temperature) and execute commands across all connected Alexa-enabled smart devices.
019d754badjust brightness
Changes the brightness of an Alexa light by a relative amount (positive or negative value).
019d754bderegister alexa device
Removes a specific device from your account without affecting the physical device itself.
019d754bforget alexa device
Completely removes (forgets) an Alexa-connected device, requiring it to be set up and rediscovered later.
019d754bget alexa device
Retrieves full technical details for a specific Alexa-connected endpoint ID.
019d754bget brightness state
Gets the current brightness level reading of an Alexa light.
019d754bget power state
Checks if a general power-controllable device (plug, switch) is currently on or off.
019d754bget speaker state
Reads the current volume level of an Alexa speaker.
019d754bget temperature sensor
Gets the precise, real-time temperature reading from a connected sensor endpoint ID.
019d754bget thermostat state
Retrieves the current operating mode and target temperature of an Alexa thermostat.
019d754blist alexa devices
Lists all connected smart home devices, providing names, manufacturers, and endpoint IDs for use in other commands.
019d754bset brightness
Sets the exact brightness level (percentage) for an Alexa light.
019d754bset volume
Adjusts the speaker volume on an Alexa device to a specific level.
019d754bturn off alexa device
Turns off any power-controllable smart device (lights, plugs, switches).
019d754bturn on alexa device
Turns on any power-controllable smart device.
019d754bupdate alexa device name
Changes the friendly name displayed for an Alexa-connected device.
019d754bupdate device room
Reassigns a connected device to a different room or unit within your smart home account.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Alexa Smart Home, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI client connects directly to your entire grid of Alexa-enabled gadgets using this MCP Server. It lets you run full smart home routines straight from your agent without needing multiple apps or complex automations. You can manage lights, climate control, speakers, and sensors across every connected endpoint.
Device Inventory & Setup: When you need to know what gear you've got hooked up, the list_alexa_devices tool pulls a complete manifest of everything: names, manufacturers, models, and unique endpoint IDs. If you run into an issue with a specific device, you can use get_alexa_device to fetch all its detailed technical specs.
For cleanup, if a gadget isn't working right, the forget_alexa_device tool completely wipes it from your account, forcing you to set it up and rediscover it later. If you just need to remove an entry without affecting the physical device, use deregister_alexa_device. You can also change how things show up by using update_alexa_device_name or reassigning a gadget to a different area with update_device_room.
Power and Lighting Control: This server gives you total control over power-controllable devices like lights, plugs, and switches. You can instantly turn any of these gadgets on with turn_on_alexa_device, or shut them down completely using turn_off_alexa_device. For lighting specifically, the system reads the current brightness level via get_brightness_state. You've got options for adjusting that light: you can set an exact percentage using set_brightness, or make a relative change—brightening it up or dimming it down by a specific amount—with adjust_brightness.
Climate and Sensor Management: Don't mess with the temperature. To check the ambient reading, call get_temperature_sensor to get the precise, real-time number from any dedicated sensor. For your main thermostat, you can fetch its current operating mode and target temp using get_thermostat_state. You also need to know if a general power plug or switch is actually on or off; that's what get_power_state checks for.
Audio Control: Need to adjust the volume? The server lets you read the current sound level with get_speaker_state, and then set it exactly where you want it using set_volume. This works on any Alexa-enabled speaker in your house.
When your agent uses these tools, it's talking directly to the smart home hardware via the Alexa Smart Properties API. You just give your AI client the token credentials and let it do the heavy lifting. It runs tool calls—like checking a temperature or setting brightness—that interact straight with your physical devices, handling all the complexity behind the scenes.
How Alexa Smart Home MCP Works
- 1 Subscribe to the server and obtain an OAuth 2.0 access token from Login with Amazon (LWA).
- 2 Connect your AI client (e.g., Claude or Cursor) using this token.
- 3 Your agent uses specific tool calls—like
get_temperature_sensor—to read data or execute commands against your connected devices.
The bottom line is: you give the connection credentials, and your AI client handles all the API communication to run device routines.
Who Is Alexa Smart Home MCP For?
Facility operations teams who manage buildings across multiple units. Property managers running portfolios of rental or hotel rooms. Home automation enthusiasts building complex, reliable routines. Anyone tired of switching between a climate app, a lighting app, and a speaker app just to adjust the mood.
Uses list_alexa_devices to verify which devices are installed in Unit 302. Then uses set_brightness to dim all lights across a floor after hours.
Monitors HVAC status using get_thermostat_state and adjusts the unit's target temperature via agent commands to meet building energy goals.
Builds complex, multi-step routines that check sensor data (get_temperature_sensor) before running a sequence of actions like turn_on_alexa_device and set_volume.
What Changes When You Connect
- Full Device Visibility: Use
list_alexa_devicesto pull a complete manifest of everything connected. You don't have to guess what devices are available; the agent shows you all endpoints first. - Granular Climate Control: Don't just turn things on. With
get_thermostat_state, your AI client reads the mode and target temperature, letting you run complex routines that verify HVAC status before making adjustments. - Precision Lighting: Forget simple ON/OFF switches. You can use
set_brightnessfor specific percentages oradjust_brightnessto dim lights gradually in a scene setup. This gives you true ambiance control. - Automated Maintenance: If a device is moved or decommissioned, use
update_device_roomto keep your physical location records accurate. You can also re-index old devices usingforget_alexa_devicewhen they're sold. - Single Control Point: Instead of running 5 different apps for the house (lights, HVAC, sound), you tell your agent one thing, and it handles the sequence: check state -> actuate device -> confirm success.
Real-World Use Cases
Pre-Departure Scene Setting
The user leaves for vacation. They ask their agent to 'Set the house to away mode.' The agent first calls get_power_state on all devices, then uses turn_off_alexa_device sequentially for every controllable item and finally reports back that the entire property is secured.
Optimizing Office Climate
An engineer needs to ensure a conference room is ready. They ask their agent, 'What's the temp and what should it be?' The agent calls get_temperature_sensor for real data, compares it with get_thermostat_state, and if the difference is over 2 degrees, it uses an action tool to adjust the target temperature.
Multi-Zone Lighting Scene
The user wants to watch a movie. They tell their agent this request. The agent then calls set_brightness for the living room lamps (e.g., 30%), calls turn_on_alexa_device for accent lights, and ensures the main speakers are active with set_volume.
Device Auditing
A property manager suspects a device is mislabeled. They ask their agent to 'List all devices in unit 4B.' The agent runs list_alexa_devices, which provides the full list and endpoints, allowing the manager to then use update_alexa_device_name to correct it.
The Tradeoffs
Treating state retrieval as optional
The agent just turns off the main lights without checking if they're actually on first. It wastes tokens and doesn't confirm success.
→
Always check the state first. Before running turn_off_alexa_device, run get_power_state to verify the device is active. This confirms both status and prevents unnecessary API calls.
Confusing relative vs absolute brightness
The user asks to 'dim the lights a bit,' but the agent uses an absolute setting, making them too dark.
→
Use adjust_brightness for small changes ('dim it by 20'). Use set_brightness only when you know the exact target percentage (e.g., 'set to 50%').
Overlooking device location updates
The client moves a smart plug from the kitchen to the laundry room, but doesn't update its records.
→
After moving or installing a device, use update_device_room immediately. This keeps your local record consistent with the physical world.
When It Fits, When It Doesn't
Use this server if your automation routines require reading and writing multiple types of live sensor data (temperature, brightness) and controlling multiple disparate device functions (lights, HVAC, audio). The core strength is coordination. Don't use it if you are only polling a single type of simple metric—for instance, just checking the outdoor temperature might be better handled by a dedicated weather API. Similarly, don't use it if your entire need is to manage user credentials or accounts; for that, you need an identity management tool. You must use this server when you need a sequence: check get_thermostat_state -> If target > current temp, then run turn_on_alexa_device on the HVAC unit.
If your goal is simply to create a list of devices for documentation purposes, list_alexa_devices handles that. But if you are building an operational routine—like 'When temperature drops below 20C, and it's after sunset, turn on the heater and dim the lights'—this collection of tools is what makes the sequence possible.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Alexa Smart Home. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 16 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Managing multiple apps to control your home is a nightmare.
Right now, if you want to set a scene, you open the climate app for the thermostat. Then you switch over to the lighting app to dim the bulbs. You might check the speaker volume in a third app, and then maybe use your phone's general control panel just to turn off the porch light. This is tedious, requires context switching, and fails when one app goes down.
With this MCP server, your agent handles it all from one chat window. The AI client executes `get_thermostat_state` first, then calls `set_brightness` on the lights, and finally adjusts the audio using `set_volume`. You just get the result: 'Scene set.' No app switching required.
Alexa Smart Home MCP Server: Control devices with specific tools.
Manual routines require you to remember that a simple on/off action needs `turn_on_alexa_device`, but changing the color needs a separate, specialized tool. You have to manage which endpoint ID belongs to which function manually every single time.
The agent handles the mapping. It knows that 'dimming' means running `set_brightness` and it grabs the correct device ID for you automatically. The complexity stays hidden; you just give the command.
Common Questions About Alexa Smart Home MCP
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 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.
How do I get the necessary endpoint ID before I can use `set_brightness` or `turn_on_alexa_device`? +
You must call the list_alexa_devices tool first. This function returns a comprehensive list of all connected devices, and each device entry provides the specific endpoint ID you need for any subsequent control action.
When I use the `adjust_brightness` tool, does the value I send represent an absolute or relative change? +
The adjust_brightness tool accepts relative changes. Sending a positive number increases the device's current brightness level by that percentage, and sending a negative number decreases it.
If I run `get_temperature_sensor`, is the reading real-time, or is there a delay? +
The get_temperature_sensor tool reads the current available state reported by the Alexa API. While it provides near real-time data, actual latency depends on the device's internal reporting interval and network conditions.
What exactly does the `turn_on_alexa_device` tool control—is it just the main power switch, or does it manage lights too? +
The turn_on_alexa_device tool controls the device's primary physical power state. It works for switches and plugs; if you need to specifically adjust light levels after turning it on, use the set_brightness tool.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
PDFMonkey
Generate dynamic PDF documents from JSON data and HTML templates with an API built for high-volume document automation.
Nubank MX
Manage your Nubank Mexico banking from any AI agent — check balances, review transactions, send SPEI transfers, pay bills, and track spending analytics.
Telekom Malaysia (TM) OIP
Orchestrate Telekom Malaysia (TM) services — manage broadband plans, service orders, and network usage directly from any AI agent.
You might also like
Scytale (Security Compliance Automation)
Automate security compliance via Scytale — manage evidence, track security controls, and monitor framework status directly from your AI agent.
MessageFlow
Omnichannel communication via MessageFlow — send SMS, WhatsApp, and Email messages.
The Movie Database (TMDb)
Search movies, TV shows, people, get details, cast, trailers, and discover content via TMDb API.
