MCP.so
Sign In

rework-mcp-server

@caobo171

About rework-mcp-server

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": [
        "-y",
        "@taazkareem/clickup-mcp-server@latest"
      ],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "DOCUMENT_SUPPORT": "true"
      }
    }
  }
}

Tools

10

Create a task in a project

Get tasks from a board

Get detailed information about a task

Get all projects and boards

Create a job in a workflow

Get jobs from a workflow

Get detailed information about a job

Get all available workflows

Find users by name or email

Get all workspace members

Overview

What is rework-mcp-server?

A Model Context Protocol (MCP) server that integrates the Rework platform with AI applications, enabling AI agents to interact with Rework projects, tasks, workflows, and jobs via a standardized protocol.

How to use rework-mcp-server?

Obtain your Rework API key and workspace ID, then configure the MCP server in your client’s settings JSON or run it directly with Node. Optionally enable SSE mode, set a custom port, or disable specific tools using environment variables. Docker deployment is also supported.

Key features of rework-mcp-server

  • Create, view, and manage tasks and projects
  • Create and track jobs and workflows
  • Find users and assign them to tasks
  • Support for custom fields on tasks and jobs
  • ID and name‑based lookups with markdown content
  • Built‑in error handling and API rate limiting

Use cases of rework-mcp-server

  • AI assistant managing project tasks and boards
  • Automated workflow job creation and status tracking
  • User assignment and lookup within Rework workspaces
  • Natural language project and workflow management via AI

FAQ from rework-mcp-server

What credentials are required?

You need a Rework API key and workspace ID, configured via REWORK_API_KEY and REWORK_WORKSPACE_ID environment variables.

How do I disable specific tools?

Set the DISABLED_TOOLS environment variable to a comma‑separated list of tool names (e.g., create_task,get_tasks).

How do I run the server with SSE support?

Set ENABLE_SSE=true and optionally PORT (default 3000) in the environment, then start the server. See the Docker Compose example for a full setup.

Can I customize log verbosity?

Yes, set LOG_LEVEL to trace, debug, info, warn, or error (default: info).

What error messages does the server provide?

Clear messages for missing parameters, invalid IDs, not‑found resources, authentication failures, permission issues, API errors, and rate limiting.

Frequently asked questions

What credentials are required?

You need a Rework API key and workspace ID, configured via `REWORK_API_KEY` and `REWORK_WORKSPACE_ID` environment variables.

How do I disable specific tools?

Set the `DISABLED_TOOLS` environment variable to a comma‑separated list of tool names (e.g., `create_task,get_tasks`).

How do I run the server with SSE support?

Set `ENABLE_SSE=true` and optionally `PORT` (default 3000) in the environment, then start the server. See the Docker Compose example for a full setup.

Can I customize log verbosity?

Yes, set `LOG_LEVEL` to `trace`, `debug`, `info`, `warn`, or `error` (default: `info`).

What error messages does the server provide?

Clear messages for missing parameters, invalid IDs, not‑found resources, authentication failures, permission issues, API errors, and rate limiting.

Comments

More Other MCP servers