Skip to main content
Glama
serversmx

alexa-mcp

by serversmx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to alexa-mcp

No user-submitted related servers found.

    Related Servers

    • alexa-mcp

      James-Tucke-r
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-compatible LLMs to control Amazon Alexa devices by sending announcements, text commands, and SSML speech, as well as managing smart-home groups, routines, lists, volume, Do Not Disturb, and sensor queries.
      19
      MIT

    • ha-mcp

      osrd-gh
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      MIT
    • Home Assistant MCP Server by homeassistant-ai

      Home Assistant MCP Serverofficial

      homeassistant-ai
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      77
      31,054 PyPI
      4,916
      MIT

    • alexa-mcp

      GraysonCAdams
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables users to manage their Amazon Alexa shopping lists directly from MCP clients like Claude. It provides tools for listing, adding, updating, and deleting shopping list items through secure Amazon account authentication.
      7
      MIT

    • ha-mcp

      qubit999
      A
      license
      A
      quality
      C
      maintenance
      A self-hosted MCP server for Home Assistant that exposes full control over entity states, service calls, history, templates, and areas via local stdio, enabling AI assistants to manage your smart home.
      9
      64 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Every tool targets a distinct action and resource. The 'list_' tools are clearly differentiated by object (devices vs groups vs lists vs routines vs smarthome_devices), and all other tools have unique purposes (announce vs speak_ssml vs text_command, etc.), leaving no ambiguity.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'alexa_verb_noun' in snake_case. Verbs are descriptive (add, get, list, create, delete, set, etc.) and multi-word verbs are hyphenated appropriately (do_not_disturb, text_command). No mixing of conventions.

    Tool Count5/5

    18 tools is well-scoped for a server covering voice announcements, smart home control, list management, routines, and device configuration. Each tool serves a necessary function without redundancy, fitting the typical 3-15 range slightly above but still reasonable.

    Completeness4/5

    The tool surface covers the main Alexa domains: CRUD for lists (add/get but missing delete/update), groups (full CRUD), devices (list, query, volume), routines (list/execute but no create/edit/delete), and voice actions (announce, SSML, text command). Minor gaps like list item deletion exist, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources