ClickUp MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is ClickUp MCP Server?

ClickUp MCP Server is a Model Context Protocol server implementation that enables AI assistants to interact with ClickUp workspaces, facilitating task and project management through AI integration.

how to use ClickUp MCP Server?

To use the ClickUp MCP Server, configure the server with your ClickUp OAuth credentials, restart the application, and it will automatically download and start when needed.

key features of ClickUp MCP Server?

  • Integration with ClickUp for task management
  • Secure OAuth2 authentication
  • Environment variable configuration for flexibility
  • Tools for team and list management

use cases of ClickUp MCP Server?

  1. Automating task creation and updates in ClickUp.
  2. Managing teams and lists programmatically.
  3. Creating boards for project organization.

FAQ from ClickUp MCP Server?

  • What is required to run the ClickUp MCP Server?

You need to set up your ClickUp OAuth credentials and configure the environment variables.

  • Is the ClickUp MCP Server secure?

Yes, it uses OAuth2 for secure authentication and encrypts tokens at rest.

  • How can I troubleshoot common issues?

Common issues include authentication errors and server startup problems, which can be resolved by checking your environment variables and logs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago