Amazon Q Developer CLI

What is Amazon Q Developer CLI?

Amazon Q Developer CLI is a command-line interface that integrates Amazon Q with MCP (Model Context Protocol) servers, enabling users to query AWS documentation, analyze costs, and perform other tasks directly from the terminal. It is intended for developers and AWS practitioners who want to augment Amazon Q with custom tools and context.

How to use Amazon Q Developer CLI?

Install Amazon Q Developer CLI, configure an mcp.json file (globally at ~/.aws/amazonq/mcp.json or per workspace at .amazonq/mcp.json), and add MCP server entries using uvx commands. Use the /tools command to view available tools and /tools trust <tools> to auto‑approve them.

Key features of Amazon Q Developer CLI

• Configures MCP servers via structured JSON configuration file.
• Supports global and workspace‑specific MCP settings.
• Runs MCP servers using uvx and Python 3.10+.
• Lists and manages tools with /tools and /tools trust.
• Integrates with AWS Documentation and Cost Analysis MCP servers.

Use cases of Amazon Q Developer CLI

• Query AWS documentation (e.g., S3 bucket naming rules) and cite sources.
• Retrieve cost analysis information for a specific AWS profile.
• Manage on‑premises servers as hybrid nodes using documentation lookups.
• Consolidate conversation context with /compact to free up space.

FAQ from Amazon Q Developer CLI

What are the installation prerequisites?

You need Amazon Q Developer CLI, uv from Astral, and Python 3.10 or higher (installable via uv python install 3.10).

Where should I place the MCP configuration file?

Either globally at ~/.aws/amazonq/mcp.json (applies to all workspaces) or at .amazonq/mcp.json in the current workspace (applies to that workspace only).

Does Amazon Q Developer CLI work with Docker?

The README notes that Docker support was not achieved; Docker usage is not confirmed to work.

How do I see which tools are configured?

Use the /tools command in Amazon Q Developer CLI to list configured and available tools.

How can I avoid constant approval prompts for tools?

Use /tools trust <tools> to trust specific tools so they run without manual confirmation.