setup-devops-agent

Configure and diagnose the AWS DevOps Agent MCP server connection in .mcp.json.

1|Updated Aug 1, 2024
One-click install
npx skills add https://github.com/obispobruno/dotfiles --skill setup-devops-agent-obispobruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-devops-agent
Source: https://github.com/obispobruno/dotfiles/tree/main/dot_agents/skills/setup-devops-agent
Command: npx skills add https://github.com/obispobruno/dotfiles --skill setup-devops-agent-obispobruno

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about setup-devops-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the AWS DevOps Agent MCP server in Claude?▼

Run the setup flow which checks for existing aws-devops-agent config, diagnoses your credentials, verifies connectivity against the live endpoint, and writes one server entry to .mcp.json. You choose between Bearer token and SigV4 authentication before anything is written.

Bearer token vs SigV4 for AWS DevOps Agent — which should I use?▼

Use a Bearer token if you only have access to the operator app for a single agent space. Use SigV4 with AWS credentials if you work across multiple agent spaces or need admin tooling to manage agent spaces.

Why are the chat and investigate tools missing from the DevOps Agent?▼

Missing chat and investigate tools means your Bearer token only has the agent:read scope. Create a new token in the Operator Web App with the Operate permission, which grants the agent:operate scope required for those tools.

What does an ExpiredTokenException mean during SigV4 setup?▼

ExpiredTokenException means your AWS session credentials have expired. Re-authenticate with aws sso login or refresh your credentials, then verify with aws sts get-caller-identity before retrying the connection.

Can I configure both Bearer token and SigV4 at the same time?▼

No, only one server entry should be written to .mcp.json. If both DEVOPS_AGENT_TOKEN and AWS credentials are set, clients may attempt bearer auth instead of the signing proxy, so unset DEVOPS_AGENT_TOKEN when using SigV4.