What WebMCP is
WebMCP is a proposed web standard that lets a page offer tools to an AI agent running in the browser. Each tool has a name, a description, and a description of the input it takes. An agent finds the page's tools and calls them, much as it would call tools over the Model Context Protocol, except that the tools run inside the page itself.
That means an agent works on what you see: your open patch, in your own session, with no account, server, or upload involved. Everything it changes appears in PUNCHER as it lands.
WebMCP is a draft from the W3C Web Machine Learning Community Group. The API is still changing, and no browser turns it on for every site yet.
What an agent can do
PUNCHER offers nineteen tools. With them an agent can read the whole sequence and change almost anything you can change by hand.
| Tool | Does |
|---|---|
get_sequence | Reads everything: settings, voices and patterns, every step that holds anything, modulations, the transport, and the selection |
set_steps | Notes, transposition, rests and skips, jumps, and CC envelopes, on any number of steps |
set_voices | A voice's settings, its pattern, and its dots' options |
list_rhythm_presets | Lists the named rhythms of the voice's Presets panel, each with its group, pace, and dots |
apply_rhythm_preset | Puts a named rhythm on a voice, as choosing it in the Presets panel does |
set_euclidean | Spreads a number of hits as evenly as they go over a pattern, then turns it, as the panel's Hits, Length, and Rotate do |
transform_pattern | What the panel's Edit bar does: reverse, invert, mirror, double, halve, random, clear, or fill |
set_sequencer | Tempo, size, pace, direction, loop, scale, and the rest of the sequencer's settings |
set_modulations | Binds a setting to a CC, as its gear does, so step envelopes modulate it |
step_menu | What right-clicking a step offers: copy, paste, insert before or after, clear, delete |
play, pause, stop | The transport |
set_recording | The Record button, and the step recording goes into |
set_actions | Hold, Sync, Flip, and Transpose |
select_step | What clicking a step does: shows it, sounds it, or plays it next |
undo, redo | Edit → Undo and Redo |
clear_sequence | Empties the steps and resets the voices |
Steps, voices, and dots are numbered from 1, as PUNCHER shows them. Notes are named, with C4 as middle C. When a voice's dots are a preset or a Euclidean rhythm, the tools say which beside them, as the Presets panel does.
What stays yours
An agent cannot save, open, or export files, since those need your click in a file dialog. It cannot change Settings: MIDI outputs and inputs, themes, and SoundFonts. It can start a recording, but only you can play into it.
Browsers also start audio only after you click or press a key on the page, and an agent's call does not count. If the built-in synth is silent, click anywhere in PUNCHER once. play and get_sequence tell the agent when nothing would be heard.
Undo and safety
- Every request is one undo step. However much a single call changes, Edit → Undo (Ctrl + Z) takes it back in one go. A call that changes nothing leaves no entry.
- All or nothing. If any part of a request cannot be done, nothing changes, and the agent is told what to fix.
- You see it land. The first step or voice an agent edits is selected, so the change is in view.
- The patch stays in your browser. The tools act on the patch open in the page. The agent sees only what its calls return, mostly through
get_sequence, and PUNCHER's usage statistics record only which tool was called. Patch and file names can come from any file you opened, so the agent is told to treat them as untrusted content.
Turn it on
On punchermidi.app, use Chrome 149 or later. PUNCHER takes part in Chrome's WebMCP origin trial, which turns the API on for this site with nothing for you to set. The trial runs until March 2027.
Running PUNCHER on your own computer, or on another address, needs Chrome's testing flag instead:
- Open
chrome://flags/#enable-webmcp-testing. - Set WebMCP for testing to Enabled, and relaunch Chrome.
Browser availability is changing: Microsoft Edge also lists a WebMCP origin trial. These setup instructions target Chrome. PUNCHER exposes tools only when the page has the WebMCP API enabled; a browser name alone does not guarantee access. Without the API, the sequencer still works normally.
Try it
The quickest way to see the tools is Chrome's Model Context Tool Inspector extension:
- Install it from the Chrome Web Store.
- Open the editor, then click the extension's icon to open its side panel. It lists PUNCHER's tools with the input each takes.
- Choose
get_sequence, enter{}, and run it. The current patch comes back. - Choose
set_sequencerand run{ "tempo": 96, "scale": "A minor" }. The sequencer's settings over the grid follow at once, and Edit → Undo puts it back.
Then ask an agent for something musical, such as "Make a four-chord loop in A minor with a bass on voice 1 and an arpeggio on voice 2, then play it." A good agent reads the sequence first, then makes a few calls and plays the result.
If no tools appear
- Check that you are in Google Chrome 149 or later, not another browser.
- Reload the editor with Ctrl + Shift + R.
- In DevTools, open Application → Frames → top. Under Origin Trials, Chrome shows whether it accepted PUNCHER's token for WebMCP, and why not if it did not.
- Off punchermidi.app, including on your own computer, turn on the flag described in Turn it on.
Learn more
- WebMCP specification, the W3C Web Machine Learning Community Group's draft
- WebMCP on GitHub, with the explainer, issues, and proposals
- WebMCP early preview, Chrome's announcement and sign-up for its documentation and demos
- Origin trials, how Chrome tries out new features on real sites
- Model Context Tool Inspector, the extension's source and instructions
- Model Context Protocol, the protocol WebMCP is modeled on