ClickUp AI Orchestrator via Supergateway Proxy

This architecture deploys the ClickUp MCP server stack, routing traffic through a Supergateway instance to expose functionality as a Server-Sent Events (SSE) interface. This setup is optimized for consumption by external automation frameworks like n8n nodes.

Necessary Components

• Node.js runtime environment (version 18+ recommended)
• Docker and Docker Compose for containerized deployment options
• Valid ClickUp Personal Access Token (API Key) and associated Workspace Team Identifier (Team ID)

Local Execution Guide

Direct Node.js Startup

1. Install global dependencies: bash npm install -g supergateway @taazkareem/clickup-mcp-server

2. Establish required environment authentication variables: bash export CLICKUP_API_KEY=pk_94547006_D8DFEXXFDOX7RUOJBBPLM2BSVRFXPZE9 export CLICKUP_TEAM_ID=2357720

3. Initiate the primary integration service: bash ./run-clickup-mcp.sh

4. Optional: Modify runtime parameters (e.g., port binding, CORS policy): bash ./run-clickup-mcp.sh --port 9000 --base-url http://example.com --cors "http://localhost:8080,http://localhost:3000"

Containerized Deployment (Docker Compose)

1. Generate a local configuration file from the template: bash cp .env.example .env

2. Populate the .env file with your specific ClickUp credentials.

3. Start the service stack detached from the terminal: bash docker-compose up -d

4. Monitor service output: bash docker-compose logs -f

Cloud Deployment Strategy (Railway)

1. Provision a new project within the Railway environment.

2. Use the Railway CLI or connect your source code repository for deployment.

3. Configure the following mandatory and optional runtime settings within the Railway dashboard:

   • CLICKUP_API_KEY: Secret ClickUp authorization token.
   • CLICKUP_TEAM_ID: Workspace identifier.
   • PORT: Network access port (defaulting to 8000).
   • BASE_URL: The public URL exposed by Railway (e.g., https://myapp.up.railway.app).
   • SSE_PATH: The URI segment for Server-Sent Events subscriptions (e.g., /sse).
   • MESSAGE_PATH: The URI segment for input message submission (e.g., /message).
   • LOG_LEVEL: Verbosity setting (e.g., info, debug).
   • DOCUMENT_SUPPORT: Boolean flag for enhanced document handling.
   • CORS_ORIGINS: Allowed client domains (e.g., * or comma-separated list).

4. Finalize the deployment process.

Interaction with n8n Automation

1. Within your n8n canvas, integrate a dedicated "MCP" connector node.

2. Configure the node's endpoint pointing to the service:

   • Server URL: Concatenate your Railway base URL and the SSE path (e.g., https://myapp.up.railway.app/sse).
   • Message Path: Specify the inbound message URI (e.g., /message).

3. Select the specific ClickUp operational module required from the available toolset.

4. Define necessary input parameters specific to the chosen ClickUp function.

5. Link the configured node into your broader workflow sequence.

Exposed Network Interfaces

• SSE Subscription Endpoint: {BASE_URL}{SSE_PATH} (Example: http://localhost:8000/sse)

  • Method: GET
  • Function: Establishes a persistent, unidirectional stream for receiving server notifications.

• RPC Message Ingress: {BASE_URL}{MESSAGE_PATH} (Example: http://localhost:8000/message)

  • Method: POST
  • Function: Accepts commands for processing.
  • Header Requirement: Content-Type set to application/json
  • Payload Format: JSON-RPC 2.0 structure.

• Operational Status Check: {BASE_URL}/healthz (Example: http://localhost:8000/healthz)

  • Method: GET
  • Function: Verifies the service availability.
  • Expected Output on Success: "ok"

Common Issue Resolution

• Connectivity Failures: Check local or cloud firewall rules for port accessibility.
• Authorization Failures: Re-validate the supplied ClickUp API credentials and Team Identifier.
• Client-Side Errors (CORS): Update the CORS_ORIGINS variable to explicitly whitelist the originating client domain.