01
Open Cursor MCP settings
In Cursor IDE, open settings and navigate to the MCP configuration section. Cursor supports MCP tool servers that extend its AI capabilities with external services.
// Cursor + Flux
Boards inside your editor.
Connect Cursor IDE to Flux via MCP. Create cards, move tasks, and check board status without leaving your code. The AI handles the API calls.
02
Add the Flux MCP server
Add the Flux MCP server URL and your Flux API key to Cursor's MCP config. This registers Flux board operations as tools that Cursor's AI can call during your coding sessions.
03
Use AI commands to manage boards
Ask Cursor to create a card for the bug you just found, move a task to Done after fixing it, or list your current sprint board. Cursor calls the Flux MCP tools in the background and reports results inline.
04
Keep code and project tracking in sync
As you work on code, update your Flux board without switching windows. Create cards for TODOs you find in the codebase, mark tasks complete as you commit, and review board state without leaving your editor.
01 Does Cursor support MCP?
+
Yes. Cursor IDE supports MCP (Model Context Protocol) tool servers. You configure them in Cursor's settings, and the AI assistant can then call the registered tools during conversations. Check Cursor's documentation for the latest MCP setup instructions.
02 Can I use this alongside Cursor's other features?
+
Absolutely. The Flux MCP tools are additive. Cursor's code generation, editing, and chat features work as usual. The MCP connection adds board management as another capability the AI can use when relevant.
03 What Flux operations are available in Cursor?
+
The MCP server exposes board listing, card creation, card updates, card movement between columns, and board reading. These are the same operations available via the REST API, wrapped as MCP tools for AI consumption.
// Code and ship
Track work from your IDE.
Connect Cursor to Flux via MCP. No window switching, no context loss.