Files
agent-claw/agentclaw/app/agent_claw_main
daniel 88ed337938 Add AWS MCP Server integration + IAM self-modify with approval gate
- CDK: add compute/build, broad read-only, IAM self-modify (scoped to own role),
  IAM policy management, and SSM read permissions to runtime1Role
- config.py: load /agent-claw/aws-mcp-url from SSM at cold start
- main.py: connect to AWS MCP Server with SigV4 auth (_AwsMcpSigV4Auth);
  add request_iam_permission and apply_iam_permission tools
- agentcore.json: add EXECUTION_ROLE_ARN env var
2026-05-15 08:56:06 -05:00
..
2026-05-06 18:55:16 -05:00
2026-05-06 18:55:16 -05:00
2026-05-06 18:55:16 -05:00

This is a project generated by the AgentCore CLI!

Layout

The generated application code lives at the agent root directory. At the root, there is a .gitignore file, an agentcore/ folder which represents the configurations and state associated with this project. Other agentcore commands like deploy, dev, and invoke rely on the configuration stored here.

Agent Root

The main entrypoint to your app is defined in main.py. Using the AgentCore SDK @app.entrypoint decorator, this file defines a Starlette ASGI app with the chosen Agent framework SDK running within.

model/load.py instantiates your chosen model provider.

Environment Variables

Variable Required Description
LOCAL_DEV No Set to 1 to use .env.local instead of AgentCore Identity

Developing locally

If installation was successful, a virtual environment is already created with dependencies installed.

Run source .venv/bin/activate before developing.

agentcore dev will start a local server on 0.0.0.0:8080.

In a new terminal, you can invoke that server with:

agentcore invoke --dev "What can you do"

Deployment

After providing credentials, agentcore deploy will deploy your project into Amazon Bedrock AgentCore.

Use agentcore invoke to invoke your deployed agent.