Skip to content

strands

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

strands

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
.env.example
.env.example
 
 
README.md
README.md
 
 
main.py
main.py
 
 
pyproject.toml
pyproject.toml
 
 

README.md

Example: Using MCP Proxy for AWS as a client for Strands Agents SDK

This example demonstrates how to use aws_iam_streamablehttp_client from mcp-proxy-for-aws to connect a Strands AI agent to an MCP server using AWS IAM authentication.

Note: Strands accepts a factory function that returns an MCP client. The aws_iam_streamablehttp_client is passed as a factory to Strands' MCPClient, which handles the connection lifecycle internally.

Prerequisites

Setup

Create a .env file or set the following environment variables:

# MCP server details
MCP_SERVER_URL=https://example.gateway.bedrock-agentcore.us-west-2.amazonaws.com/mcp
MCP_SERVER_AWS_SERVICE=bedrock-agentcore
MCP_SERVER_REGION=us-west-2

All three environment variables are required.

Usage

Run the example:

uv run main.py

The agent will connect to the MCP server and list its available tools.

How It Works

  1. Loads configuration from environment variables or .env file
  2. Creates an AWS IAM-authenticated MCP client using aws_iam_streamablehttp_client()
  3. Integrates with Strands by passing the client factory to MCPClient
  4. Loads tools from the MCP server
  5. Creates an agent with access to the MCP server tools
  6. Runs the agent to demonstrate tool discovery and usage

Example MCP Server URL Formats

AgentCore Runtime URL:

https://bedrock-agentcore.[AWS_REGION].amazonaws.com/runtimes/[RUNTIME_ID]/invocations?qualifier=DEFAULT&accountId=[AWS_ACCOUNT_ID]

AgentCore Gateway URL:

https://[GATEWAY_ID].gateway.bedrock-agentcore.[AWS_REGION].amazonaws.com/mcp

Troubleshooting

Common Issues

No AWS credentials available

  • Verify AWS credentials are configured (AWS CLI, environment variables, or IAM roles)
  • Test with aws sts get-caller-identity

Missing environment variables

  • Ensure all required variables are set: MCP_SERVER_URL, MCP_SERVER_REGION, and MCP_SERVER_AWS_SERVICE
  • Check your .env file or environment variable configuration

Connection errors

  • Verify your MCP server details are correct
  • Ensure the MCP server is running and accessible
  • Verify your AWS credentials have the necessary permissions to access the MCP server