Try WebMCP

Industry playground / SaaS operations

WebMCP saas project management demo.

Filter a small project board, update task status and inspect an accurate project summary.

CommerceTravelCustomer supportHealthcareReal estateSaaS operations
Checking browser support…Browser setup
SaaS operations playground

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-12
todo
Add registration lifecycle

SDK

SDK-08
in progress
Test unsupported browsers

Quality assurance

QA-04
todo

Project status

Local only
2todo
1in progress
0done
Tool inspector5 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.

Try a complete workflow

List open tasks, mark DOC-12 as done, then summarize the project.

Execution trace0 calls

Newest first. Example workflows are deterministic scripts, not LLM conversations.

No calls yet.

What this example teaches

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.

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