native-mcp

You can expose external MCP server tools without manual bridge scripts by using an auto-discovery client that automatically registers them as native capabilities. This eliminates custom adapters by directly injecting discovered tools into the agent's toolset.

The MCP client supports both stdio command-line and HTTP transports for remote tool access. This allows diverse server setups across development and automation workflows to connect without requiring transport-specific adapters.

Discovered MCP tools are registered with the agent using a specific naming convention. They are automatically injected into all toolsets with the format mcp_{server}_{tool}, ensuring clear identification and immediate usability.

The MCP client handles security by filtering environment variables, passing only safe ones to subprocesses. It also redacts credentials in error messages to prevent sensitive data exposure during remote tool execution.

When an MCP server connection drops, the client maintains reliability through persistent connections with exponential backoff. It includes graceful shutdown handling to ensure automation workflows recover without manual intervention.

You can connect to a remote API server for data retrieval using auto discovery. The client automatically discovers and exposes the server's tools, allowing agents to retrieve data without writing custom adapters.