Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ClickUp Scribe

    0

    Bulk read and write ClickUp boards over the REST API without burning the ClickUp MCP's daily quota - idempotent, dry-run first.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    ClickUp Scribe

    ClickUp Scribe

    Example session with this skill installed

    I need to sync my local roadmap.json to the 'Product Development' list. Run a dry run first to see what tasks would be created.

    • Read your context and instructions
    • Compiled the clickup scribe

    Dry run complete: 4 tasks would be created, 2 already exist, nothing was written.

    I copied the bundled ClickUp Scribe scripts into a temporary folder and compared roadmap.json with the Product Development list over the REST API, so none of your ClickUp MCP quota was used.

    $ scribe.py apply roadmap.json
    list 901600000002: 2 tasks present
    spec: 6 entries, 4 to create, 0 to update
    
      = API Authentication Flow  (completed)
        + OAuth2 Integration  (to do)
        + Webhook Listener  (to do)
      = Database Schema Design  (completed)
      + Rate Limit Middleware  (to do)
      + Documentation Site  (to do)
    
    Dry run. Re-run with --apply to write.
    
    ActionTaskTypeStatus from your spec
    Exists, left as isAPI Authentication FlowTaskcompleted
    CreateOAuth2 IntegrationSubtask of API Authentication Flowto do
    CreateWebhook ListenerSubtask of API Authentication Flowto do
    Exists, left as isDatabase Schema DesignTaskcompleted
    CreateRate Limit MiddlewareTaskto do
    CreateDocumentation SiteTaskto do

    Existing tasks are matched by name across the whole list, so a re-run never creates duplicates. Nothing is ever deleted.

    One mismatch to know about: your spec marks API Authentication Flow as completed, but on the board it is still

    in progress. A plain apply leaves existing tasks untouched. Adding --reconcile would update it as well:

    $ scribe.py apply roadmap.json --reconcile
    list 901600000002: 2 tasks present
    spec: 6 entries, 4 to create, 1 to update
    
      = API Authentication Flow  (completed)
        + OAuth2 Integration  (to do)
        + Webhook Listener  (to do)
      = Database Schema Design  (completed)
      + Rate Limit Middleware  (to do)
      + Documentation Site  (to do)
      ~ API Authentication Flow -> status=completed
    
    Dry run. Re-run with --apply to write.
    

    Next steps

    • Check that OAuth2 Integration and Webhook Listener belong under API Authentication Flow.
    • Say

    "apply" to create the 4 tasks (--apply), or

    "apply with reconcile" to also mark API Authentication Flow completed.

    • After applying, running the same spec again plans 0 to create, so it is safe to repeat.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The ClickUp MCP server has a small daily quota. One workspace walk or a 40-task import can exhaust it, and then reads and writes are blocked for about 23 hours. ClickUp Scribe gives your agent the REST API instead (100+ requests a minute) with the safety rails a bulk job needs.

    Write

    • Create, update, or delete one task with every common field (status, priority, due/start dates, estimate, tags, assignees by id, email, or username)
    • Build a whole parent/subtask tree from one declarative JSON spec
    • --reconcile converges an existing board onto the spec: creates what is missing, updates only the fields the spec declares
    • Create folders and lists, skipping any that already exist

    Read

    • Walk the full hierarchy, including folderless lists that naive traversals silently drop
    • Every task and subtask on a list, re-nested, following pagination to the end
    • Name search, single-task detail, and export --as-spec to clone a board's shape onto another list

    Link git commits to tasks

    • ClickUp's API has no endpoint for the GitHub/Bitbucket panel, so commits posts one comment per task listing short SHA, subject, and a web link, deduped by full SHA
    • --rollup adds a per-subtask summary on the parent task

    Safe by design

    • Idempotent: tasks are matched by name across the whole list before anything is created, so a re-run creates only what is missing
    • Dry-run first: nothing is written without --apply
    • Statuses are validated against the list before the first write
    • Serialized, paced, and every command reports how many API calls it spent
    • Your token is never typed into chat: you store it once in your own terminal with a hidden prompt, and it is saved owner-only

    Ships as stdlib-only Python 3 plus a Windows PowerShell 5.1 twin of every command, so it runs on Linux, macOS, or Windows with nothing to install.

    Deliberately left to the ClickUp MCP or UI, which do these in one call each: comments (other than commit links), docs, chat, time tracking, attachments, creating tags, dependencies, moving or merging tasks, reminders, custom field values, and full-text search. Descriptions and assignees are not reconciled. Tasks are matched by name, so renaming in a spec creates a new task (use set to rename).

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Requires

    Clickup
    Python 3 (Linux, macOS, or Windows)
    Git

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files
    Environment Variables

    Allowed Hosts

    api.clickup.com
    Listed4 days ago

    What's inside

    Frequently Asked Questions

    For one task, do. Its daily quota is small, though: a bulk import or a workspace walk can use it up and block reads and writes for about 23 hours. This skill uses the REST API's per-minute limit instead.

    No. You run one command in your own terminal. It prompts without echoing, checks the token against the API, and stores it in a file only your user can read.

    No packages. Python 3 on any OS, or the built-in Windows PowerShell 5.1 on Windows.

    No. `apply` never deletes anything, with or without `--reconcile`. Plain `apply` only creates what is missing; `--reconcile` also updates status, priority, dates, estimate, and tags on existing tasks where they differ from the spec. The only way to delete is the separate `delete` command, which shows what would go (the task and its subtasks) and refuses without `--yes`.

    No. Each command prints its plan and results to the terminal, ending with how many API calls it spent. The only file it keeps is your stored token.

    ClickUp's API has no endpoint for that. Scribe posts an idempotent comment listing each commit with a link, and recommends a `Refs: CU-<task-id>` commit footer so future pushes link natively.

    New in APIs & Backend