What problem does it solve? Setting up the AWS DevOps Agent MCP connection involves choosing between Bearer token and SigV4 authentication, verifying credentials against the live endpoint, and writing the correct .mcp.json entry — a process prone to misconfiguration and silent failures. ## Core Features & Use Cases - Guided Setup: Detects existing aws-devops-agent configuration across plugin, project, and user-level MCP config files, then walks through diagnostics, auth selection, verification, and config writing. - Dual Auth Support: Configures either Bearer token authentication (single agent space) or SigV4 via mcp-proxy-for-aws-cli (multiple agent spaces and admin tooling), with live connectivity verification before writing config. - Diagnostics & Troubleshooting: Maps HTTP errors and AWS exceptions (401, 403, ExpiredTokenException, AccessDeniedException) to concrete fixes, plus multi-space routing setup for SigV4 users. - Use Case: A developer installs the DevOps Agent plugin but sees no tools available. This Skill checks their environment variables and AWS credentials, verifies the endpoint, writes the correct .mcp.json entry, and tells them to reload plugins. ## Quick Start Ask the assistant to set up the DevOps Agent MCP connection and follow the prompts to choose Bearer token or SigV4 authentication.