In-page WebMCP

What it is

When a browser exposes WebMCP (document.modelContext), Aden registers tools for the page you are on. Agents can read public product copy, a public artist or track page, or (after you sign in) the same workspace mutations the UI uses. They never type passwords, 2FA, passkeys, captcha, or payment.

Using it

1. Chrome 153+, which ships the API behind an origin trial, or another client that implements WebMCP. Earlier builds need chrome://flags/#enable-webmcp-testing.
2. Open Aden. Tools appear only when document.modelContext exists. Missing the API is a no-op. Registration happens after the page hydrates.
3. Marketing (/, /features, /pricing): get_product_overview, get_pricing, get_page_markdown. Aden copy only. No competitor tables.
4. Public artist (/@you): get_artist, list_public_releases, list_public_shows. If booking is on, request_booking asks you to confirm in the page, then uses the public booking form.
5. Public track (/@you/track/...): get_track.
6. Signed out on app routes: get_session tells you to sign in. Mutating workspace tools stop with the same message. They do not fill the login form.
7. After you sign in: list or switch teams and organisations, invite with the same in-page confirm as the UI, then open a track in the app and add milestones.
8. Anywhere under /app, the full Aden tool catalog is on the page: track, album, playlist, version, track_comment, todo, milestone, event, tour, share, stats and the rest, each with an action (create, updateStatus, updateReleaseDate, updateMetadata, setVisibility, createArtworkUpload, addTracks, …). These are the same tools the MCP server offers. Not sure which one? aden_find_tools searches them, aden_describe_tool returns one action's exact schema.
9. Moving around: list_pages names every sidebar page, navigate opens a page, a path, or a track/album/playlist/mix by id, and toggle_details_panel shows or hides the right-hand details panel.
10. Deleting, removing, cancelling or clearing anything asks you to confirm on the page first, like the UI's own delete buttons.