MCP server
by asrvd
Flux (AO & Arweave) lets developers easily run, create, and test AO code using natural language—no deep technical skills
Enables developers to run, create, and test AO (Arweave's compute layer) code using natural language commands without needing deep technical knowledge of the underlying systems.
You can install Flux (AO & Arweave) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
Flux (AO & Arweave) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Flux (AO & Arweave) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Flux (AO & Arweave) against two servers with overlapping tools; this profile had the clearer scope statement.
We evaluated Flux (AO & Arweave) against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Flux (AO & Arweave) is the kind of server we cite when onboarding engineers to host + tool permissions.
Flux (AO & Arweave) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Flux (AO & Arweave) is the kind of server we cite when onboarding engineers to host + tool permissions.
Useful MCP listing: Flux (AO & Arweave) is the kind of server we cite when onboarding engineers to host + tool permissions.
Flux (AO & Arweave) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Flux (AO & Arweave) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
According to our notes, Flux (AO & Arweave) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 27
AI based AO tool calling on steroids that integrates with your existing tools and editor using a MCP server.
https://github.com/user-attachments/assets/3484e2db-e7cb-479a-84a2-0b399e1149ac
There are currently two ways to install and use Flux, right now it has been tested significantly only on Cursor so we will be showing how to install FLux in Cursor -
Local Setup - For users who want everything to be present locally, no remote servers involved
"mcpServers": {
"flux": {
"command": "npx",
"args": ["-y", "flux-ao@latest"],
}
}

Remote Setup - For users who want to use Flux without installing anything locally
"mcpServers": {
"flux": {
"url": "https://flux-2esw.onrender.com/sse",
}
}

We would suggest you add the llms.txt for AO docs in cursor first and use it as a context before you start using the MCP server. If you don't know how to do it, checkoout this documentation on how to add docs to cursor.
The more context you give to cursor, the more acurate the responses will be.
Now add these custom rules in your Cursor project to make sure Cursor doesn't hallucinate or give wrong responses. You can add these rules in the Settings > Cursor Settings > Rules > Add new rule.
For adding json capabilities ONLY IF NEEDED, you need to add a line "local json = require("json")" on top of file. BUT DONT USE IT UNLESS NEEDED. SIMPLE THINGS CAN BE DONE USING AO PROCESS STATE
Always use Send instead of msg.reply
Always make sure a handler is sending out a response/reply (using Send) and send it as data as well instaed of just returning using tags
Never add any tags by yourself, always add tags when needed or instructed by user, also {"Action":"Eval"} tag is for running lua in an ao process and {"Action" : "action_name"} is for running a handler
Never add the "Type" tag to anything, thats reserved for internal ao specifications
Always use Handler.utils whever possible when creating a handler, for example --
Handlers.add(
"pingpong",
Handlers.utils.hasMatchingTag("Action", "Ping"),
function (msg)
Handlers.utils.reply("Pong")(msg) -- or use Send() here
end
)
Now you can start using the Flux MCP server in Cursor Agents.
If you find any issues with the Server or encounter any bugs, please let us know by opening an issue or mailing us @ flux.mcp@gmail.com
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.