350ce231a4
- Add workspace-mcp >= 1.20.0 to pyproject.toml (pulls google-api-python-client etc. transitively) - Remove redundant google-api-python-client/google-auth/google-auth-httplib2 direct deps - Rewrite google_workspace.py: single Secrets Manager call per tool (client_id/client_secret are already in the credentials secret stored by oauth-handler, no separate oauth-client secret needed) - Mirror workspace-mcp output format for list_calendars and get_calendar_events - Add body_format param to get_gmail_message (text/html/raw) matching workspace-mcp API - Update uv.lock
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.