deploy_on_flux — Flux Cloud MCP Prompt

deploy_on_flux is one of 1 prompt on the Flux Cloud MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke deploy_on_flux from your client

• Claude Code Flux Cloud Prompt/deploy_on_flux run in your project directory
• Claude Desktop Flux Cloud Prompt/deploy_on_flux ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Flux Cloud Prompt/deploy_on_flux ~/.cursor/mcp.json
• VS Code Flux Cloud Prompt/deploy_on_flux .vscode/mcp.json
• Zed Flux Cloud Prompt/deploy_on_flux ~/.config/zed/settings.json
• Windsurf Flux Cloud Prompt/deploy_on_flux ~/.codeium/windsurf/mcp_config.json
• Cline Flux Cloud Prompt/deploy_on_flux ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Flux Cloud Prompt/deploy_on_flux ~/.gemini/settings.json
• Grok Flux Cloud Prompt/deploy_on_flux .mcp.json (in your project root)
• ChatGPT Flux Cloud Prompt/deploy_on_flux Settings → Connectors → Advanced → Developer mode
• Claude.ai Flux Cloud Prompt/deploy_on_flux Settings → Connectors → Add custom connector
• LangChain Flux Cloud Prompt/deploy_on_flux pip install langchain-mcp-adapters

Flux Cloud also offers 4 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.