Integration Approaches
| Framework | MCP Support | Recommended Approach |
|---|---|---|
| LangChain | Via MCP adapter | MCP native |
| CrewAI | Via MCP adapter or shell tools | FDX CLI wrapping |
| AutoGen | Via MCP adapter | MCP native |
| Semantic Kernel | Via adapter | MCP native |
| Custom | Depends on implementation | MCP SDK or FDX CLI |
LangChain
MCP Integration (Recommended)
FDX CLI Tool Wrapper
CrewAI
AutoGen
Custom MCP Client
For frameworks with direct MCP support or when building your own agent: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. Allfdx 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.