Awslabs Ccapi Mcp

AWS Cloud Control API

Direct resource management with security scanning.

When to use

• Use AWS Cloud Control API only when the task directly involves the relevant service, SaaS product, platform, or technology.

Connection

Docker stdio

{
  "command": "docker",
  "args": [
    "run",
    "--rm",
    "-i",
    "-e",
    "AWS_SECRET_ACCESS_KEY",
    "mcp/ccapi-mcp-server"
  ]
}

MCP instructions

• Use the MCP tools only for the user-requested service workflow and prefer read-only operations by default.
• Confirm the target account, workspace, project, repository, or dataset before actions that can read private data or mutate remote state.
• This server requires authorization or environment-provided credentials; ask the user before connecting or requesting access.

Docker launch notes

• Launch through Docker stdio with docker run --rm -i -e AWS_SECRET_ACCESS_KEY mcp/ccapi-mcp-server.
• Confirm required environment variables before launch: AWSSECRETACCESS_KEY.

References

• https://github.com/awslabs/mcp
• https://github.com/docker/mcp-registry/tree/main/servers/awslabs-ccapi

Security policy

• Authentication: Environment variables

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Friz-zy
• Source: Friz-zy/ai-capability-registry
• License: MIT

Install and usage instructions live in the source repository linked above.