ClickUp MCP Server: Governed AI Access

ClickUp's MCP server includes 51 different actions available to any connected model or AI agent. When registered with Barndoor, you can ensure centralized governance, visibility, and control across every AI agent your team uses.

Tools 51
Capabilities Create, Delete, Read, Update
Category Project & Task Management
Type Barndoor Hosted

What can AI agents do with the ClickUp MCP server?

Tools Available

• clickup_create_task
  create
  Create a task in a specific list with assignees, due dates, and details.

• clickup_get_task
  read
  Retrieve full details for a single task by task ID.

• clickup_update_task
  update
  Update task fields such as status, assignees, due date, or description.

• clickup_delete_task
  delete
  Delete a task from your workspace by task_id; confirm task_id with the user first.

• clickup_filter_tasks
  read
  Retrieve tasks with combined filters by tags, lists, folders, spaces, statuses, and dates.

• clickup_get_workspace_hierarchy
  read
  Retrieve spaces, folders, and lists in the workspace hierarchy.

Use cases for ClickUp

• Task Management
  "Create and update tasks with due dates", "Filter and search across your workspace", "Manage task dependencies and links"

• Time Tracking
  "Start and stop timers on tasks", "Log manual time entries for reporting", "Track time-in-status across the team"

• Workspace Organization
  "Create and manage spaces and folders", "Set up lists and track work items", "Resolve assignees and manage team members"

• Collaboration and Docs
  "Create and update workspace documents", "Send messages in chat channels", "Add comments and threaded discussions"

What are the risks of using the ClickUp MCP without an AI gateway?

• Uncontrolled reads — AI agents can pull data out of ClickUp with no visibility into what was accessed.
• Ungoverned writes — agents can create or modify records in ClickUp with no approval step.
• Destructive actions — agents can delete or overwrite ClickUp data with no approval gate or audit trail.

Why connect ClickUp with the Barndoor AI gateway?

Barndoor MCP Governance is the gateway between your AI agents and the tools they use.

• Centralized MCP management — One place to manage and control every MCP server across the organization so your team has an approved catalog of MCP servers that employees and AI agents connect through.
• Universal connection — One universal URL works across every AI provider your team uses.
• Fine-grained access controls — Set access policies for how AI is connecting with ClickUp based on human identities, agent profiles, tool-access, context, and data fields.
• Protect sensitive data — Keeps sensitive data from reaching a model or AI agent with PII detection, masking, tokenization, redaction, and more.
• Observability — Real-time reporting and dashboards that give you visibility into what AI is doing with ClickUp, how policies are being enforced, and who (human or agent) is doing what.
• Enterprise-grade security — Stay compliant with audit trails and logging.

Works with every AI client

ChatGPT
Claude Code
Claude Desktop
Codex
CrewAI
Cursor
Gemini CLI
GitHub Copilot
Google ADK
LangChain
Microsoft Copilot
OpenClaw

Getting started with ClickUp in Barndoor

1. Connect the ClickUp MCP server once
2. Define your policies
3. Go live across every AI client

Frequently asked questions

• What is MCP?
  MCP (Model Context Protocol) is the open standard that lets AI models and agents connect to external tools and data sources through a common interface, instead of a custom integration for every tool. ClickUp is an MCP server that exposes a defined set of tools an AI agent can call. Barndoor sits at that connection point, applying access policies and audit logging to every tool call regardless of which AI client is making it.

• Is Barndoor secure?
  Yes. Barndoor is SOC 2 Type II compliant. Barndoor enforces fine-grained access control, requires approval before destructive actions, protects sensitive data with data loss prevention, and logs every action for audit.

• How are ClickUp schema changes handled?
  Barndoor tracks tool and schema changes on ClickUp. New or changed tools inherit deny-by-default access until an admin reviews and approves them, keeping runtime enforcement current without manual reconfiguration. Every schema change is captured in the audit trail alongside who approved it.

• Do you integrate with my identity provider?
  Barndoor authenticates admins and policy managers through your OIDC or SAML 2.0 identity provider. Signing into Claude, Cursor, or ChatGPT still happens directly with those providers.

• Do users have to enter tokens manually?
  No. Barndoor brokers the OAuth connection to ClickUp centrally, so users and agents never handle or store a standing token themselves. Access is granted and revoked through policy instead of shared credentials.

• How does Barndoor integrate with AI agent identities?
  Barndoor gives each AI agent its own governed identity called an AgentProfile, separate from the human who configured or uses it.

• Can I deploy custom-built MCP servers?
  Yes. Barndoor supports customer-built MCPs, so internal tools and systems your team builds get the same policy enforcement and audit trail as Barndoor MCPs and official MCPs.

• Can I set and audit tool-level access across teams?
  Yes. Barndoor's access control is fine-grained, down to the agent, team, group, user, MCP server, the specific tool call, and the data type involved. Every call is logged with a timestamp, the user or agent calling it, the client it came from, and the result of the policy applied.

• How can I get started with ClickUp and Barndoor?
  Connect ClickUp once, define your access policies, and go live across every AI client your team uses.