Supported Clients
The XBTFX MCP Server works with any client that implements the Model Context Protocol. The following clients have been tested:
Tested Clients
Section titled “Tested Clients”| Client | Type | Setup |
|---|---|---|
| Claude Code | CLI agent | claude mcp add xbtfx-trading -e XBTFX_API_KEY=... -- npx @xbtfx/mcp-trading |
| Claude Desktop | Desktop assistant | Add to claude_desktop_config.json — see Configuration |
| Cursor | AI code editor | Add to .cursor/mcp.json — see Configuration |
| Windsurf | AI code editor | Add to MCP settings — same JSON format as Cursor |
| OpenAI Codex | CLI agent | codex mcp add xbtfx-trading -- npx @xbtfx/mcp-trading |
Other MCP Clients
Section titled “Other MCP Clients”Any client that supports the MCP stdio transport should work. The server uses @modelcontextprotocol/sdk and communicates over stdin/stdout.
Alternative: Skills Hub
Section titled “Alternative: Skills Hub”The Skills Hub provides the same API coverage through structured markdown files. It works with any agent framework — not just MCP clients:
| Framework | How to Use |
|---|---|
| Claude Code | claude --skill ./skills/xbtfx/xbtfx-trading/SKILL.md |
| LangChain | Ingest SKILL.md as tool description |
| CrewAI | Reference in agent instructions |
| Custom agents | Parse structured markdown |
The MCP server is preferred when your client supports MCP natively, as it provides automatic tool discovery and structured parameter validation. The Skills Hub is better for frameworks that don’t support MCP.