No install? Use cloud.anythingmcp.com directly.
Sign in, install the ClickUp in one click, paste the credentials, mint an MCP API key — done. No Docker, no git clone, no local server to run.
TL;DR
Drive ClickUp (project management) from any AI agent: spaces, folders, lists, tasks, comments, time tracking, custom fields, teams, members. 16 tools, API token auth.
💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → ClickUp klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein
git clone, kein lokaler Server.
ClickUp + Gemini
Drive ClickUp (project management) from any AI agent: spaces, folders, lists, tasks, comments, time tracking, custom fields, teams, members. 16 tools, API token auth.
Voraussetzungen
Die vollständige Setup-Anleitung ist in den Connector eingebaut (im Store sichtbar, wenn du den Connector auswählst). Benötigte Umgebungsvariablen für diesen Connector:
CLICKUP_API_TOKEN
Schritt 1 — Zugangsdaten holen
com/api).
Setup:
- Sign in to ClickUp → top-right avatar → Settings → Apps → API Token → Generate (personal token).
- Copy the token (starts with
pk_). SetCLICKUP_API_TOKEN.
Authentication: header Authorization: ${CLICKUP_API_TOKEN} — no Bearer or Token prefix, just the raw key. The adapter sets this via API_KEY profile.
…(continued in the in-app connector instructions)
Schritt 2 — Adapter installieren
git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d
Schritt 3 — Connector in Gemini hinzufügen
Gemini CLI liest MCP-Server aus ~/.gemini/settings.json (oder %APPDATA%\gemini\settings.json unter Windows). Hinzufügen:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MCP_API_KEY" }
}
}
}
- Hole deinen MCP API Key aus AnythingMCP → Profil → MCP API Keys → Neuer Key.
- Speichern und
geminineu starten. /mcpin Gemini CLI ausführen —ClickUpsollte als verfügbar gelistet sein.- Vertex AI Studio:
https://cloud.anythingmcp.com/mcpimtools-Array der Anfrage mit demselben Bearer-Header übergeben.
Verfügbare Tools
| Tool | What it does |
|---|---|
clickup_get_authorized_user | Return the authenticated user: id, username, email, color, profilePicture, initials |
clickup_list_teams | List workspaces (called 'teams' in the API — confusingly different from per-workspace 'teams' which are user groups) |
clickup_list_spaces | List spaces in a workspace |
clickup_list_folders | List folders in a space |
clickup_list_lists | List lists in a folder |
clickup_list_folderless_lists | List lists that live directly in a space (no parent folder) |
clickup_list_tasks | List tasks in a list with filtering |
clickup_get_task | Fetch a single task by ID with all fields including custom_fields, checklists, comments_count, dependencies, watchers |
clickup_create_task | Create a task in a list |
clickup_update_task | Update a task |
clickup_delete_task | Delete a task |
clickup_create_task_comment | Add a comment to a task |
clickup_list_task_comments | List comments on a task |
clickup_get_list_custom_fields | List custom fields available on a list, with their IDs and types |
clickup_list_team_members | List members of a workspace |
FAQ
Unterstützen Gemini 1.5 Pro oder 2.x MCP? Ja — Gemini CLI ≥ 0.4 und die Vertex AI Tools API akzeptieren MCP httpUrl-Connectors mit Bearer-Header.
Nächste Schritte
War dieser Guide hilfreich?