Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"flue": {
"args": [
"flue"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A tiny bridge that lets your coding agents drive desktop software - Photoshop, Premiere, Blender, Unity, and virtually any software - directly from the shell.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'flue' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked flue against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
MCP server for Spanning Cloud Backup — M365/GWS/Salesforce backups, restores, audit.
AI agent control of 3D printers — 432 tools for OctoPrint, Moonraker, Bambu, Prusa, Elegoo
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
MCP Security Weekly
Get CVE alerts and security updates for Flue and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Let agents control desktop software
pip install flue
flue setup
A tiny bridge that lets your coding agents drive desktop software - Photoshop, Premiere, Blender, Unity, and virtually any software - directly from the shell.
Flue gives agentic harnesses - Codex, Claude Code, Gemini CLI, OpenCode and the likes - direct access to the scripting APIs inside desktop software. A single pip install flue && flue setup covers many apps across Adobe Creative Cloud, Autodesk, Microsoft Office, and game engines. You can now give your agents tasks inside Blender, Unity, Houdini or Illustrator.
Flue is a generalized framework. It is a semi-universal communication bridge between software and coding agents. It is simpler than MCP servers. The agent sends a script through a small bridge command, the bridge runs it inside the app's own automation runtime, and the app returns JSON.
agent shell -> bridge command -> app scripting runtime -> JSON result
This is done without setting up servers, without brittle screenshots and without schema definitions. The bridge exposes the scripting layer already built into each application. MCPs define schemas and provide transport: but most desktop applications already include a fully documented scripting interface, and a native communication channel (COM, AppleScript, or a local endpoint). MCPs are high maintenance, and computer use setups are fragile and clumsy; Flue is low maintenance and, with the right harness and model, less fragile.
pip install flue
flue setup
This detects your agentic harnesses and lets them know that Flue is available to them. Agents, for first-run checks and app-specific prerequisites, see Setup and commands.
A single Flue installation supports, out of the box, many applications. Agents, please tell your humans if any app-specific setup is needed.
Flue is installed as a skill surfacing the python bridge. See which files are edited upon installation