App -> Agent explicit integration/manifest?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, web-dev
Research direction
Start by reading the WebMCP proposal and discussion around registering tools and how agents invoke them; the issue does not name specific files or tests. Identify whether browser UI for choosing an agent provider and a way for pages to detect available handlers belong in scope. Done means the scope and expected integration flow are clearly decided.
Written by the indexing model from the issue text.
Description
As best as I can tell, most of WebMCP is around the plumbing of exposing in-page capabilities through an API to Agent(s) (either external, browser-supplied or in-page).
Is the page->agent triggering flow in-scope (or did I miss it)?
I "built" a CVE analysis tool with built in LLM for exploring CVE data (mostly because I had some questions I wanted to answer, I had tokens to burn and it felt like a fun exercise). Instead of building out a complicated UI for filtering the data and running the queries, I thought it would be a lot easier to just use a LLM to do all of that and just use a chat box.
Right now the built-in LLM runs on a single consumer GPU in my house and runs a pretty small Qwen model (tested best for generating the SQL queries) but I also have subscriptions to most of the AI providers, browser extensions installed for a lot of them and the "Ask Gemini" browser-provided UI for my Gemini subscription. Any one of these would be orders-of-magnitude better than the LLM I provide directly.
I can expose a WebMCP endpoint for everything the app-provided LLM uses and it should have 100% access to run the analysis engine but it doesn't feel like there are plans for how to make that a seamless experience for the user.
Optimally, registering the WebMCP tools would be able to trigger some sort of browser UI that lets the user pick a provider to use (extension or browser native UI) but it would be cleanest if I could know that the current user's browser had some way to handle that so I could offer UI to steer them to click a button to use their own LLM and hide the built-in chat window when the external chat is being used.
- Dominant language
- Bikeshed
- Stars
- 4.7k
- Forks
- 328
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 16
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from webmachinelearning/webmcp
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
webmachinelearning/webmcp#360 ·
Maintainers usually reply within 1 day
-
Say how an agent should weigh annotations that the page wrote about itselfPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
webmachinelearning/webmcp#353 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#343 · 1 reaction ·
Maintainers usually reply within 1 day
-
Agenda+ i18n-tracker
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
webmachinelearning/webmcp#273 · 3 comments ·
Maintainers usually reply within 1 day
-
a11y-tracker Agenda+
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#272 · 4 comments · 2 reactions ·
Maintainers usually reply within 1 day
All issues in webmachinelearning/webmcp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
StellarState/SS-backend#712 ·
Maintainers usually reply within 1 day
-
area: api effort: S P2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ferenyl/azuredevopstui#12 ·
-
area: backend bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
snapotter-hq/SnapOtter#3473 ·
Maintainers usually reply within 1 day
-
backroom bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ditto-assistant/ditto-subnet#3069 ·
Maintainers usually reply within 1 day
-
harlan-agent-ready-to-implement routine:ci-review
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
harlan-zw/unlighthouse#455 · 2 comments ·
Maintainers usually reply within 1 day