No QA. No Jira. Just the board.

The task manager for vibe coders that don't QA.

You already ship in Cursor. You don't run a QA team, a staging ritual, or a ticket farm. TaskViber is the task manager in the agent: dump a session, know what to ship, mark it done.

Add to Cursor

TaskViber

Task manager MCP · vibe coders that don't QA

mcp oauth v0.2.0 
{
  "mcpServers": {
    "taskviber": {
      "url": "https://taskviber.com/mcp"
    }
  }
}
https://taskviber.com/mcp 
claude mcp add --transport http taskviber https://taskviber.com/mcp
Claude Code

Who it's for

You vibe. You ship. You don't QA. If someone has to “send it to QA,” you wanted a different product.

For you

Vibe coders that don't QA.

  • You live in Cursor or Claude Code. The chat is the work.
  • There is no QA person. You are the pipeline.
  • You want “what should I do?” not a sprint and a test plan.
  • Solo, pair, or a tiny team sharing one board.
Not this

Not a QA tool. Not Jira.

  • No test cases, no bug tracker for a QA team.
  • No web board. The agent is the UI. On purpose.
  • If you need Gantt charts, staging sign-off, or a PMO — keep Jira.

What you get

A board in the chat you already have. Capture the session. Know what to start. Close it when it ships — no QA handoff.

01 Capture

Turn a session into tasks.

Paste a Cursor transcript, meeting dump, or brain dump. You get 3–12 shippable tickets — not a 40-item graveyard.

02 Today

Know what to start.

Ask “what should I do?” You get one thing to do now, a few next, and the files to open.

03 Close

Keep the board honest.

“That's done.” “Park it.” “This is blocked.” Status moves. You never leave the editor.

Add it to Cursor. Keep talking.

One click, browser login, then the board is in the chat. Same install pattern as Stripe or Supabase MCP.

01

Add to Cursor

Click the button. Cursor connects TaskViber as a remote MCP. No API key in the snippet.

02

Log in

Create an account, or join a teammate with an invite code. One board per workspace.

03

Ask

“What should I do?” The agent reads your board and tells you what to start.

Talk like you already talk.

You don't learn a UI. You tell the agent; it updates the board.

YouThe agent
“what can you do?”help
“what should I do?”start
paste a long chatturn it into tasks
“add these: …”add_tasks
“that's done”complete_task
“park it”park to backlog
“invite jane@…”invite

What the agent can call

A small MCP surface. Your agent uses these. You don't have to.

startWhat to do now. Call this first.
helpThe pitch — not a raw tools dump.
ingest_transcriptStore a messy chat dump.
confirm_tasksWrite 3–12 shippable tickets.
add_tasksFast expand from titles.
create_taskOne ticket, one outcome.
daily_briefing3–7 focus items + status.
complete_taskThat's done.
update_taskPark, block, retitle.
add_noteAppend context. Keep status.
list_tasksFilter the board.
get_taskOne id, e.g. T-014.