Rework MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rework MCP Servercreate a new task to review the project proposal by Friday"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.3 now available with complete project management and workflow support.
Setup
Get your Rework credentials:
API key from Rework platform settings
Workspace information from your Rework account
Configure the MCP server with your credentials
Use natural language to manage your projects and workflows!
Related MCP server: Rytnow MCP Server
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-passwordYou 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:
{
"mcpServers": {
"Rework": {
"command": "node",
"args": [
"index.js"
],
"env": {
"REWORK_PROJECT_ACCESS_TOKEN": "your-project-access-token",
"REWORK_PROJECT_PASSWORD": "your-project-password",
"REWORK_WORKFLOW_ACCESS_TOKEN": "your-workflow-access-token",
"REWORK_WORKFLOW_PASSWORD": "your-workflow-password",
"REWORK_ACCOUNT_ACCESS_TOKEN": "your-account-access-token",
"REWORK_ACCOUNT_PASSWORD": "your-account-password",
"ENABLE_SSE": "true",
"PORT": "8000" // Optional, defaults to 3000
}
}
}
}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=8000Docker 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: 5sFeatures
π Project Management | π Workflow Management |
β’ Create and manage tasksβ’ View task detailsβ’ List tasks in projectsβ’ Add comments to tasksβ’ Organize tasks within projectsβ’ View task status and progress | β’ Create and manage jobsβ’ Track job statusβ’ View job detailsβ’ List jobs by workflowβ’ Organize workflowsβ’ Link jobs to workflows |
π₯ User Management | β‘ Integration Features |
β’ Find users by name or emailβ’ List all available usersβ’ Assign users to tasksβ’ View user informationβ’ User authenticationβ’ Manage user permissions | β’ ID and name-based lookupsβ’ Markdown content supportβ’ Built-in error handlingβ’ API rate limitingβ’ Validation of inputsβ’ Comprehensive API coverage |
Available Tools
Tool | Description | Required Parameters |
Project Management | ||
| Create a task in a project |
|
| Get tasks from a board |
|
| Get detailed information about a task |
|
| Get all projects and boards | Optional search query |
Workflow Management | ||
| Create a job in a workflow |
|
| Get jobs from a workflow |
|
| Get detailed information about a job |
|
| Get all available workflows | Optional search query |
User Management | ||
| Find users by name or email |
|
| Get all workspace members | None |
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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityCmaintenanceEnables AI integrations with ClickUp tasks, supporting resource management, task operations, workspace organization, and AI-powered task recommendations through a standardized protocol.24,32150
- Flicense-quality-maintenanceEnables AI assistants to interact with Rytnow project management platform, supporting task management, time tracking, plan creation, and team collaboration through natural language commands.
- Alicense-qualityAmaintenanceEnables AI assistants to manage Todocko application data, including tasks, projects, worklogs, and attachments. It supports comprehensive project management operations such as tracking activity, managing Kanban boards, and handling shared project synchronization.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to submit projects, track tasks, and manage work on RobotFail, connecting them with human workers for real-world task execution.8MIT
Related MCP Connectors
Manage projects, tasks, time tracking, and team collaboration through natural language.
Task manager your agent can fully operate: boards, tasks, sprints, roles, worklogs, day planner.
Create and manage AI agents that collaborate and solve problems through natural language interactiβ¦
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rework-com/rework-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server