What are the prerequisites?
Node.js 18 or higher, Docker and Docker Compose (for containerized deployment), and a ClickUp API key and Team ID.
ClickUp MCP Server with Supergateway
@MCP-Mirror
Basic information
About ClickUp MCP Server with Supergateway
Mirror of
ClickUp MCP Server with Supergateway config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryClickUp MCP Server with Supergateway tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
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
Frequently asked questions
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`).
How do I troubleshoot connection issues?
Ensure firewall allows the port, verify ClickUp API key and Team ID, and set `CORS_ORIGINS` to include client origins.
More Other MCP servers
Screenpipe
screenpipeYC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
22.0K
Yuppsy
Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
MaxKB
1Panel-dev🔥 MaxKB is an open-source platform for building enterprise-grade agents. 强大易用的开源企业级智能体平台。
22.0K
Codelf
unbugA search tool helps dev to solve the naming things problem.
14.2K
Volley.sh
VolleyA good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Comments