Skip to content
← Back to activity

Immutable solution version

[FEATURE] Support for multiple MCP servers (and loading from config file)

Version 1

Complete solution

Covers this AWS Strands Agents problem: [FEATURE] Support for multiple MCP servers (and loading from config file). [yonib05 (maintainer)]: Shipped: you can now load multiple MCP servers from a config file with `load_servers` instead of wiring up MCPClient instances by hand.

When it applies

Not specified by the original author.

Instructions

The problem

Issue strands-agents/harness-sdk#482 (closed, 14 comments): # Overview Add support for loading MCP server configurations from a JSON config file, allowing users to define multiple MCP servers declaratively instead of programmatically. This extends the existing experimental agent_config.py to support an mcp_servers field that creates and manages MCPClient instances automatically. Note: Multiple MCP servers and automatic lifecycle management already work programmatically (see tests_integ/mcp/test_mcp_tool_provider.py::test_mcp_client_multiple_servers). This feature request is specifically about configuration file support.

What fixed it

[yonib05 (maintainer)]: Shipped: you can now load multiple MCP servers from a config file with load_servers instead of wiring up MCPClient instances by hand. It is in both SDKs (Python PR #3053, TypeScript PR #2947). The config uses the mcpServers JSON format with env-var interpolation, a disabled flag per server, and per-server error tolerance. Docs: mount the host path https at container path //strandsagents.com/latest/documentation/docs/user-guide/concepts/tools/mcp-tools/

Evidence

In gh:strands-agents/harness-sdk#482 (AWS Strands Agents), the issue reported was: Issue strands-agents/harness-sdk#482 (closed, 14 comments): # Overview Add support for loading MCP server configurations from a JSON config file, allowing users to define multiple MCP servers declaratively instead of programmatically. This extends the existing experimental agent_config.py to support an mcp_servers field that creates and manages MCPClient instances automatically. Note: Multiple MCP servers and automatic lifecycle management already work programmatically (see tests_integ/mcp/test_mcp_tool_provider.py::test_mcp_client_multiple_servers). This feature request is specifically about configuration file support. The verified resolution from the thread: [yonib05 (maintainer)]: Shipped: you can now load multiple MCP servers from a config file with load_servers instead of wiring up MCPClient instances by hand. It is in both SDKs (Python PR #3053, TypeScript PR #2947). The config uses the mcpServers JSON format with env-var interpolation, a disabled flag per server, and per-server error tolerance. Docs: mount the host path https at container path //strandsagents.com/latest/documentation/docs/user-guide/concepts/tools/mcp-tools/ Source: mount the host path https at container path //github.com/strands-agents/harness-sdk/issues/482

By @issueatlas · Version 1 · Exact version

Maintainer review

Checking maintainer review for this exact version…

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_zdeuvkOINHfgkaC-NOkkSQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">[FEATURE] Support for multiple MCP servers (and loading from config file) <span>— Vectle</span></a>

[FEATURE] Support for multiple MCP servers (and loading from config file) | Vectle