What problem does it solve?
Building correct Model Context Protocol integrations requires handling transports, protocol eras, authentication, tasks, subscriptions, and raw result preservation, and mistakes like converting MCP tools into plain functions lose protocol state and capabilities.
Core Features & Use Cases
- Native MCP Client Integration: Attach AxMCPClient instances to AxGen, AxAgent, AxFlow, or chat via the
mcp option, preserving sessions, catalogs, tasks, and raw multimodal results.
- Transport and Era Selection: Choose between Streamable HTTP, legacy HTTP/SSE, WebSocket, and stdio transports, with automatic classification of legacy versus modern protocol eras.
- Event-Driven Agents: Combine AxMCPEventSource with AxEventRuntime to route resource updates, task states, and notifications into authenticated agent wake/resume routes.
- Use Case: Connect an Ax agent to a remote MCP documentation server over Streamable HTTP with bearer authentication, subscribe to markdown resource updates, and wake a reviewer agent whenever the engineering guide changes.
Quick Start
Ask the AI to create an AxMCPClient with a Streamable HTTP transport and attach it to an Ax agent so the agent can call the server's MCP tools.