Cursor kanban: connect Cursor to a task board with MCP

What is a kanban MCP for Cursor?

It turns board actions into tools Cursor can call. Cursor reads the card, uses it as context and writes the result back after the code is checked. You spend less time being human middleware.

Cursor's MCP documentation supports local and remote servers. Kelvia uses a hosted URL with OAuth, so the normal setup does not need another tiny process living in your menu bar forever.

How do you connect Cursor to Kelvia MCP?

Add the server globally in ~/.cursor/mcp.json, or commit the same shape to a trusted project's .cursor/mcp.json:

{
  "mcpServers": {
    "kelvia": {
      "url": "https://mcp.kelvia.app/mcp"
    }
  }
}

Open Cursor Settings → Tools & MCP, enable kelvia and select Connect. Approve OAuth in the browser, then ask Cursor to list boards without changing them.

What does the Cursor-to-kanban loop look like?

1. Cursor reads the task and acceptance criteria before touching the repository.
2. The agent inspects code and returns a plan; the user approves the scope.
3. Cursor implements and verifies the change, then comments with the evidence.
4. The task moves to Review and the worklog records the effort; a person decides when it is Done.

This is deliberately less automatic than "finish everything." It creates a reviewable boundary between code execution and project state.

Which kanban actions does Kelvia expose?

Kelvia exposes boards, tasks, comments, worklogs, stages, members, invitations, tags and a personal day planner. Cursor can read the brief, create follow-up work, add a handoff comment, move a task to Review and keep the discussion beside the task.

Toolsets can publish only the relevant groups. For a small project, tasks plus comments is usually enough. Loading fewer tools keeps the agent's context focused and makes its next action easier to review.

How do you keep Cursor board writes safe?

Start with OAuth while you are watching. For a recurring agent, give it its own Kelvia identity and only the boards and scopes it needs. An edit key cannot magically escape a viewer role. No admin cape hidden under the hoodie.

• Auto-approve reads when the workflow needs speed.
• Ask for a preview before bulk task creation or status changes.
• Keep delete, invitations and role changes behind explicit approval.
• Use activity history to review which identity made each change.

Which Cursor kanban prompts are useful?

Read Kelvia task #28 and inspect the related code.
Return a plan and any missing acceptance criteria. Do not write yet.

Implement the approved plan and run the focused tests.
If they pass, comment on #28 with the evidence and move it to Review.
Do not close the task or modify unrelated cards.

For complete setup and troubleshooting, use the Kelvia MCP documentation. For another coding client, see the Claude Code and Codex guides.

FAQ

Can Cursor connect to a kanban board?

Yes. Cursor can connect to MCP servers that expose board and task tools.

Where is Cursor MCP configuration stored?

Use ~/.cursor/mcp.json globally or .cursor/mcp.json inside a project.

Does Kelvia support remote OAuth in Cursor?

Yes. Add the hosted endpoint, enable it under Tools & MCP and select Connect.

Can Cursor move a Kelvia task across columns?

Yes, when the connected identity has edit access to that board.