MCP Setup for Codex, Claude, TraeWork and Other Agents
Install the local FusionIntel MCP server, configure your client and verify tool access.
Maintained by FusionIntel Labs · Product documentation and data interpretation
Requirements
Use a supported Node.js LTS release. The local server communicates over stdio and calls the FusionIntel HTTPS API. Your client must support launching local commands.
Configure your client
Choose your client on the integrations page for its exact configuration format. Codex, Claude Code, Cursor, TraeWork, WorkBuddy and VS Code use different settings.
Download the versioned MCP package
FusionIntel hosts this package directly. The bare npm package name is not available in the public registry. The API URL is not a remote MCP URL.
npx -y https://fusionintel.net/downloads/fusionintel-mcp-2.0.2.tgzVerify the connection
Restart or reconnect the MCP server. Inspect its tool list, then ask the agent to call get_public_macro_feargreed. This one tool needs no API key. For protected data, configure FUSIONINTEL_API_KEY privately and use a dataset and history window covered by your plan.
Troubleshooting
If Windows cannot launch npx, use command cmd and arguments /c, npx, -y, followed by the package URL. Keep API keys out of shared configuration and source control. A 401 indicates an invalid or missing key, 403 a permission issue, and 429 a quota limit.