Clarify backend-inference, browser-executed tools as a WebMCP use case
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reading the WebMCP explainer and its sections on in-page agent APIs, discovery, and tool execution. Check how the explainer describes chat and backend orchestration, then decide whether the described flow fits the existing model. Done means clarifying the pattern in the explainer or adding a non-normative example, without proposing a relay protocol.
Written by the indexing model from the issue text.
Description
Our app provides a chat UI in the browser, while inference runs on our backend. The frontend sends the conversation and available WebMCP tool descriptions to the backend. When the backend returns a tool call, the frontend resolves it to a currently registered browser tool, executes it, and sends the result back for the next inference step.
Is this flow an intended use case for WebMCP’s in-page agent APIs? The existing APIs appear to provide browser-side discovery and execution, while leaving chat and backend orchestration to the application. Would it be useful to clarify this pattern in the explainer or add a non-normative example? We are not proposing a new relay protocol at this stage.
- 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
-
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
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webmachinelearning/webmcp#234 · 5 comments ·
Maintainers usually reply within 1 day
All issues in webmachinelearning/webmcp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cran-task-views/Survival#76 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
sandtable-ai/sandtable#300 ·
Maintainers usually reply within 1 day
-
content good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100