AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured procedure to configure, verify, and troubleshoot the AWS DevOps Agent MCP server connection within Claude. It guides users through selecting between Bearer Token and SigV4 authentication methods, performs connectivity diagnostics, and manages the necessary configuration files to ensure the agent is correctly integrated.
What it does
- Detects existing AWS DevOps Agent MCP configurations and connection status.
- Diagnoses authentication readiness for both Bearer Token and SigV4 methods.
- Verifies connectivity to the AWS DevOps Agent endpoint before applying changes.
- Generates and writes the appropriate .mcp.json configuration based on user choice.
- Provides guidance for multi-space routing when using SigV4 authentication.
- Offers troubleshooting steps for common connection and permission errors.
When to use it
- When the AWS DevOps Agent is missing from the MCP configuration.
- When the existing agent connection is broken or failing.
- When a user explicitly requests to set up or configure the DevOps agent.
- When switching between Bearer Token and SigV4 authentication methods.
Advantages
- Ensures valid credentials and connectivity before modifying configuration files.
- Provides clear decision paths for different authentication requirements.
- Automates the creation of complex MCP server configuration blocks.
- Includes built-in diagnostic checks to identify missing dependencies or permissions.
Usage examples
- “set up devops agent”
- The agent initiates the diagnostic workflow, checks for existing configurations, and prompts the user to choose between Bearer Token or SigV4 authentication.
- “configure agent”
- The agent verifies current environment variables and AWS credentials, then guides the user through the setup process for the selected authentication method.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/aws/setup-devops-agent/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip setup-devops-agent.zip -d .agents/skills
Documentation by AWS
AWS DevOps Agent — Claude Setup
The instructions below are specifically for setting up the AWS DevOps Agent plugin for Claude applications. For other clients, use this as a reference, but adjust the instructions based on the client's specific requirements.
Step 0: Check if setup is needed
1/ Check if the "aws-devops-agent" MCP server is running. If it is, verify that it has a valid connection (see "Step 3: Verify connectivity").
If verification is successful, you should inform the user that the plugin is already setup using SigV4 or Bearer Token. Offer that you can switch the configuration to Bearer Token or SigV4, see "Step 2: Decide auth path" below for details.
If the user does not want to change their auth configuration, then you are DONE STOP HERE.
2/ Check for an MCP server config with a key "aws-devops-agent" in the following locations:
Plugin scoped:
${CLAUDE_PLUGIN_ROOT}/.mcp.jsonProject-scoped: .mcp.json (in your project directory, version-controlled)
Project-specific: .claude/settings.local.json (in your project directory)
User-specific local: ~/.claude/settings.local.json
User-specific global: ~/.claude/settings.json
Main Claude.json: ~/.claude.json
Dedicated MCP file: ~/.claude/mcp_servers.json
Then:
If
aws-devops-agentkey exists AND the server is connected (tools are available, see "Step 3: Verify connectivity") → Inform the user: "DevOps Agent is already configured and connected."; If Bearer Token is used in the MCP config, suggest that you can alternatively setup the plugin to use SigV4 credentials for the AWS DevOps Agent (multiple agent spaces, admin tooling). If SigV4 credentials are used in the MCP config, suggest that you can alternatively setup the plugin to use Bearer Token credentials for the AWS DevOps Agent (single agent space).If
aws-devops-agentkey exists but is failing → continue to "Step 1: Diagnose current state"If
aws-devops-agentkey does NOT exist → continue to "Step 1: Diagnose current state"
Step 1: Diagnose current state
Run these checks:
# Bearer token
echo "DEVOPS_AGENT_TOKEN: $([ -n "$DEVOPS_AGENT_TOKEN" ] && echo 'set' || echo 'not set')"
echo "DEVOPS_AGENT_REGION: ${DEVOPS_AGENT_REGION:-not set}"
# SigV4 dependencies
uvx --version 2>&1
# AWS credentials
aws sts get-caller-identity 2>&1Determine:
bearer_ready=DEVOPS_AGENT_TOKENis set ANDDEVOPS_AGENT_REGIONis setsigv4_ready=aws sts get-caller-identitysucceeds ANDuvxis installed
Step 2: Decide auth path
After diagnostics, ALWAYS ask the user which path they want — even if only one is available. Present what you found and let them choose.
The user may want to use bearer token if they only have access to the operator app for an agent space.
The user may want to use SigV4 if they use multiple agent spaces and/or have admin permissions to manage agent spaces.
| Bearer ready | SigV4 ready | Action |
|---|---|---|
| yes | yes | "You have both a bearer token and AWS credentials configured. Which would you prefer for the DevOps Agent? Bearer token (single agent space) or AWS credentials / SigV4 (multiple agent spaces and admin tooling)?" |
| yes | no | "You have a bearer token configured. Would you like me to set up the DevOps Agent using your Bearer token (single agent space)? Or would you prefer to configure AWS credentials / SigV4 instead (multiple agent spaces and admin tooling)?" |
| no | yes | "You have valid AWS credentials. Would you like me to set up the DevOps Agent using SigV4 (multiple agent spaces and admin tooling)? Or would you prefer to set up a Bearer token instead (single agent space)?" |
| no | no | "Neither a bearer token nor AWS credentials are configured. Would you like to connect via Bearer token (single agent space) or AWS credentials / SigV4 (multiple agent spaces and admin tooling)?" Then guide them through the chosen path. |
If the user would like to setup a bearer token, refer them to the AWS docs for Connect to DevOps Agent remote servers or walk them through the steps to create a access token from this document.
Do NOT proceed to Step 3 until the user confirms their choice.
Step 3: Verify connectivity
If the "aws-devops-agent" MCP server is already running, check if you can list tools. If you can, then you have verified the connection.
Otherwise, proceed.
Verify BEFORE writing .mcp.json. This confirms the credentials work against the live endpoint. Or use this to verify an existing MCP server config.
Bearer verification
curl -s -w "\nHTTP_STATUS: %{http_code}" \
-X POST \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DEVOPS_AGENT_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
"https://connect.aidevops.${DEVOPS_AGENT_REGION}.api.aws/mcp"| Result | Meaning | Action |
|---|---|---|
HTTP 200 + result.tools array | Success | Proceed to Step 4 |
| HTTP 401 | Token invalid or expired | Tell user to create a new token in the Operator Web App |
| HTTP 403 | Token scope insufficient | Tell user token needs agent:read + agent:operate scopes |
| Connection refused / timeout | Endpoint unreachable | If SigV4 is available, offer fallback. Otherwise report unavailable. |
SigV4 verification
timeout 30 bash -c '
{
echo "{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"setup-check\",\"version\":\"1.0\"}}}"
sleep 0.5
echo "{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}"
sleep 0.5
echo "{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/list\",\"params\":{}}"
sleep 8
} | uvx mcp-proxy-for-aws-cli@latest "https://connect.aidevops.${DEVOPS_AGENT_REGION}.api.aws/mcp" --service aidevops --region "$DEVOPS_AGENT_REGION"
'Note: The first run may take 10-15s as
uvxdownloadsmcp-proxy-for-aws-cliand its dependencies. Subsequent runs are near-instant.
| Result | Meaning | Action |
|---|---|---|
Second line contains result.tools | Success | Proceed to Step 4 |
| No output / timeout | Credentials invalid or endpoint unreachable | Check aws sts get-caller-identity again |
ExpiredTokenException in stderr | AWS session expired | Tell user to re-authenticate (aws sso login or refresh creds) |
AccessDeniedException | Missing IAM permissions | User needs DevOps Agent permissions on their role |
Step 4: Confirm and write .mcp.json
Before writing, confirm with the user:
"I've verified connectivity. I'll now add the [Bearer token / SigV4] MCP server to the plugin's
.mcp.json. Proceed?"
Only write after the user confirms. Write ONE server entry — never both. Install the MCP config in ${CLAUDE_PLUGIN_ROOT}/.mcp.json. You can also offer to install the MCP server at the workspace level. The installation options are:
Plugin scoped:
${CLAUDE_PLUGIN_ROOT}/.mcp.json(default)Project-scoped: .mcp.json (in your project directory, version-controlled)
Project-specific: .claude/settings.local.json (in your project directory)
Bearer config
{
"mcpServers": {
"aws-devops-agent": {
"type": "http",
"url": "https://connect.aidevops.${DEVOPS_AGENT_REGION}.api.aws/mcp",
"headers": {
"Authorization": "Bearer ${DEVOPS_AGENT_TOKEN}"
},
"timeout": 120000
}
}
}SigV4 config
Replace <REGION> with the user's actual region:
{
"mcpServers": {
"aws-devops-agent": {
"command": "uvx",
"timeout": 120000,
"args": [
"mcp-proxy-for-aws-cli@latest",
"https://connect.aidevops.<REGION>.api.aws/mcp",
"--service", "aidevops",
"--region", "<REGION>"
]
}
}
}Fallback (aws-mcp)
Only add if the primary aws-devops-agent endpoint is unreachable AND SigV4 credentials are available:
{
"mcpServers": {
"aws-mcp": {
"command": "uvx",
"timeout": 100000,
"args": [
"mcp-proxy-for-aws-cli@latest",
"https://aws-mcp.us-east-1.api.aws/mcp",
"--metadata",
"AWS_REGION=us-east-1"
]
}
}
}For Sigv4 only: After writing the new MCP config, inform the user that the MCP server has been written successfully. Proceed to the next step.
Step 5: Multi-space routing (SigV4 only)
After successful SigV4 setup, discover and configure AgentSpace routing:
Call
list_agent_spacesvia the newly connected MCP to discover available spacesPresent the list to the user
If multiple spaces exist, write a routing guide to
.claude/aws-agents-for-devsecops.md:
# AWS DevOps Agent — Routing Guide
| Space | Agent Space ID | Purpose |
|-------|----------------|---------|
| <name> | <id> | <ask user> |Instruct: pass
agent_space_idon every tool call when targeting a specific space.
Step 6: Reload plugin
Inform the user that they will need to run /reload-plugins to start the new MCP server. You may need to prompt the user to run it. Also mention that after restarting the MCP server they should try the following prompts:
setup multi-space routing (SigV4 only)
<list skill and prompt suggestions from ${CLAUDE_PLUGIN_ROOT}/README.md>
Bearer token guidance (for users who need to create one)
Open the AWS DevOps Agent Operator Web App for your AgentSpace
Navigate to Settings → Access tokens → Generate token
Create a token with Permissions:
OperateSet environment variables:
export DEVOPS_AGENT_TOKEN="<your-token>" export DEVOPS_AGENT_REGION="<your-region>"Available regions: https://docs.aws.amazon.com/devopsagent/latest/userguide/about-aws-devops-agent-supported-regions.html
Restart Claude Code (it reads env vars from the shell that launched it)
Important: Without
Operatepermissions, thechatandinvestigatetools will be completely invisible — not just fail, but absent from the tool list.
SigV4 guidance (for users who need to configure AWS credentials)
Install
uvxif not present:macOS:
brew install uvLinux:
curl -LsSf https://astral.sh/uv/install.sh | sh
Configure AWS credentials:
aws configure sso --profile devops-agent aws sso login --profile devops-agent export AWS_PROFILE=devops-agentSet the region:
export DEVOPS_AGENT_REGION="<your-region>"Verify:
aws sts get-caller-identityThe IAM role must have DevOps Agent permissions (e.g., managed policy with aidevops access)
Important: Unset
DEVOPS_AGENT_TOKENwhen using SigV4. If both are set, clients may attempt bearer auth instead of the signing proxy.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| No tools visible | Token not set or Claude Code not restarted | Set DEVOPS_AGENT_TOKEN + DEVOPS_AGENT_REGION, restart |
| HTTP 401 | Token invalid/expired | Create new token in Operator Web App |
chat/investigate missing | Token scope is agent:read only | Create token with agent:operate scope |
| Connection refused / timeout | Endpoint unreachable | Check network; if SigV4 available, offer aws-mcp fallback |
ExpiredTokenException | AWS session credentials expired | aws sso login or refresh credentials |
AccessDeniedException (SigV4) | Missing IAM permissions | Use a role with DevOps Agent access |
| Proxy won't start | uvx not installed | brew install uv (macOS) or install per platform |
| Tools appear but calls timeout | Normal for chat (5-30s) | Ensure "timeout": 120000 in mcp.json |
Files
- ATTRIBUTION.mdAdded by AutoGineer922 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md12.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs network access, Needs a command-line tool
Security
What our scanner noticed· Medium risk
- Instructions that use the network
- Downloads piped into a shell
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · plugins/aws-agents-for-devsecops/skills/setup-devops-agent · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS or AWS.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download setup-devops-agent.zip