@dwlf/tickets-mcp

MCP server for the DWLF delivery board (tickets.dwlf.co.uk) — an internal ticket board for DWLF platform work. This package lets an AI agent (Claude Code or any MCP client) read and update the board.

It is a thin client over the board's REST API. It holds no secrets: you supply a personal access token via an environment variable.

Setup

The board's UI generates the exact command for you: sign in at tickets.dwlf.co.uk, click Connect agent, create a token, and copy the printed command. It looks like this:

claude mcp add dwlf-tickets --scope user \
  -e DWLF_TICKETS_API=https://mle2zqvap3.execute-api.eu-west-2.amazonaws.com/v1 \
  -e DWLF_TICKETS_TOKEN=dwlft_your_token_here \
  -- npx -y @dwlf/tickets-mcp

Then restart your MCP client.

Environment

| Variable | Required | Purpose | |---|---|---| | DWLF_TICKETS_API | yes | The board's API base (ends in /v1) | | DWLF_TICKETS_TOKEN | yes | A personal access token (dwlft_…) from the board | | DWLF_TICKETS_QUEUE_DIR | no | Where to park writes made while the board is unreachable (default ~/.dwlf-tickets/pending) |

Tools

tickets_list · tickets_get · tickets_create · tickets_update · tickets_comment · tickets_link · tickets_unlink · tickets_archive · tickets_meta · tickets_pending

Updates require the version you read (a mismatch is a 409, not a silent overwrite). If the board is unreachable, a write is parked locally and replayed on the next successful call, and every response says so until the queue drains — so the board never blocks work, and a write is never lost.

Access is restricted to @dwlf.co.uk. Without a valid token the tools do nothing.