In-page WebMCP

What it is

When a browser exposes WebMCP (document.modelContext), Aden registers tools for the page you are on. An agent can read session, teams, organisations, and tracks, and can run the same mutations the UI already uses. It never types passwords, 2FA, passkeys, captcha, or payment.

Using it

1. Chrome 149+ with chrome://flags/#enable-webmcp-testing enabled, or another client that implements WebMCP.
2. Open Aden. Tools appear only when document.modelContext exists. Missing the API is a no-op.
3. Signed out: get_session tells you to sign in on the page. Mutating tools stop with the same message. They do not fill the login form.
4. Signup: start_signup / register prefills public fields (email, name, invite code) then returns a needs-human error so you finish password and any 2FA yourself.
5. After you sign in: list or switch teams and organisations, invite with the same in-page confirm as the UI, then open a track and add milestones.