Skip to content
This repository was archived by the owner on Jun 3, 2026. It is now read-only.

Add MCP connection patterns guide for AgentCore Runtime#336

Open
cflow30 wants to merge 1 commit into
strands-agents:mainfrom
cflow30:add-mcp-connection-patterns
Open

Add MCP connection patterns guide for AgentCore Runtime#336
cflow30 wants to merge 1 commit into
strands-agents:mainfrom
cflow30:add-mcp-connection-patterns

Conversation

@cflow30

@cflow30 cflow30 commented Nov 19, 2025

Copy link
Copy Markdown

Addresses strands-agents/harness-sdk#2568 - 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

Description

Adds comprehensive guide for MCP connection patterns on AgentCore Runtime to address issue strands-agents/harness-sdk#2568. This documentation provides authoritative guidance on persistent connections, connection pooling, service discovery, and lifecycle management for MCP servers.

Type of Change

  • New content addition

Motivation and Context

Issue strands-agents/harness-sdk#2568 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

  • New page: user-guide/deploy/mcp-connection-patterns.md
  • Updated: mkdocs.yml (added navigation entry)

Screenshots

N/A - Documentation only

Checklist

  • I have read the CONTRIBUTING document
  • My changes follow the project's documentation style
  • I have tested the documentation locally using mkdocs serve
  • Links in the documentation are valid and working
  • Images/diagrams are properly sized and formatted
  • All new and existing tests pass

Additional Notes

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Addresses #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
@yonib05

yonib05 commented Dec 24, 2025

Copy link
Copy Markdown
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.

Comment thread mkdocs.yml
- 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking, but would you consider adding TypeScript as well? You can look at other pages to see how to do this

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move into the agentcore folder (you may need to rebase)

@strands-agent

Copy link
Copy Markdown
Contributor

This repository has been merged into the strands-agents/harness-sdk monorepo and will be archived shortly. All new development happens there.

If this PR is still relevant, please recreate it against the monorepo. The code now lives under site/. Full commit history was preserved, so your base should be findable.

Apologies for the disruption, and thank you for contributing!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants