AI Prompt to Generate a Weekly Project Status Report From ClickUp via MCP

0 views Updated Oct 12, 2026

This AI prompt turns raw task data sitting inside ClickUp into a clear, readable weekly status report, using ClickUp's MCP server to pull live task, status, and due-date information directly into the conversation instead of asking you to copy and paste from the ClickUp app. It's built for project managers, team leads, and freelancers who run weekly check-ins or client updates and are tired of manually scanning boards to figure out what actually moved.

Once ClickUp's MCP server is connected, the model can read a space, folder, or list and group tasks by status, flag anything overdue or blocked, and summarize what changed since the last report, all without you re-typing task names or statuses into the prompt yourself. The prompt below is written so the model asks for the specific ClickUp scope (a list ID, folder, or workspace) before pulling data, which keeps the report focused and avoids pulling in unrelated projects.

Because a status report is only useful if it's phrased consistently and sent to the right audience every time, it also helps to tighten the instructions themselves before you rely on them weekly. Running this template through a tool like Prompt Builder first can turn a loose description of "summarize my ClickUp tasks" into the kind of structured, repeatable instruction set used below.

Prompt template

prompt-template

368 tokens

ROLE: You are a project status reporting assistant with access to ClickUp through its MCP server integration. CONTEXT: Workspace or list to report on: [CLICKUP_LIST_OR_FOLDER_NAME_OR_ID] Reporting period: [DATE_RANGE, e.g. "October 6-12, 2026"] Audience for this report: [CLIENT / INTERNAL TEAM / MANAGER] Team or project name: [PROJECT_NAME] TASK: 1. Use the ClickUp MCP connection to pull all tasks in the specified list or folder that were updated, completed, or due during the reporting period. 2. Group the tasks into exactly these four sections: Completed This Period, In Progress, Blocked or Overdue, and Not Started. 3. For each task, include its name, assignee (if available), and due date. 4. In the Blocked or Overdue section, briefly note why each task appears to be stuck if that information is available from comments or status fields. 5. Write a 2-3 sentence executive summary at the top of the report before the detailed sections. 6. If a task's status or details are ambiguous or missing from ClickUp, say so explicitly rather than guessing. CONSTRAINTS: - Do not include tasks outside the specified list, folder, or date range. - Do not fabricate task details, assignees, or comments that aren't present in the ClickUp data. - Keep the tone factual and concise; avoid filler phrases like "great progress this week." OUTPUT FORMAT: Return the report in this structure: [EXECUTIVE SUMMARY - 2-3 sentences] [COMPLETED THIS PERIOD - bulleted list] [IN PROGRESS - bulleted list] [BLOCKED OR OVERDUE - bulleted list with reason noted] [NOT STARTED - bulleted list]

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input

67 tokens

Workspace or list to report on: "Website Redesign" list in the Marketing folder Reporting period: October 6-12, 2026 Audience for this report: Client Team or project name: Acme Co. Website Redesign Please pull the current task data from ClickUp and generate this week's status report.

When to use it

You run a recurring weekly or biweekly status update for a client, manager, or internal team
Your ClickUp workspace has enough tasks that scrolling through the board to write a summary takes real time
You need the same report format every week so stakeholders can scan it quickly without re-learning the layout
You want overdue or blocked tasks surfaced automatically instead of discovering them in a standup

Best practices

Give the model a specific ClickUp list, folder, or space ID rather than your whole workspace, so the report doesn't mix unrelated projects together
Ask for the report to separate "completed this week," "in progress," and "blocked or overdue" rather than one flat list, since mixed statuses are harder to scan
Have the model call out the date range explicitly (e.g. "for the week of Oct 6-12") so recipients know exactly what window the report covers
Review the first two or three reports closely before treating the format as final, since MCP tool access can pull in subtasks or archived items you didn't intend to include

Common mistakes

Asking for a report across an entire workspace instead of a scoped list, which produces a bloated summary nobody reads
Not specifying how overdue tasks should be flagged, so they get buried in the middle of the report instead of called out at the top
Treating the MCP-generated report as final without checking it against ClickUp directly the first few times, since task names and custom fields can be summarized imprecisely
Reusing the same report for both a client and an internal team, when each audience needs a different level of task-level detail

FAQs

How do I connect ClickUp's MCP server to ChatGPT or Claude?

You add ClickUp's MCP server through your AI client's connector or integrations settings using the server URL and an API token generated from your ClickUp account, after which the model can read task data in your authorized workspaces during the conversation.

Can this prompt work without MCP, just by pasting ClickUp data manually?

Yes, if you copy task names, statuses, and due dates into the prompt yourself, the model can still generate the same report structure; MCP just removes the manual copy-paste step and keeps the data current.

Will the AI see every task in my ClickUp workspace?

Only the lists, folders, or spaces your MCP connection has been granted access to, and only what you specify in the prompt's scope field, so narrowing the request to one list is both faster and more accurate.

What should I do if the status report misses or misreads a task?

Treat the first few reports as a check against ClickUp directly, since MCP tool calls summarize underlying field data and can occasionally miss custom fields or nested subtasks that aren't part of the standard task view.

Which Cuelara tool can help me build a stronger version of this prompt?

Prompt Builder — turns a plain description like "summarize my ClickUp tasks weekly" into a fully structured prompt with the role, constraints, and output format filled in. Intelligence Score — grades this prompt's clarity and specificity before you rely on it for a recurring report, flagging vague instructions that could cause inconsistent summaries.

Found this prompt useful? Share it.

More in Productivity

Productivity

AI Prompt to Organize and Prioritize Tasks via Asana's MCP Server

This Asana MCP prompt is for anyone who manages a busy task list in Asana and wants an AI assistant to pull that data directly through Asana…

ROLE: You are a task prioritization assistant with access to an Asana MCP server connection.

CONTEXT:
- Workspace: [ASANA_WORKSPACE_NAME]
- Projects to include: [PROJECT_NAME_1, PROJECT_NAME_2]
- My role: [YOUR_ROLE, e.g., project manager, individual contributor]
- Time horizon: [e.g., tasks due in the next 7 days]

INSTRUCTIONS:
1. Use the Asana MCP connection to retrieve open (non-completed) tasks from the projects listed above.
2. Pull the following fields for each task: task name, due date, assignee, project, and any custom priority field.
3. Exclude tasks that are marked complete, archived, or outside the specified time horizon.
4. Rank the tasks using this method: [PRIORITIZATION_RULE, e.g., overdue tasks first, then high-impact tasks, then soonest due date].
5. Group the ranked tasks under clear headings: Overdue, Due Today, Due This Week, Upcoming.
6. Flag any task that is missing a due date or assignee as "needs clarification."

CONSTRAINTS:
- Do not invent task data; only use what the MCP connection returns.
- If the MCP call fails or returns no data, say so plainly instead of guessing.
- Keep task names exactly as they appear in Asana.

OUTPUT FORMAT:
A ranked list grouped by the headings above, with each task shown as:
[Task name] — Due: [date] — Assignee: [name] — Reason: [one-line justification for its rank]
End with a 2-3 sentence summary of what needs immediate attention.

Productivity

ChatGPT Prompt to Find and Shortlist Freelancers via Upwork's MCP Server

This is a prompt for clients using Upwork's MCP server , which connects the Upwork marketplace directly to ChatGPT, Claude, Cursor, and any…

I'm hiring on Upwork through your MCP connection. Here's the role:

Role: [JOB TITLE]
Must-have skills: [SKILL 1, SKILL 2, SKILL 3]
Nice-to-have skills: [OPTIONAL SKILLS]
Budget range: [HOURLY OR FIXED RANGE]
Timezone / availability needs: [OVERLAP REQUIRED, IF ANY]
Deal-breakers: [ANYTHING THAT SHOULD AUTOMATICALLY RULE SOMEONE OUT]

Using the Upwork MCP connection:
1. Search for freelancers matching this brief.
2. Return a shortlist of 3-5 candidates.
3. For each one, give their top relevant experience and one sentence on why they fit this specific brief.
4. Flag anyone who's a strong skill match but falls outside my budget or timezone needs, separately.
5. Do not send any messages or offers yet — just show me the shortlist first.

Productivity

ChatGPT Prompt to Turn a Messy Brain Dump Into an Organized Project Plan

This ChatGPT prompt to turn a brain dump into a project plan takes a raw, unordered list of thoughts — the kind you type out in five minutes…

ROLE: You are a project planning assistant that turns unstructured notes into an organized project plan.

CONTEXT:
- Project name: [PROJECT NAME]
- Raw brain dump (unedited): [PASTE YOUR NOTES, BULLET POINTS, OR STREAM-OF-CONSCIOUSNESS TEXT]
- Team members involved, if known: [NAMES OR ROLES]
- Target deadline, if any: [DATE OR TIMEFRAME]

TASK:
1. Read through the raw notes and group related ideas into 3-6 themes or phases
2. For each phase, list the specific tasks that belong to it, pulled from the notes
3. Assign an owner to each task if a name or role was mentioned; otherwise mark it "Unassigned"
4. Flag any item from the notes that was too vague to turn into an actionable task
5. Note any dependency where one task must finish before another can start

CONSTRAINTS:
- Do not invent tasks that weren't implied by the notes
- Do not merge two distinct ideas into one task just to shorten the list

OUTPUT FORMAT:
A phased project plan with phase names as headers, tasks as a checklist under each, and a separate "Needs Clarification" section at the end.