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

Name: Alexa Smart Home
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 16 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Alexa Smart Home and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "alexa-smart-home": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

Claude Desktop is the definitive way to connect Alexa Smart Home to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 16 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

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

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Alexa Smart Home

Look for the 🔌 icon in the chat — your 16 tools are now available

Why Use Claude Desktop with the Alexa Smart Home MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Alexa Smart Home through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Alexa Smart Home + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Alexa Smart Home MCP Tools for Claude Desktop (16)

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

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

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

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Alexa Smart Home + Claude Desktop FAQ

Common questions about integrating Alexa Smart Home MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.