What is Rework Mcp Server

Rework MCP Server is a Model Context Protocol (MCP) server designed to integrate the Rework platform with AI applications, enabling AI agents to interact with Rework projects, tasks, workflows, and jobs through a standardized protocol.

Use cases

Use cases include automating project tasks, managing workflows through AI agents, and integrating Rework functionalities into custom AI solutions.

How to use

To use Rework MCP Server, obtain your Rework credentials (API key and workspace information), configure the server with these credentials, and then manage your projects and workflows using natural language commands.

Key features

Key features include complete project management and workflow support, the ability to use natural language for project management, and options to disable specific tools if needed.

Where to use

Rework MCP Server is suitable for use in project management, task automation, and workflow integration within AI applications across various industries.

Rework MCP Server

A Model Context Protocol (MCP) server for integrating Rework platform with AI applications. This server allows AI agents to interact with Rework projects, tasks, workflows, and jobs through a standardized protocol.

🚀 Status Update: v1.1.0 now available with complete project management and workflow support.

Setup

1. Get your Rework credentials:
   • API key from Rework platform settings
   • Workspace information from your Rework account
2. Configure the MCP server with your credentials
3. Use natural language to manage your projects and workflows!

Installation

Add this entry to your client’s MCP settings JSON file:

{
  "mcpServers": {
    "Rework": {
      "command": "npx",
      "args": [
        "-y",
        "rework-mcp-server"
      ],
      "env": {
        "REWORK_PROJECT_ACCESS_TOKEN": "",
        "REWORK_PROJECT_PASSWORD": "",
        "REWORK_WORKFLOW_ACCESS_TOKEN": "",
        "REWORK_WORKFLOW_PASSWORD": "",
        "REWORK_ACCOUNT_ACCESS_TOKEN": "",
        "REWORK_ACCOUNT_PASSWORD": ""
      }
    }
  }
}

Alternatively, you can run the server directly using Node:

node index.js --env REWORK_PROJECT_ACCESS_TOKEN=your-project-access-token --env REWORK_PROJECT_PASSWORD=your-project-password --env REWORK_WORKFLOW_ACCESS_TOKEN=your-workflow-access-token --env REWORK_WORKFLOW_PASSWORD=your-workflow-password --env REWORK_ACCOUNT_ACCESS_TOKEN=your-account-access-token --env REWORK_ACCOUNT_PASSWORD=your-account-password

You can use the DISABLED_TOOLS environment variable to disable specific tools. Provide a comma-separated list of tool names to disable (e.g., create_task,get_tasks).

Disable tools you don’t need if you are experiencing issues with the number of tools or any context limitations.

Running with SSE Support

The server can be run in SSE (Server-Sent Events) mode by setting the following environment variables:

Or via command line:

node index.js --env REWORK_PROJECT_ACCESS_TOKEN=your-project-access-token --env REWORK_PROJECT_PASSWORD=your-project-password --env REWORK_WORKFLOW_ACCESS_TOKEN=your-workflow-access-token --env REWORK_WORKFLOW_PASSWORD=your-workflow-password --env REWORK_ACCOUNT_ACCESS_TOKEN=your-account-access-token --env REWORK_ACCOUNT_PASSWORD=your-account-password --env ENABLE_SSE=true --env PORT=8000

Docker Deployment

version: '3.8'

services:
  rework-mcp-server:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - '3000:8000'
    environment:
      - REWORK_PROJECT_ACCESS_TOKEN=${REWORK_PROJECT_ACCESS_TOKEN}
      - REWORK_PROJECT_PASSWORD=${REWORK_PROJECT_PASSWORD}
      - REWORK_WORKFLOW_ACCESS_TOKEN=${REWORK_WORKFLOW_ACCESS_TOKEN}
      - REWORK_WORKFLOW_PASSWORD=${REWORK_WORKFLOW_PASSWORD}
      - REWORK_ACCOUNT_ACCESS_TOKEN=${REWORK_ACCOUNT_ACCESS_TOKEN}
      - REWORK_ACCOUNT_PASSWORD=${REWORK_ACCOUNT_PASSWORD}
      - ENABLE_SSE=true
      - LOG_LEVEL=info
    volumes:
      - ./src:/app/src
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8000/health"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 5s

Features

Available Tools

See the project documentation for optional parameters and advanced usage.

User Management

When creating tasks or jobs, you can assign users using the user_id parameter. Additionally, you need to specify the creator_username to indicate who created the task or job:

{
  "name": "🚀 New Feature Implementation",
  "board_id": "board_123",
  "content": "Implement the new feature described in the spec",
  "creator_username": "jane.doe",
  "user_id": "user_456"
}

The user management tools help you find users by name or email and get their IDs for task assignment.

Error Handling

The Rework MCP server provides clear error messages for:

• Missing required parameters
• Invalid IDs or references
• Resources not found
• Authentication failures
• Permission issues
• API errors
• Rate limiting

The LOG_LEVEL environment variable can be specified to control the verbosity of server logs. Valid values are trace, debug, info, warn, and error (default).
This can also be specified on the command line as: --env LOG_LEVEL=info.

Custom Fields Support

Both task and job creation support custom fields through the custom_fields parameter, which accepts an array of objects with id and value properties:

{
  "custom_fields": [
    {
      "id": "custom_field_123",
      "value": "High Priority"
    },
    {
      "id": "custom_field_456",
      "value": true
    }
  ]
}

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Disclaimer

This software makes use of the Rework API. All trademarks and brand names are the property of their respective owners. This project is not officially associated with or endorsed by Rework.