Nextcloud Deck MCP Server for Cursor

A Model Context Protocol (MCP) server that connects Cursor to a Nextcloud Deck kanban board. Cursor agents can list, create, update, move, archive, and delete tasks on your board.

Deck does not have a separate “status” field on cards. A card’s status is the column (stack) it lives in. This server maps your column titles to canonical statuses (backlog, todo, blocked, planned, in_progress, review, done) so the agent can work with familiar status names.

Prerequisites

• Nextcloud instance with the Deck app installed
• A Nextcloud account with access to the target board
• An app password (recommended) or token for API access — not your main account password
• Go 1.22+ to build the server (or use a prebuilt deck-mcp binary)

Create an app password

1. Log in to Nextcloud → Settings → Security
2. Under Devices & sessions, create a new app password
3. Copy the generated token — this is your NEXTCLOUD_TOKEN

Column naming (important)

Each Deck column is a stack. The MCP server resolves canonical statuses from column titles.

Recommended layout

A simple workflow works well:

Matching is case-insensitive and ignores extra spaces, hyphens, and underscores (To-Do = todo).

You do not need exactly these titles — the defaults cover common variants. If your board uses unusual names, set DECK_STATUS_ALIASES (see below).

Custom column names

Override or extend aliases with JSON in DECK_STATUS_ALIASES:

{
  "done": ["Shipped", "Released"],
  "in_progress": ["Building"]
}

Keys are canonical statuses; values are column titles on your board.

Unmapped columns

Columns that do not match any status appear as unmapped in listings. Tools that move or create tasks by status require a column that maps to the requested status.

Find your board ID

1. Open the board in the Deck web UI
2. Check the URL — the board ID is usually in the path, e.g. /apps/deck/board/42 → board ID 42
3. Or call the API: GET {NEXTCLOUD_URL}/index.php/apps/deck/api/v1.0/boards (with auth) and read the id field

Configuration

Environment variables

Build

git clone https://github.com/vatlnetwork/nextcloud-deck-mcp-server.git
cd nextcloud-deck-mcp-server
make build
# binary: ./deck-mcp

Or:

go build -o deck-mcp ./cmd/deck-mcp

Cursor MCP setup

Edit ~/.cursor/mcp.json (create if missing):

{
  "mcpServers": {
    "nextcloud-deck": {
      "command": "/absolute/path/to/deck-mcp",
      "env": {
        "NEXTCLOUD_URL": "https://cloud.example.com",
        "NEXTCLOUD_USERNAME": "your-user",
        "NEXTCLOUD_TOKEN": "your-app-password",
        "DECK_BOARD_ID": "42"
      }
    }
  }
}

Use the full path to the deck-mcp binary. Restart Cursor or reload MCP servers after changes.

Do not commit credentials. Keep tokens only in mcp.json or your environment.

MCP tools

... View full README on GitHub