This page walks you through the one-time setup, then shows you what to do with the connection.
Total setup time is about 30 seconds: one terminal command, one browser sign-in.
Once connected, Claude Code can read, create, update, and complete your tasks — and you can hand off drafts, research, and planning for it to work on using your own AI subscription.
Using a different MCP-capable client (Claude Desktop, ChatGPT, Cursor)? The setup is similar — see the MCP setup guide for client-specific instructions.
Before you begin
You'll need two things:
Node.js 18 or later — Claude Code installs via npm, which ships with Node. Check with node --version; if you don't have it (or it's older than 18), grab the latest from nodejs.org.
A Tasks Wiz account — used for the browser sign-in in step 3. Sign up or sign in if you haven't already.
1 Install Claude Code
Check whether it's already installed:
claude --version
If you see command not found, install it with npm:
npm install -g @anthropic-ai/claude-code
2 Add the Tasks Wiz MCP server
Run this once — the -s user flag makes Tasks Wiz available in every project on your machine:
claude mcp add --transport http tasks-wiz https://api.tasks-wiz.com/mcp -s user
3 Start Claude Code and sign in
claude
Then ask Claude to use Tasks Wiz, for example:
show me my tasks from tasks-wiz
Your browser will open to auth.tasks-wiz.com — the same
sign-in page you use for the website. After you sign in, Claude Code
stores a refresh token locally and silently keeps the connection alive
for around 30 days. You will not be prompted again unless you change
your password.
Nothing to copy-paste. No JWT to lift from devtools. No header to
type. Sign in once in the browser and you're done.
How to use it
Once connected, you can ask Claude Code about Tasks Wiz in plain English at any prompt.
The fastest way to verify the connection is live:
what's due today on tasks-wiz?
Below are the workflows that make Tasks Wiz + Claude actually different from a regular to-do list — start with the headline workflow.
The headline workflow: let AI work your tasks
Tag tasks in Tasks Wiz with the sparkle, run one slash-prompt in Claude Code, and the agent drafts, researches, or plans each one — writing its results back into the task for you to Accept, Refine, or Reject.
In Tasks Wiz, click the sparkle on any task that's a draft, research, plan, or summary you'd normally do yourself.
Optionally expand Add context on the create form and paste the source material (an email thread, an article URL, a JD).
In Claude Code, run the work-on-my-tasks slash-prompt:
/mcp__tasks-wiz__work-on-my-tasks
It loads our pre-tuned system prompt and works through up to 5 tagged tasks per invocation.
Open Tasks Wiz, see the "Needs review" badge, and hit Accept, Refine, or Reject on each result.
Variations on the same workflow:
"Work on my tagged tasks, but only the email drafts — leave research for later."
After hitting Refine in Tasks Wiz: "continue" — Claude reads the running thread (including your refinement note) and produces a fresh draft.
"List my delegatable tasks and tell me which ones you can finish in this session vs. ones you'd need more context for — don't start writing yet."
"For the next task on my queue, do all the research first and show me the comparison table; ask me which option to draft a recommendation for before continuing."
You only pay for the AI subscription you already have — Tasks Wiz never calls a paid LLM on your behalf. Claude Code uses its own (your) tokens for the actual work.
More things to try
Quick commands
Plain-English CRUD — a good first sanity check that the connection is live.
"What's due today? Group it by priority and suggest an order to tackle them in."
"Add a task: pay credit card bill, due Friday, high priority."
"Create tasks for these grocery items, all due Saturday: milk, eggs, sourdough, blueberries."
"Push every overdue task forward by one week."
"What did I finish last week? Summarise the themes."
"Add 'review weekly goals' as a weekly recurring task on Sunday mornings."
Capture from anywhere
Claude can read files, paste, and screenshots — turn any of them into structured tasks in one shot.
"Read meeting-notes.md and create a task for every action item assigned to me, using the dates I mentioned and a sensible priority."
"Here are my notes from a call (pasted below). Pull out the action items, infer due dates from phrases like 'by Friday', and add them: …"
"I'll attach a photo of my whiteboard — create one task per sticky note. Work items go in the work category, personal in personal."
"Look at the TODO comments in the files I've staged for commit. Turn each one into a work task due this week."
Plan your day intelligently
Stop staring at a flat list — Claude reads today's open tasks and proposes a time-blocked schedule (mornings = high-priority, afternoons = admin) before applying anything. Confirm and Claude writes the schedule into the Day Planner.
/mcp__tasks-wiz__plan-my-day
Or skip the slash-prompt and ask in your own words:
"I have 4 hours of focus time before lunch. Pick the highest-impact tasks from my open list that fit and schedule them in 30-min blocks."
"Move every work task scheduled for today into the morning, personal tasks into the afternoon, and leave a 1-hour gap at noon."
"My energy crashes after 3pm — reshuffle today so anything requiring deep focus lands before 1pm and admin/email tasks go after lunch."
Cross-tool magic
The real superpower: Claude can combine your tasks with git, files, the web, and other MCP servers in a single prompt.
"Read CLAUDE.md and the open issues in this repo, then create tasks for anything on the roadmap I haven't logged yet."
"Check my git log for the last 7 days, cross-reference with my open tasks, and complete any task whose work I've clearly already shipped."
"Pull the unchecked items from this project's README's TODO section and turn each one into a work task due this sprint."
"Look at the failing tests in the latest CI run, and create a high-priority task for each one with the test name and file path in the notes."
Bulk cleanup with judgement
Bulk operations that aren't dumb — Claude reads, decides, and asks before destructive moves.
"Find duplicates in my open tasks (close paraphrases count). Keep the earliest, delete the rest, and show me each pair before deleting."
"For everything overdue more than 2 weeks: ask me task-by-task whether to push to next Monday or delete."
"Re-prioritize my open list: anything tied to the launch on the 20th becomes high priority; anything that mentions 'someday' or 'maybe' gets dropped to low."
"Audit my recurring tasks — flag any I haven't actually completed in the last month so I can decide whether to stop the series."
Reflect & review
Your activity log + Claude's reasoning = a coach you didn't have before.
"What did I finish last week? Group by category, call out anything that took multiple reschedules, and suggest one habit to try next week."
"I keep deferring 'gym' tasks. Show me how often over the last month and suggest a smaller version of the habit that might actually stick."
"Write me a weekly retro in markdown: what shipped, what slipped, what I should ditch. Save it to retro-$(date).md."
What Claude can do
Exactly what you can do in the Tasks Wiz UI — read, create, update,
complete, and delete your tasks, plus read your activity log.
Nothing else. Claude cannot see other users' data, your email, your
password, or anything outside the Tasks Wiz API.
To run read-only, type /mcp inside a Claude Code session
and toggle off create_task, update_task,
complete_task, and delete_task.
To revoke access from any device — including a lost laptop — change
your Tasks Wiz password from the Forgot Password link on the login
page. That invalidates every refresh token immediately.
Troubleshooting
Most setup problems are caused by a stale registration or cached token shadowing the fresh OAuth flow. Try the steps below if:
You ran claude mcp add and it succeeded, but the tasks-wiz tools never appear inside Claude.
Tool calls return 401 Unauthorized even after you've signed in via the browser.
You're switching from an older paste-the-JWT setup to the new browser OAuth flow.
Reset and re-add
Remove every Claude Code CLI registration of tasks-wiz (covers all three scopes; harmless if a scope didn't have one):
claude mcp remove tasks-wiz -s user; claude mcp remove tasks-wiz -s local; claude mcp remove tasks-wiz -s project
Confirm tasks-wiz is gone from the list:
claude mcp list
Then re-run the claude mcp add command from step 2 above and sign in again.
Last resort: reinstall Claude Code
Step 1 — Reinstall the Claude Code binary. Fixes corrupted installs, version mismatches, and broken global symlinks. Your MCP servers, project history, and sessions are not touched.
After it finishes, re-run the reset commands above and re-add tasks-wiz.
Step 2 (only if Step 1 didn't help) — Wipe Claude Code's config. This is the nuclear option.
Warning — this deletes everything Claude Code stores locally:
every MCP server (not just tasks-wiz), every project's per-folder
conversation history, all custom commands, all sessions, and any cached
OAuth tokens. Skip this step if you have other MCP servers or work history
you want to keep.
rm -rf ~/.claude.json ~/.claude/
Then run the install + add commands from steps 1 and 2 of the setup above. If you're still stuck after that, get in touch and we'll help.
Other common issues
Force a fresh browser sign-in (instead of reusing your Cognito session cookie):
open "https://auth.tasks-wiz.com/logout?client_id=4i60kb1rrb92016t1radosbifc&logout_uri=https://www.tasks-wiz.com/"
HTTP 429 / "throttled" mid-bulk-edit: the MCP endpoint is rate-limited at 5 requests/second with a max batch of 10 messages. Ask Claude to do the work in smaller batches.