Skip to content

[Feature] - Add developer-kit-clickup plugin with ClickUp MCP Server integration #91

Description

@giuseppe-trisciuoglio

Overview

This issue aims to implement a new plugin developer-kit-clickup that integrates ClickUp with Git workflows using the official ClickUp MCP Server, similar to the Jira implementation in PR #51.

Proposed Workflow

The workflow should mirror the jira-mcp-workflow and include the following commands:

Workflow Commands

  1. Start: devkit.clickup.workflow.start [TASK_ID]

    • Fetch task details via ClickUp MCP (Get Task)
    • Confirm with user
    • Execute git commands (checkout main, pull, create branch based on task ID/name)
    • Add comment to ClickUp (Create Task Comment)
  2. Commit: devkit.clickup.workflow.commit "message"

    • Stage and commit with task ID prefix
    • Add comment to ClickUp
  3. Push: devkit.clickup.workflow.push

    • Push branch to remote
    • Add comment to ClickUp with push details
  4. PR Create: devkit.clickup.workflow.pr-create [title]

    • Create PR via GitHub CLI
    • Transition task to a "Review" status (e.g., 'In Review') using Update Task
    • Add comment with PR link
  5. PR Ready: devkit.clickup.workflow.pr-ready

    • Mark PR as ready
    • Transition task status if applicable
  6. PR Merge: devkit.clickup.workflow.pr-merge

    • Merge PR via GitHub CLI
    • Transition task to 'Complete' or 'Done' status
    • Add final comment to ClickUp
  7. Status: devkit.clickup.workflow.status

    • Show git status and ClickUp task status

Individual Task Commands

  • devkit.clickup.task.view [TASK_ID]: Display task details.
  • devkit.clickup.task.comment [TASK_ID] "message": Add a comment.
  • devkit.clickup.task.status [TASK_ID] [STATUS]: Update task status.

Technical Details

  • MCP Server: Use the official ClickUp MCP Server.
  • Task Inference: Implement logic to extract Task IDs from branch names (e.g., feature/CU-xxxx), commit messages, and PR titles.
  • Confirmations: All state-changing operations (branch creation, status transitions, PR merges) must require user confirmation.

References

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions