Flux

What is Flux?

Flux is an MCP server that enables AI-based AO tool calling using natural language. It integrates with existing developer tools and editors such as Cursor, Windsurf, and Claude by exposing AO code execution and blueprint creation through standard MCP tool calls.

How to use Flux?

Install Flux either locally (by running node with a local script) or remotely (by connecting to a hosted SSE endpoint). In Cursor, add Flux as a new MCP tool via Settings > Cursor Settings > MCP, then paste the appropriate JSON configuration. After loading, the Flux MCP tools are available in Cursor Agents. The README recommends adding the AO docs (llms.txt) as context and applying custom Cursor rules to improve response accuracy.

Key features of Flux

• Run AO code using natural language
• Create and run custom AO blueprints entirely with natural language
• Integrates with Cursor, Windsurf, Claude, and any MCP‑compatible tool
• Test code pushed to an AO process
• Create and test complex handlers

Use cases of Flux

• Automate AO process interactions from an AI‑powered editor
• Build and iterate on AO blueprints without writing Lua manually
• Test AO handlers and code changes inside your development environment
• Combine AO ecosystem tools with existing MCP‑supported editors

FAQ from Flux

What runtime does Flux require?

Flux requires the latest stable version of Node.js. It uses the MCP TypeScript SDK and is built with TypeScript and Node.js.

What transports does Flux support?

Flux supports both local (stdio) and remote (SSE) transports. The remote endpoint is hosted at https://flux-2esw.onrender.com/sse.

Which tools and editors work with Flux?

Flux works with any tool that supports MCP tool calling, including Cursor, Windsurf, and Claude. The README notes that it has been tested most extensively on Cursor.

Are there any special configuration rules for Cursor?

Yes. The README provides custom Cursor rules that advise always using Send instead of msg.reply, ensuring handlers reply with data, avoiding unnecessary tags, and leveraging Handlers.utils when creating handlers.

Where does the code execution happen?

Code is executed on AO processes. Flux pushes code to a process and can test that code, but does not run a local AO environment.