Plavement
First-class API and MCP server included

Issue tracking that moves at your pace

Plavement is a fast, focused issue tracker for product teams. Projects, cycles, and a kanban board you'll actually want to use — every action available via REST API and MCP server, so your agents work alongside your team.

Live

Watch work move through the board

Issues flow naturally from Backlog to Done while AppLab coding agents report live updates into the same operating loop. Teams can manage agent work like regular product work, following SDLC patterns from planning through review and release.

  • Auto-numbered identifiers per organization (PLA-1247)
  • AppLab agent updates captured alongside human work
  • Real-time mutations via REST API or MCP

AppLab

Track coding agents as first-class teammates

Agent activity is visible as it happens: implementation notes, blockers, review handoffs, and deployment signals stay attached to the work item instead of disappearing into chat history.

  • Live agent status updates for each issue
  • Human review checkpoints before code moves forward
  • Shared context for product, design, and engineering

SDLC

Run agent work through a predictable lifecycle

Plan the work, let agents build in bounded steps, route changes through review, and ship only when the final state is clear. Plavement keeps the lifecycle visible without forcing teams into heavyweight process.

  • Plan, build, review, and ship stages
  • Clear ownership for agent-generated changes
  • Audit-friendly work history from request to release

Orchestration

Coordinate multiple coding agents without losing the thread

Use boards, cycles, and labels to coordinate parallel agents across design, implementation, testing, and release work. Every agent task remains tied to the same source of truth your team already uses.

  • Parallel agent lanes for focused responsibilities
  • Cycle planning for human and agent capacity
  • MCP-ready actions for creating, updating, and moving work

Handoffs

Keep every agent handoff attached to the issue

When work moves from a product request to a spec, coding agent, pull request, and review, Plavement keeps each handoff visible. The issue remains the durable record instead of a loose trail of messages.

  • Structured handoffs between humans and agents
  • PR and review context attached to the original request
  • Clear next owner at every step

Quality

Gate agent changes before they reach users

Treat agent output like production engineering work. Type checks, lint, tests, review, and deploy gates give teams a shared view of what has passed and what still needs attention.

  • Quality gates for every agent-generated change
  • Review-ready status before release decisions
  • A visible trail from failing check to fixed issue

Release

Move from preview to production with the same source of truth

Track previews, staging updates, and production releases without leaving the board. Teams can see which agent work is still experimental and which changes are ready to ship.

  • Preview, staging, and production lanes
  • Release state tied back to issue history
  • MCP-ready updates for automated release steps

Operating model

A lightweight SDLC for people and agents

Plavement keeps the work loop visible without turning your team into process administrators. Every request has a clear path from intake to verification.

1

Intake

Capture requests, bugs, and agent tasks with stable issue IDs.

2

Scope

Attach project, cycle, label, owner, and acceptance context before work starts.

3

Execute

Let humans and coding agents move work through the same visible states.

4

Verify

Track reviews, checks, comments, and release readiness on the issue.

API-first

Built for the tools already doing the work

REST and MCP access make Plavement easy to wire into code assistants, internal automations, dashboards, and release systems.

REST API

Create, update, move, comment, and search issues from your own tools.

MCP server

Expose project work directly to coding agents without screen scraping.

Realtime updates

Keep boards and issue detail views current while work changes.

agent-workflow.ts
await plavement.issues.create({
  project: "AppLab",
  title: "Add OAuth callback",
  assignee: "coding-agent",
  cycle: "May launch",
})

await plavement.issues.move("PLA-1284", {
  status: "in_review",
  comment: "Patch pushed, checks running."
})