MCP Server APIs

The MCP (Model Context Protocol) Server APIs provide programmatic interfaces for client libraries and applications to interact with ClickUp resources through a standardized protocol. For more information about MCP, see the official documentation.

Transport Options

MCP Server supports two transport mechanisms:

1. HTTP Streaming - Long-lived HTTP connections with streaming responses
2. Server-Sent Events (SSE) - Event-based communication over HTTP

Available Resources

The following resource endpoints are available:

• ✅ Team - Team management
• 🚧 Space - Space management within teams
• ⛔️ Folder - Folder management within folders
• ⛔️ List - List management within folders
• ⛔️ Task - Task management within lists
• ⛔️ User - User management and information

Protocol Format

MCP requests and responses follow a standardized JSON format:

Request:

{
  "id": "request-id",
  "method": "resource.action",
  "params": {
    // Request parameters
  }
}

Response:

{
  "id": "request-id",
  "result": {
    // Response data
  },
  "error": null
}

Or in case of an error:

{
  "id": "request-id",
  "result": null,
  "error": {
    "code": 404,
    "message": "Resource not found"
  }
}

Error Handling

MCP Server API errors follow a standard format with an error code and descriptive message. Common error codes include:

• 400 - Bad Request (invalid parameters)
• 401 - Unauthorized (authentication required)
• 403 - Forbidden (insufficient permissions)
• 404 - Not Found (resource doesn't exist)
• 500 - Server Error (internal error)