Labsco
MCP SERVER

Create and track Rework tasks and workflow jobs by describing them, with users resolved by name rather than by ID.

Project & Task Management✓ Verified
Summary
Both halves of Rework — board tasks and workflow jobs — with the field definitions readable before you create anything.

The workflow tools give you the stage list and the field schema for a workflow, including which fields are required and what options they accept, so a job can be created correctly on the first attempt rather than rejected. Name-to-id resolution is a separate step by design: look the person up, take the username and id, then pass them into the create or filter call.

What it is

A server over the Rework platform covering both halves of it: project boards with tasks, and workflows with jobs that move through stages.

What you get
  • Tasks created on a board with tags, content, deadline, start date, assignee, parent task and custom fields supplied as code and value pairs
  • Tasks retrieved across boards and filtered by name query, board, project, creator, assignee, status and Unix-timestamp ranges for deadline and creation date, with paging
  • One task opened in full detail
  • Projects listed and filtered, each carrying its boards — task boards come back with the tasks on them
  • Jobs created in a workflow with the same shape of fields, and retrieved with filters that add a finish-date range
  • One job opened in detail, and comments posted onto it
  • Workflows listed with their stages and the field definitions used to create a job — name, code, type, whether it is required, and the available options
  • User lookup returning username, id, name and a match score, which is how a person's name in a request becomes the id an assignment needs
Requirements

A Rework account and credentials from the platform settings — three access-token and password pairs, one per area: REWORK_PROJECT_ACCESS_TOKEN with REWORK_PROJECT_PASSWORD, REWORK_WORKFLOW_ACCESS_TOKEN with REWORK_WORKFLOW_PASSWORD, and REWORK_ACCOUNT_ACCESS_TOKEN with REWORK_ACCOUNT_PASSWORD. Run it with npx -y rework-mcp-server over stdio, from the npm package rework-mcp-server, currently 1.1.5. ENABLE_SSE=true switches it to an SSE server on PORT, which defaults to 3000, and there is a Docker Compose setup for the same. DISABLED_TOOLS takes a comma-separated list of tool names to leave unregistered, which is the lever when a client is straining under the number of tools. LOG_LEVEL controls log verbosity.

Setup effort

One command plus a key — npx -y rework-mcp-server, then supply credentials