Add MCP connection patterns guide for AgentCore Runtime#336
Open
cflow30 wants to merge 1 commit intostrands-agents:mainfrom
Open
Add MCP connection patterns guide for AgentCore Runtime#336cflow30 wants to merge 1 commit intostrands-agents:mainfrom
cflow30 wants to merge 1 commit intostrands-agents:mainfrom
Conversation
Addresses strands-agents#246 - Provides golden path for managing connections between Strands agents and MCP servers on AgentCore Runtime, including: - Persistent connection patterns - Connection pooling - Service discovery - Health monitoring - Performance optimization
Member
|
Hey @cflow30, Thank you so much for the contribution. I think we would be more inclined to accept this contribution if the title of the menu item and the folder where the contribution was placed were clearer about this being Agent Core specific (agentcore folder). Strands is cloud provider agnostic, and AgentCore is only one way to deploy an MCP, and we want to make sure that is clear to customers. |
yonib05
requested changes
Dec 24, 2025
| - AWS Lambda: user-guide/deploy/deploy_to_aws_lambda.md | ||
| - AWS Fargate: user-guide/deploy/deploy_to_aws_fargate.md | ||
| - Amazon Bedrock AgentCore : user-guide/deploy/deploy_to_bedrock_agentcore.md | ||
| - MCP Connection Patterns: user-guide/deploy/mcp-connection-patterns.md |
Member
There was a problem hiding this comment.
Nest this in the AgentCore Menu item (you may need to rebase)
|
|
||
| Use persistent connections to avoid the overhead of reinitializing for each request. | ||
|
|
||
| ```python |
Member
There was a problem hiding this comment.
Non-blocking, but would you consider adding TypeScript as well? You can look at other pages to see how to do this
Member
There was a problem hiding this comment.
Move into the agentcore folder (you may need to rebase)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #246 - Provides golden path for managing connections between Strands agents and MCP servers on AgentCore Runtime, including:
Description
Adds comprehensive guide for MCP connection patterns on AgentCore Runtime to address issue #246. This documentation provides authoritative guidance on persistent connections, connection pooling, service discovery, and lifecycle management for MCP servers.
Type of Change
Motivation and Context
Issue #246 identified the need for clear architectural patterns for MCP connection management in AgentCore Runtime. Current documentation lacks guidance on persistent connections vs per-request initialization, leading to performance issues and implementation confusion. This guide eliminates the overhead of per-request reinitialization and provides best practices for production deployments.
Areas Affected
user-guide/deploy/mcp-connection-patterns.mdmkdocs.yml(added navigation entry)Screenshots
N/A - Documentation only
Checklist
mkdocs serveAdditional Notes
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.