ClickUp MCP Server with Supergateway

Name: ClickUp MCP Server with Supergateway
Author: MCP-Mirror

@MCP-Mirror

リポジトリ

ClickUp MCP Server with Supergateway について

Mirror of

#clickup #mcp-server #supergateway

基本情報

カテゴリ

その他

ライセンス

MIT license

ランタイム

node

トランスポート

stdio

公開者

MCP-Mirror

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is ClickUp MCP Server with Supergateway?

The ClickUp MCP Server with Supergateway runs a ClickUp MCP server through Supergateway, exposing it as an SSE endpoint for use by n8n nodes or other clients. It requires Node.js 18 or higher, Docker and Docker Compose, and a ClickUp API key and Team ID.

How to use ClickUp MCP Server with Supergateway?

Install dependencies with npm install -g supergateway @taazkareem/clickup-mcp-server, set environment variables CLICKUP_API_KEY and CLICKUP_TEAM_ID, then run ./run-clickup-mcp.sh. Optionally customize port, base URL, and CORS origins. For containerized deployment, copy .env.example to .env, edit with credentials, and run docker-compose up -d. Deploy to Railway by setting environment variables and deploying the app. Use with n8n by adding an MCP node configured with the server URL and message path.

Key features of ClickUp MCP Server with Supergateway

Exposes ClickUp MCP via SSE endpoint
Supports n8n MCP node integration
Runs locally with Node.js or Docker
Deployable to Railway cloud platform
Configurable port, CORS, and base URL

Use cases of ClickUp MCP Server with Supergateway

Automate ClickUp tasks from n8n workflows
Integrate ClickUp tools into custom SSE clients
Deploy a ClickUp MCP endpoint on Railway

FAQ from ClickUp MCP Server with Supergateway

What are the prerequisites?

Node.js 18 or higher, Docker and Docker Compose (for containerized deployment), and a ClickUp API key and Team ID.

What environment variables are required?

CLICKUP_API_KEY, CLICKUP_TEAM_ID. Optional: PORT, BASE_URL, SSE_PATH, MESSAGE_PATH, LOG_LEVEL, DOCUMENT_SUPPORT, CORS_ORIGINS.

How do I check if the service is running?

Access the healthcheck endpoint {BASE_URL}/healthz (GET). It returns "ok" if healthy.

What endpoints does the server expose?

SSE endpoint (GET {BASE_URL}/sse), Message endpoint (POST {BASE_URL}/message with JSON-RPC 2.0 body), and Healthcheck endpoint (GET {BASE_URL}/healthz).