setup-devops-agent

Installation
SKILL.md

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

The plugin has a default aws-devops-agent entry in ${CLAUDE_PLUGIN_ROOT}/.mcp.json. This entry uses Bearer token auth for us-east-1. It gets the token from DEVOPS_AGENT_TOKEN. Before setup, this variable is usually not set. Because of this, the server shows as failed with HTTP 401 at session start. The 401 message is Access token not configured. Older servers send Invalid or expired access token. This 401 is normal before setup. It does not show a bad token. If DEVOPS_AGENT_TOKEN is not set, the server is not set up. Go to "Step 1: Diagnose current state". Do not tell the user that the token is expired.

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:

Installs
1.7K
GitHub Stars
3.5K
First Seen
Jun 18, 2026