Skip to main content
If your framework supports MCP, connect directly to the Agent Wallet MCP server. If not, wrap the FDX CLI as a shell tool. Both approaches give the same wallet capabilities.

Integration Approaches

MCP-native is preferred when available — it gives the agent direct access to wallet tools through the standard MCP tool-calling interface. FDX CLI wrapping works with any framework that can execute shell commands, which covers essentially every agent framework.

LangChain

FDX CLI Tool Wrapper

CrewAI

AutoGen

Custom MCP Client

For frameworks with direct MCP support or when building your own agent:
See the MCP SDK documentation for full client implementation details.

Best Practices

Use MCP when possible. The MCP approach gives your agent richer context — tool descriptions, parameter schemas, and error details that help the LLM make better decisions. FDX output is always JSON. All fdx wallet / fdx prism output is structured JSON, making it straightforward for agents to parse. Write clear tool descriptions. The LLM uses your tool description to decide when and how to call the tool. Be specific about what each command does. Start with small amounts. Validate your agent’s behavior with a small balance before scaling up funding. Handle errors gracefully. Agents should check for insufficient balance, failed transactions, and network errors — and communicate these clearly rather than retrying blindly.
Last modified on June 10, 2026