Alexa For BusinessMCP Configuration & Schema Registry
The Alexa For Business Model Context Protocol (MCP) configuration provides a validated, machine-readable JSON schema and executable bridge that connects state-of-the-art AI coding assistants — including Claude Desktop, Cursor IDE, Windsurf, Cline, and VS Code Copilot — directly to the Alexa For Business REST API. By leveraging the standardized open Model Context Protocol, AI agents can dynamically discover capabilities, validate input parameters against strict JSON Schemas, and execute live API operations without context switching or manual copy-pasting.
Quick Specs & Integration Summary
Technical Architecture & Protocol Semantics
Under the Model Context Protocol specification, the Alexa For Business configuration functions as an isolated protocol adapter. When an AI agent initializes a session, the client establishes a bidirectional JSON-RPC 2.0 communication channel over standard input/output (stdio) or Server-Sent Events (SSE). During the initial handshake, the server publishes its tool manifest extracted from the Alexa For Business OpenAPI specification (version 2017-11-09).
Alexa for Business is a comprehensive cloud-based service provided by Amazon Web Services (AWS) that enables organizations to deploy and manage Alexa-enabled devices at scale within their professional environments. It extends the voice-based capabilities of consumer Alexa devices into the enterprise realm, providing administrators with a centralized platform to manage thousands of devices, enroll employees as users, and assign custom or third-party skills tailored to business workflows. The API serves as the programmatic backbone for this service, allowing developers to automate the configuration, management, and monitoring of an organization's Alexa ecosystem. Typical use cases include streamlining conference room bookings, automating office environment controls like lighting and thermostats, providing hands-free access to corporate knowledge bases, and creating custom voice-driven interfaces for specific business applications like sales dashboards or IT ticketing systems. Exposing the Alexa for Business API as a set of tools via the Model Context Protocol (MCP) presents significant value for AI coding assistants like Claude Desktop or Cursor. In this paradigm, the AI agent gains the ability to directly interact with and manipulate an organization's voice-enabled infrastructure through natural language commands. This transforms the assistant from a passive code generator into an active operational participant. For example, a developer could instruct the AI to "list all network profiles assigned to conference rooms in the London office" or "create a new address book for the marketing department and add these five contacts." The AI could then execute the appropriate API calls (`ListNetworkProfiles`, `CreateAddressBook`, `AddContacts`) based on the conversational context, drastically reducing the manual effort and specialized knowledge required to perform administrative tasks, thus accelerating development and deployment cycles for voice-integrated solutions. Dynamic, AI-driven workflows become possible when this API is toolified. A developer could instruct the AI agent: "Scan our inventory of devices and automatically associate any new Echo Show 15 models with the 'Sales_Kiosk' room and the 'Corporate_WiFi' network profile." The agent would invoke `SearchDevices`, filter the results, and then execute a sequence of `AssociateDeviceWithRoom` and `AssociateDeviceWithNetworkProfile` calls. Another example: "Analyze last week's conference room usage reports and create a new `BusinessReportSchedule` to email a summary to facilities every Monday at 9 AM." Here, the AI would use `GetBusinessReportSchedule` for context, then `CreateBusinessReportSchedule` to automate future reporting. It could also handle onboarding: "Enroll these five new hires as users, assign them to the 'Engineering' skill group, and grant them access to the 'Office_Info' skill," executing `CreateUser`, `AssociateSkillGroupWithUsers`, and `AssociateSkillWithUsers` in a coordinated workflow. Secure integration is paramount. While the API itself uses AWS IAM for authentication, the configuration of the MCP server must meticulously protect the credentials. Developers must create a dedicated IAM role with the principle of least privilege, granting only the specific Alexa for Business permissions required for the intended tasks (e.g., read-only access for monitoring versus full admin rights for setup). The access keys for this IAM user should be stored securely, ideally in a secrets manager or environment variables, and never hardcoded. The MCP server endpoint should enforce HTTPS and be configured to accept requests only from authorized clients. Network-level controls, such as VPC endpoints or firewall rules, should restrict access to the AWS API endpoints. Regular auditing of API call logs via AWS CloudTrail is essential to monitor for unexpected or malicious activity, ensuring the powerful automation capabilities are governed by robust security practices. This architecture guarantees strict process boundary isolation: all sensitive authorization headers and secret tokens remain sandboxed inside the client runtime, never leaking into language model context windows or external logging endpoints.
Hosted Remote Configuration URL
MCP Configuration FileProvide this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/amazonaws-com-alexaforbusiness.json2. AI Assistant Use Cases & Practical Workflows
Tailored for CommunicationReal-world execution scenarios demonstrating how LLM agents (Claude 3.7, GPT-4o, Cursor Agent) invoke Alexa For Business tools to automate developer workflows.
1. Automated Incident Escalation & Notification Routing
Incident CommsBroadcast priority notifications with rich incident context, system health metrics, and on-call engineer assignment details.
"Dispatch a high-priority incident notification via Alexa For Business containing the latest stack trace, affected microservice names, and link to the active monitoring dashboard."
2. Knowledge Base & Workspace Documentation Sync
Knowledge SyncSynchronize newly merged pull request documentation and architectural decision records into searchable workspace hubs.
"Fetch updated technical notes from our repository and sync them into Alexa For Business. Ensure headers, code blocks, and parameter tables are correctly formatted in markdown."
3. Omnichannel Customer Ticket Triaging & Sentiment Analysis
Support AutomationClassify incoming customer inquiry tickets, detect customer sentiment urgency, and auto-draft contextual solution proposals.
"Retrieve open customer support tickets from Alexa For Business. Classify urgency based on customer sentiment and generate drafted reply outlines for Tier-2 engineering review."
4. Scheduled Webhook Dispatch & Event Orchestration
Event OrchestrationAutomate event notification triggers when deployments complete, staging builds pass, or schema changes are detected.
"Configure an event notification hook in Alexa For Business to trigger Slack updates whenever a high-severity deployment event is logged in staging."
End-to-End Multi-Step Agent Execution Lifecycle
When an engineer submits a task to Claude Desktop or Cursor, the LLM executes an autonomous 4-phase Model Context Protocol loop:
Schema Introspection
Handshake lists all 10 tools and builds argument validators.
Argument Synthesis
Model extracts parameters from prompt and validates types against OpenAPI rules.
Stdio Execution
Bridge invokes live API with injected local credentials and captures raw HTTP response.
Output Remediation
LLM parses JSON results, handles status codes, and presents synthesized answers.
3. Multi-Client Installation Matrix & Setup Guides
Select your AI assistant below to view exact configuration file paths, JSON installation snippets, and launch commands.
Claude Desktop
claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": {
"amazonaws-com-alexaforbusiness": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"
],
"env": {
"ALEXA_FOR_BUSINESS_API_KEY": "your_alexa_for_business_api_key"
}
}
}
}Cursor IDE
.cursor/mcp.jsonOpen Cursor Settings → Features → MCP Servers, or create .cursor/mcp.json in your project root.
{
"mcpServers": {
"amazonaws-com-alexaforbusiness": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"
],
"env": {
"ALEXA_FOR_BUSINESS_API_KEY": "your_alexa_for_business_api_key"
}
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline Extension
cline_mcp_settings.jsonPaste into your Cline extension MCP configuration or Roo Code host settings.
{
"mcpServers": {
"amazonaws-com-alexaforbusiness": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"
],
"env": {
"ALEXA_FOR_BUSINESS_API_KEY": "your_alexa_for_business_api_key"
}
}
}
}Zed Editor & Docker CLI
Zed / DockerDocker container execution command:
docker run -i --rm -e ALEXA_FOR_BUSINESS_API_KEY="YOUR_SECRET_VALUE" node:20-alpine npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json
Zed settings context servers JSON:
{
"context_servers": {
"amazonaws-com-alexaforbusiness": {
"command": {
"path": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"
],
"env": {
"ALEXA_FOR_BUSINESS_API_KEY": "your_alexa_for_business_api_key"
}
}
}
}
}Programmatic SDK Integration (TypeScript / Python)
Initialize the Alexa For Business MCP client directly in your backend codebase.
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
// Initialize Alexa For Business MCP client transport over stdio
const transport = new StdioClientTransport({
command: "npx",
args: ["-y","@modelcontextprotocol/server-openapi","https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"],
env: { ALEXA_FOR_BUSINESS_API_KEY: process.env.ALEXA_FOR_BUSINESS_API_KEY || "YOUR_SECRET_KEY" }
});
const client = new Client(
{ name: "amazonaws-com-alexaforbusiness-client", version: "1.0.0" },
{ capabilities: { tools: {}, resources: {}, prompts: {} } }
);
async function connectAndRun() {
await client.connect(transport);
const tools = await client.listTools();
console.log("Connected to Alexa For Business MCP Server.");
console.log("Discovered 10 mapped tools:", tools);
}
connectAndRun().catch(console.error);Raw Stdio Schema Definition
schema.jsonFor standalone CLI wrappers, background daemon daemons, or custom script integrations:
{
"mcpServers": {
"amazonaws-com-alexaforbusiness": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json"
],
"env": {
"ALEXA_FOR_BUSINESS_API_KEY": "your_alexa_for_business_api_key"
}
}
}
}4. Security, Authentication & Credential Management
Safely configure authentication tokens, isolate execution environments, and implement enterprise security best practices.
Required Environment Keys Reference
| Variable Name | Required | Type | Default | Purpose & Guidance |
|---|---|---|---|---|
| ALEXA_FOR_BUSINESS_API_KEY | REQUIRED | Secret Key / Token | None (Set in env) | your_alexa_for_business_api_key |
Zero-Downtime Token Rotation Protocol
- Generate Secondary Key: Create a new secret API token with identical scopes in your Alexa For Business developer portal.
- Update Client Configuration: Insert the new token inside the
envblock of your MCP client JSON config. - Validate Connection: Issue a test query in Claude or Cursor to ensure handshake and tool calls succeed.
- Revoke Stale Token: Decommission the legacy key on the vendor portal to prevent unauthorized access.
Least-Privilege & Sandboxing Rules
- Read-Only Token Scoping: Whenever your workflow only requires querying data, provision read-only credentials to prevent accidental mutations.
- Local Process Isolation: Stdio transports run in isolated local subprocesses; secret credentials are never sent across the internet to MCP Bridge servers.
- Prompt Injection Defense: AI model responses are sandboxed; verify generated destructive arguments before confirming execution in agent mode.
Enterprise Security Checklist (Mandatory Practices)
- Never commit
claude_desktop_config.jsonor.cursor/mcp.jsoncontaining raw secrets into public GitHub repositories. - Add
.cursor/mcp.jsonand.env.localto your project's.gitignorefile. - Always enforce TLS/HTTPS encryption on outbound network requests initiated by the server process.
5. Tool Parameter Schemas & Natural Language Execution
Mapped OpenAPI operations converted into discrete Model Context Protocol tools with strict JSON-RPC payload validators.
/#X-Amz-Target=AlexaForBusiness.ApproveSkillApproveSkill
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_ApproveSkill",
"arguments": {}
}
}"Use Alexa For Business to execute ApproveSkill and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateContactWithAddressBookAssociateContactWithAddressBook
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateContactWithAddressBook",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateContactWithAddressBook and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateDeviceWithNetworkProfileAssociateDeviceWithNetworkProfile
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateDeviceWithNetworkProfile",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateDeviceWithNetworkProfile and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateDeviceWithRoomAssociateDeviceWithRoom
{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateDeviceWithRoom",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateDeviceWithRoom and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateSkillGroupWithRoomAssociateSkillGroupWithRoom
{
"jsonrpc": "2.0",
"id": 5,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateSkillGroupWithRoom",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateSkillGroupWithRoom and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateSkillWithSkillGroupAssociateSkillWithSkillGroup
{
"jsonrpc": "2.0",
"id": 6,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateSkillWithSkillGroup",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateSkillWithSkillGroup and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.AssociateSkillWithUsersAssociateSkillWithUsers
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_AssociateSkillWithUsers",
"arguments": {}
}
}"Use Alexa For Business to execute AssociateSkillWithUsers and output the formatted result."
/#X-Amz-Target=AlexaForBusiness.CreateAddressBookCreateAddressBook
{
"jsonrpc": "2.0",
"id": 8,
"method": "tools/call",
"params": {
"name": "amazonaws-com-alexaforbusiness_post_X_Amz_Target_AlexaForBusiness_CreateAddressBook",
"arguments": {}
}
}"Use Alexa For Business to execute CreateAddressBook and output the formatted result."
6. Interactive Troubleshooting & FAQ Accordion
Diagnose and resolve common JSON-RPC protocol error codes, connection disconnects, and schema refresh issues.
A 401 Unauthorized response indicates that the upstream Alexa For Business API rejected the authentication credential supplied in your MCP client's environment configuration. To resolve this: (1) Verify that your secret token is defined inside the "env" block of claude_desktop_config.json or .cursor/mcp.json rather than hardcoded in the command string. (2) Check whether Alexa For Business requires a prefix such as "Bearer <token>" in the authorization header. (3) Confirm that your API key has not expired and has been granted sufficient least-privilege scopes on the Alexa For Business developer dashboard.
If your MCP client fails to initialize tools for Alexa For Business: (1) Test the bridge launcher command ("npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json") directly inside your terminal or shell to inspect stdout/stderr diagnostic traces. (2) Verify network connectivity to the schema source (https://api.apis.guru/v2/specs/amazonaws.com/alexaforbusiness/2017-11-09/openapi.json). (3) Ensure Node.js (v18+) is installed and accessible in your system PATH. (4) For authenticated APIs, confirm credentials are configured in your client's "env" mapping rather than command arguments.
MCP clients like Claude Desktop and Cursor query the server's tools list ("tools/list") during startup and cache the resulting JSON Schema for the duration of the application session. If new endpoints or parameters are added to Alexa For Business: (1) Fully quit and restart Claude Desktop (Cmd+Q on macOS or File > Exit on Windows). (2) In Cursor IDE, navigate to Settings > Features > MCP Servers, toggle the Alexa For Business server off and on, or click the refresh icon to re-execute the initialization handshake.
If the AI model hallucinates parameters or fails to invoke a tool automatically: (1) Add explicit system instructions in your project's .cursorrules or Claude project prompt (e.g., "When querying Communication, always invoke the amazonaws-com-alexaforbusiness MCP server tools first"). (2) Ensure parameter types match schema specifications (e.g., passing integers as numbers rather than strings). (3) Check that required parameters marked in Section 5 are not omitted from the model's generated payload.
When the Alexa For Business upstream endpoint returns an HTTP 429 Too Many Requests response, the MCP server bubbles the structured error payload back to the AI client over stdio. Modern LLMs like Claude 3.7 and Cursor Agent recognize rate-limiting status codes, inspect the "Retry-After" header if present, and will automatically introduce backoff delays or ask the user before retrying the operation.
The Hosted Config URL (https://mcpbridge.org/config/amazonaws-com-alexaforbusiness.json) provides a static, remote JSON schema definition that cloud-native MCP clients can fetch over HTTPS for dynamic discovery. In contrast, local stdio configurations execute a local subprocess on your workstation. Local stdio processes offer maximum security because secret API keys remain strictly on your local machine and never transit third-party proxy servers.
Similar Communication Configurations
Explore related API bridges with ready-to-use Model Context Protocol schemas.
Slack API
CommunicationSend messages, manage channels, and integrate Slack notifications into your AI agent workflows.
https://mcpbridge.org/config/slack.jsonDiscord API
CommunicationSend messages, manage servers, and integrate Discord bots into your AI agent workflows.
https://mcpbridge.org/config/discord.jsonTwilio API
CommunicationSend SMS, make calls, and manage communication channels through your AI agent.
https://mcpbridge.org/config/twilio.jsonEmail Activity (beta)
CommunicationThe Email Activity (beta) API, provided by [Your Email Service Provider], is a specialized suite of endpoints designed to grant programmatic access to granular email event data and system security configurations. Its core capability revolves around detailed filtering and search across two primary domains: user engagement events (like opens, clicks, and bounces) and security/access control settings. While the event data functionality is limited to a recent two-day window by default, it serves as a powerful tool for real-time monitoring and immediate post-campaign analysis. Typical use cases for enterprise teams include building internal dashboards for marketing performance, automating alerts for campaign anomalies (e.g., a sudden spike in bounces), and developing custom reporting pipelines that feed into business intelligence systems. The associated security endpoints—managing an access whitelist and configuring alert notifications—provide critical administrative control, allowing teams to programmatically define which IP addresses or systems can interact with their email infrastructure and to set up proactive monitoring for potential security or deliverability issues. When exposed as tools to an AI coding assistant via the Model Context Protocol (MCP), the value of the Email Activity API shifts from simple data retrieval to enabling intelligent, context-aware automation and synthesis. An AI agent, such as Claude Desktop or an IDE-integrated assistant, can leverage these endpoints not just to fetch data, but to perform complex reasoning on the results. For instance, instead of a developer manually querying for all "bounce" events, they can instruct the AI to "analyze the last 24 hours of bounce data, group them by recipient domain, and draft an alert for the ops team if the failure rate for our primary domain exceeds 1%." The AI can dynamically combine data from the activity endpoint with the current security whitelist via the `/access_settings/whitelist` endpoint to audit configurations, generating suggestions like "I noticed the marketing automation server's IP is not whitelisted, which may be causing the recent campaign sends to fail. Should I add it?" Practical workflow examples showcase the transformative potential of this integration. A developer can instruct the AI agent to perform dynamic tasks such as: "Query the `/alerts` endpoint, review the current conditions for our 'high bounce rate' alert, and suggest a more sensitive threshold based on the bounce data from the last hour, then propose the corresponding API call to update it." Alternatively, an agent could be tasked to "Audit our security posture by fetching the current whitelist, cross-reference it with recent access logs (if available through a separate log endpoint), and flag any IP addresses that have made numerous requests but are not currently whitelisted, recommending whether to create a new whitelist rule." This allows the AI to act as an operational analyst, continuously monitoring system state and suggesting or implementing administrative actions based on real-time data streams. Critical implementation considerations begin with the "None" authentication method indicated for this beta API, which is a significant security red flag. Developers must assume this is a placeholder or error and seek alternative, robust authentication (like OAuth 2.0 or API key via a secure header) as soon as the API matures. Until then, any integration must treat the endpoints as highly sensitive and be restricted to non-production, sandboxed environments only. When setting up the MCP server, adherence to the principle of least privilege is paramount: the API keys or tokens used should be scoped exclusively to the narrow set of email activity and security endpoints required for the specific workflow, with no unnecessary read/write permissions. Configuration should ensure all API calls are made over TLS, and any locally cached email event data must be treated as confidential, encrypted at rest and in transit to prevent exposure of sensitive user engagement information. Developers must also build in robust error handling for rate limits and the inherent instability of beta endpoints, designing their AI-driven workflows to gracefully manage changes in the API schema without failure.
https://mcpbridge.org/config/sendgrid-com.json