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

Name: Alexa Smart Home
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 16 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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": {
      "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.

Cursor's Agent mode turns Alexa Smart Home into an in-editor superpower. Ask Cursor to generate code using live data from Alexa Smart Home and it fetches, processes, and writes — all in a single agentic loop. 16 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Alexa Smart Home

Open Agent mode in chat and ask: "Using Alexa Smart Home, help me..." — 16 tools available

Why Use Cursor with the Alexa Smart Home MCP Server

Cursor AI Code Editor provides unique advantages when paired with Alexa Smart Home through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Alexa Smart Home + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Alexa Smart Home MCP Tools for Cursor (16)

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

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

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Alexa Smart Home + Cursor FAQ

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

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.