Caplets Catalog
official
spiritledsoftware/caplets

AWS

Inspect and manage AWS accounts, Regions, services, resources, IAM-authorized operations, and AWS documentation through the managed AWS MCP Server.

Install
caplets install spiritledsoftware/caplets aws

Inspect before installing

  • Local controlThis Caplet can operate against local project or machine state.
  • Setup requiredThis Caplet includes setup steps that should be completed before use.
CAPLET.md

Frontmatter

FieldValue
nameAWS
descriptionInspect and manage AWS accounts, Regions, services, resources, IAM-authorized operations, and AWS documentation through the managed AWS MCP Server.
avoidWhenPrefer the project workspace and deployment tooling when only local IaC or application files are needed.
tagsaws, cloud, infrastructure, iam, operations
catalog.iconhttps://a0.awsstatic.com/libra-css/images/site/fav/favicon.ico
setup.verify[0].labelCheck AWS CLI identity
setup.verify[0].commandaws
setup.verify[0].argssts, get-caller-identity
setup.verify[1].labelCheck uvx is available
setup.verify[1].commanduvx
setup.verify[1].args--version
mcpServer.commanduvx
mcpServer.argsmcp-proxy-for-aws==1.6.2, https://aws-mcp.us-east-1.api.aws/mcp
mcpServer.startupTimeoutMs100000
mcpServer.callTimeoutMs300000

AWS

Targeting and Prerequisites

  • Confirm the intended account, Region, profile, service, and resource identifiers before inspecting broad AWS state.
  • Documentation, skill, list, and describe operations can narrow ambiguous service behavior or resource matches.
  • For multi-account installations, named profiles are exposed through AWS_MCP_PROXY_PROFILES; select the intended profile on calls that support it.
  • Use explicit Region names when the target Region matters, especially when the runtime was not started with AWS_REGION.

Safe Operation

  • Inspect existing resource state, IAM context, dependencies, tags, and CloudTrail or service evidence before operational changes.
  • AWS operations can affect production infrastructure, data, security boundaries, billing, and compliance posture. Keep access read-only until a write is necessary.
  • Use least-privilege IAM roles, permission boundaries, and AWS MCP Server IAM condition keys where available.
  • Review the target account, Region, resource, and expected production effect before a mutation.
  • Confirm destructive or high-impact targets before deleting, replacing, scaling, deploying, rotating credentials, changing IAM, modifying network policy, or changing data stores.

Troubleshooting

If credentials are missing or expired, refresh the AWS CLI credentials and rerun the setup verification before retrying.