AWS quick documentation change
Summary
Comprehensive restructuring from 'Connections' to 'Connectors' documentation, adding new sections for MCP Servers and Coding Agents while updating web connector content
Security assessment
The changes introduce documentation for MCP server authentication (token-based) and environment variable configuration, which are security features. However, there's no evidence of addressing a specific vulnerability or security incident.
Diff
diff --git a/quick/latest/userguide/connections-desktop.md b/quick/latest/userguide/connections-desktop.md index b7d8cd178..d4e61ac69 100644 --- a//quick/latest/userguide/connections-desktop.md +++ b//quick/latest/userguide/connections-desktop.md @@ -7 +7 @@ -Available connectorsConnecting a serviceManaging connectionsActivity feed integration +Web ConnectorsMCP ServersCoding AgentsActivity feed integration @@ -9 +9 @@ Available connectorsConnecting a serviceManaging connectionsActivity feed integr -# Connections +# Connectors @@ -11 +11 @@ Available connectorsConnecting a serviceManaging connectionsActivity feed integr -Amazon Quick provides action connectors that link Quick to external services. When you connect a service such as Slack, Outlook, Jira, or Google Calendar, Quick can read from and write to that service during conversations and autonomous agent runs. +The **Connectors** tab in **Settings** > **Capabilities** lets you manage web connectors, MCP servers, and coding agents. You can search connectors by name, refresh the list, browse additional connectors, or create new ones using the **\+ Create** button. @@ -13 +13 @@ Amazon Quick provides action connectors that link Quick to external services. Wh -## Available connectors +## Web Connectors @@ -15 +15 @@ Amazon Quick provides action connectors that link Quick to external services. Wh -Amazon Quick provides built-in connections for services such as Slack, Microsoft Outlook, Microsoft Teams, Gmail, Google Calendar, Google Meet, Microsoft OneDrive, Microsoft SharePoint, Google Drive, Google Docs, Google Sheets, Google Slides, Dropbox, Google Analytics, Airtable, QuickBooks, Zoom, and Zapier. For a complete list of available integrations, see [Work with integrations in Amazon Quick](./working-with-integrations.html). +Web connectors link Quick to external services such as Slack, Microsoft Outlook, Jira, Google Calendar, and more. When you connect a service, Quick can read from and write to that service during conversations and agent runs. @@ -17 +17,3 @@ Amazon Quick provides built-in connections for services such as Slack, Microsoft -## Connecting a service +For integration-specific setup guides, see [Integration-specific guides](./integration-guides.html). + +### Connecting a service @@ -21 +23 @@ Amazon Quick provides built-in connections for services such as Slack, Microsoft - 2. Choose the **Connections** tab. + 2. On the **Connectors** tab, find the service under **Web Connectors**. @@ -23 +25 @@ Amazon Quick provides built-in connections for services such as Slack, Microsoft - 3. Find the service you want to connect and choose **Sign in** if it has been configured in the web experience. You can additionally toggle access and change granular permissions with the gear icon. + 3. Choose **Browse** to discover available connectors if none are listed. @@ -30 +32,175 @@ Amazon Quick provides built-in connections for services such as Slack, Microsoft -To browse and add connections beyond the built-in services, choose **Browse connections** at the bottom of the Connections tab. This opens Quick on the web, where you can discover additional integrations. Connections added on the web appear automatically in the desktop application. +To browse and add connectors beyond those listed, choose **Browse more**. Connectors added on the web appear automatically in the desktop application. + +## MCP Servers + +The Amazon Quick desktop application supports the Model Context Protocol (MCP), an open standard that extends the capabilities of Quick with custom tools and integrations. You can connect MCP servers to give Quick access to databases, internal APIs, developer tools, and other systems that are not available through built-in connectors. + +### What is MCP? + +Model Context Protocol (MCP) is a protocol that allows AI assistants to interact with external tools and data sources. When you connect an MCP server to Quick, the tools provided by that server become available in your chat conversations and scheduled tasks. For example, you can connect an MCP server that provides database query tools, and then ask Quick to query your database directly in chat. + +### Accessing MCP settings + +To manage your MCP servers, open **Settings** in the sidebar, choose **Capabilities** , and then choose the **Connectors** tab. MCP servers are listed in the **MCP Servers** section. + +You can add new servers by choosing **\+ Add MCP**. + +### Adding an MCP server + +When you choose **\+ Create** and then choose **MCP server** , a dialog appears with three connection types: **Local** , **Import** , and **Remote**. Choose the connection type that matches how your MCP server runs. + +#### Local + +Use the **Local** connection type to run an MCP server as a command on your machine. This is the most common option for development tools and locally installed servers. + +The following table describes the fields for a Local MCP connection. + +Field | Required | Description +---|---|--- +**Name** | Yes | A friendly name to identify this MCP server (for example, "My Database MCP"). +**Command** | Yes | The executable to run. Common values include `python`, `npx`, `node`, and `uvx`. +**Arguments** | No | Command line arguments, separated by spaces (for example, `-m mcp_server --port 8080`). +**Description** | No | A description of what this MCP server does and what tools it provides. This helps Quick understand when to use the server's tools. +**Environment variables** | No | Environment variables required by the server. Choose **\+ Add variable** to add key-value pairs. +**Timeout (seconds)** | No | Maximum time to wait for the server to start, from 5 to 300 seconds. The default is 30 seconds. + +###### To add a local MCP server + +Use the following procedure. + + 1. Open **Settings** in the sidebar and choose **Capabilities**. + + 2. Choose the **Connectors** tab. + + 3. In the **MCP Servers** section, choose **\+ Create** , and then choose **MCP server**. + + 4. Choose **Local** as the connection type. + + 5. Enter a **Name** and the **Command** to run (for example, `python`). + + 6. Enter any **Arguments** the command requires (for example, `-m my_mcp_server`). + + 7. Choose **Save**. + + + + +#### Import + +Use the **Import** connection type to load MCP server configurations from an existing configuration file. This is useful when you already have MCP servers configured for other tools and want to reuse that configuration in Quick. + +Quick supports configuration files from the following tools. + + * Kiro + + * Claude Code + + * AIM + + * Antigravity + + * QuickWork exports + + + + +The following table describes the fields for an Import MCP connection. + +Field | Required | Description +---|---|--- +**Config file path** | Yes | The path to the configuration file on your machine (for example, `~/.kiro/settings/mcp.json`). + +When you enter a configuration file path, Quick automatically scans the file and detects the MCP servers defined in it. Quick also detects tools installed on your system and displays them as chips (for example, "Kiro", "AIM", "Claude Code") under **Detected on this system**. + +###### To import MCP servers from a config file + +Use the following procedure. + + 1. Open **Settings** in the sidebar and choose **Capabilities**. + + 2. Choose the **Connectors** tab. + + 3. In the **MCP Servers** section, choose **\+ Create** , and then choose **MCP server**. + + 4. Choose **Import** as the connection type. + + 5. Enter the **Config file path** to your existing MCP configuration file. + + 6. Review the detected servers and system tools. + + 7. Choose **Load file** to import the servers. + + + + +#### Remote + +Use the **Remote** connection type to connect to an MCP server running on a remote machine or cloud service over HTTP. This is useful for shared team servers or hosted MCP services. + +The following table describes the fields for a Remote MCP connection. + +Field | Required | Description +---|---|--- +**Name** | Yes | A friendly name to identify this MCP server. +**URL** | Yes | The URL of the MCP endpoint (for example, `https://mcp.example.com/sse`). +**Token** | No | A bearer token for authentication with the remote server. +**Description** | No | A description of what this MCP server does and what tools it provides. +**Timeout (seconds)** | No | Maximum time to wait for the server to respond, from 5 to 300 seconds. The default is 30 seconds. + +###### To add a remote MCP server + +Use the following procedure. + + 1. Open **Settings** in the sidebar and choose **Capabilities**. + + 2. Choose the **Connectors** tab. + + 3. In the **MCP Servers** section, choose **\+ Create** , and then choose **MCP server**. + + 4. Choose **Remote** as the connection type. + + 5. Enter a **Name** and the **URL** of the MCP endpoint. + + 6. (Optional) Enter a **Token** if the server requires authentication. + + 7. Choose **Save**. + + + + +### Managing MCP servers + +After you add MCP servers, they appear in the MCP Servers section of the Connectors tab. You can manage your servers using the following features. + + * **Search** – Use the search bar to find servers by name. + + * **Filter** – Use the dropdown filter to show all servers or filter by status. + + * **Toggle** – Turn individual MCP servers on or off without removing them. + + * **Edit** – Modify server configuration. + + * **Remove** – Delete a server connection. + + + + +### Using MCP tools in scheduled tasks + +You can attach MCP servers to scheduled tasks as capabilities. When you create or edit a scheduled task, you can select which MCP servers the task has access to. This allows your automated tasks to use custom tools when they run. + +To attach MCP capabilities to a scheduled task, open **Mission Control** from the top bar, select the task, choose the **Capabilities** tab, and select the MCP servers you want to make available. + +###### Note + +MCP servers must be running and accessible when a scheduled task attempts to use their tools. For local MCP servers, the server process starts automatically when needed. For remote servers, verify that the server is online and reachable. + +## Coding Agents +