You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clarify backend-inference, browser-executed tools as a WebMCP use case #343
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.
Activity