Replies: 2 comments
|
I documented the current boundary in the DeepSeek Harness Handbook: today's Host-composed Streamable HTTP MCP client should not be read as browser-native webMCP support. The note lists origin, consent, lifecycle, credential, prompt-injection, naming, and teardown contracts a future implementation would need: https://github.com/sandbaseai/deepseek-harness-handbook/blob/main/docs/en/integrations/mcp.md Published in v0.5.428: https://github.com/sandbaseai/deepseek-harness-handbook/releases/tag/v0.5.428 |
|
I implemented this in DeepDeck, an unofficial desktop client built on Harness. The browser discovers registered WebMCP tools and lets the site agent call them through Harness. A Builder mode also lets the agent explore a site, generate missing tools, verify them, and save them for later visits. This currently requires DeepDeck's Electron browser and Cordis plugins; it is not a claim that upstream Harness's HTTP MCP client already supports browser WebMCP. Website-provided and generated tools are shown separately. I posted the implementation overview and four screenshots here, with Chinese and English versions: DeepSeek Harness + WebMCP + Builder = Efficient Computer Use. |
Uh oh!
There was an error while loading. Please reload this page.
Will dsh support webMCP?
All reactions