Skip to content

Add implementation-status.md to track browser implementation status - #235

Open
beaufortfrancois wants to merge 5 commits into
webmachinelearning:mainfrom
beaufortfrancois:implementation-status
Open

Add implementation-status.md to track browser implementation status#235
beaufortfrancois wants to merge 5 commits into
webmachinelearning:mainfrom
beaufortfrancois:implementation-status

Conversation

@beaufortfrancois

Copy link
Copy Markdown
Contributor

This PR adds an implementation-status.md file to track the implementation status of WebMCP across browser engines (Brave, Chrome, Firefox, Safari).

Following established practices in other W3C Community Groups and Web Standards repositories (such as Web Bluetooth and WebGPU), maintaining a dedicated implementation status document provides a central, up-to-date reference for web developers, spec authors, and browser vendors.

This document will be updated periodically as browser support and standards positions evolve.

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

@bwalderman Let me know if there's anything we can add for Edge/Copilot.

@bwalderman

Copy link
Copy Markdown
Collaborator

@bwalderman Let me know if there's anything we can add for Edge/Copilot.

Thanks @beaufortfrancois , I've made a suggestion which includes Microsoft's origin trial link for WebMCP. Platform support is naturally at parity with Chromium. We don't have any links to share about in-browser Copilot integration at this time.

Comment thread implementation-status.md
beaufortfrancois and others added 2 commits August 1, 2026 08:02
Co-authored-by: Brandon Walderman <bwalderman@outlook.com>
Comment thread implementation-status.md Outdated
Co-authored-by: Victor Huang <xtrkil146@gmail.com>
@domfarolino

Copy link
Copy Markdown
Collaborator

Should this just be a section in the main explainer?

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

Should this just be a section in the main explainer?

I think it's better for discoverability to have it in a separate file.

@bwalderman

Copy link
Copy Markdown
Collaborator

Should this just be a section in the main explainer?

I think it's better for discoverability to have it in a separate file.

Maybe a link at the top of the main explainer?

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

Should this just be a section in the main explainer?

I think it's better for discoverability to have it in a separate file.

Maybe a link at the top of the main explainer?

Done

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

@domfarolino I think we're good now.

@Idan-Levin

Copy link
Copy Markdown

Thank you! We added it to our WebMCP directory. We鈥檙e also tracking two more adoption signals: agents that support WebMCP, and agent frameworks/infrastructure that support WebMCP.

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

Hey @Idan-Levin, I'm glad it's already useful.

May I note that "Goes GA in Chrome 157" isn't true. An origin trial phase is there to experiment. There's no contract to say it's going to ship after OT ends. See https://www.chromium.org/blink/origin-trials/running-an-origin-trial/ for more details.

@Idan-Levin

Copy link
Copy Markdown

@beaufortfrancois of course, will change now. It is based on this resource which might be worth updating: https://chromestatus.com/feature/5117755740913664

@beaufortfrancois

Copy link
Copy Markdown
Contributor Author

I agree this is definitely misleading

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants