mcp-integration

To connect MCP tools to a multi-agent system, use an MCPClient and MCPToolAdapter to asynchronously load the tool list from your HTTP or in-memory FastMCP server, then pass the adapted tools to your LlmAgent as its toolset for execution.

Yes, you can use a FastMCP in-memory server directly with an agent. The integration supports both HTTP endpoints and in-memory FastMCP server objects, allowing you to load tools via MCPToolAdapter without needing a remote network connection.

The best way to configure MCP tool servers in YAML is by defining them directly under the agent's tools section. This YAML Composer integration enables seamless tool loading and agent orchestration without requiring manual client initialization in your code.

Yes, this MCP integration works with both HTTP endpoints and in-memory FastMCP servers. You can initialize the MCPClient to target either an external HTTP endpoint or a local in-memory server object to retrieve and adapt tools for your agents.

You need an MCPToolAdapter to wire external tools to your agents because it fetches the MCP-exposed capabilities from the server and adapts them into a format that the LlmAgent can natively execute for question answering and automation workflows.

You should use an MCP tool adapter instead of direct integration when your company-specific utilities are hosted externally via an MCP server. It provides a consistent way to fetch and use MCP-exposed capabilities without manually wrapping each external tool.