Validate the transition target
The handler accepts only known task IDs and status values. A production app must additionally check workspace membership and update rights.
INDUSTRY PLAYGROUND / SAAS OPERATIONS
WebMCP saas project management demo.
Filter a small project board, update task status and inspect an accurate project summary.
Checking browser support…Browser setup
SaaS operations playground
FICTIONAL DATA
ORBIT / PROJECTS
Move the work forward.
Filter a small project board, update task status and inspect an accurate project summary.
3 tasksShared page state
Publish API quickstart
Documentation
DOC-12todo
Add registration lifecycle
SDK
SDK-08in progress
Test unsupported browsers
Quality assurance
QA-04todo
TOOL INSPECTOR 5 tools
Filter the visible sample project tasks by status.
LAST RESULT
// Run a tool to inspect its result.
Run tool calls the local handler directly. Native agent calls appear as “Native WebMCP” in the trace.
Execution trace 0 calls
Newest first. Example workflows are deterministic scripts, not LLM conversations.
No calls yet.
WHAT THIS EXAMPLE TEACHES
Summaries should read current state
Counts are computed from the board after each change, so tool output stays aligned with the interface. No generated summary is needed for this structured result.
COMMON QUESTIONS
Does this connect to Asana, Linear or Jira?
No. It demonstrates the pattern with a small in-memory board.
Will updates survive a refresh?
No. This demo deliberately resets on page reload. Production task tools should use your existing persistence layer.
API references reviewed September 7, 2026. Chrome imperative API ↗