Documentation
WebMCP tools that share visible application state
Compass registers ten typed page-side tools. Every handler validates its input and re-checks the active Context Pack and live permissions before reading or writing IndexedDB.
Judge quick start
- Open the home page in a WebMCP-capable browser.
- On a clean browser, confirm the fictional Atlas Launch demo initialized automatically.
- Confirm the Atlas Launch Context Pack is active.
- Ask the agent to search for unresolved launch blockers.
- Ask it to create a high-priority task for the most urgent blocker.
- Watch the task and agent activity appear in the visible interface.
- Disable Allow write and confirm write tools disappear.
When an agent should use Compass
Use Compass when the person asks an agent to find, summarize, create, update, connect, or complete records inside the currently active Context Pack. Start with get_active_context. Do not use Compass to reach cloud accounts, external APIs, files outside this browser origin, or any item the active pack and permission switches do not expose.
Read tools
- get_active_context
- list_spaces
- search_personal_context
- get_personal_item
- list_recent_activity
Write tools
- create_personal_item
- update_personal_item
- complete_task
- link_personal_items
- create_context_pack
Safety properties
Tool schemas reject unknown fields. Stored personal content is returned as untrusted data, not instructions. Read and write tools unregister when their visible permission switch is disabled, while every handler repeats the same authorization check to protect against stale or in-flight calls. Creating a Context Pack never activates it; activation remains a human-only action.
Source and demo
Review the public MIT-licensed source or watch the narrated demo.