A side-by-side look at the Flox MCP and Keel Trade MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Flox MCP for finance & fintech work as a local process; choose Keel Trade for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Flox MCP when
You need dedicated capabilities in the Finance & Fintech domain.
No tool names declared yet. Check the project README from the listing page.
Keel Trade tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flox MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Keel Trade belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Flox MCP for finance & fintech work and Keel Trade for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flox MCP is listed as free. Auth: no auth required. Keel Trade is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flox-foundation-flox-mcp and keel-trade-keel-trade as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flox MCP has a quality signal of 59/100 (Good) with 5 views, 0 installs and 228 GitHub stars. Keel Trade has 49/100 (Fair) with 3 views, 0 installs and 2 GitHub stars.