Repository navigation
docs: enable Kapa WebMCP - #928
Conversation
Load the official Kapa website widget script with data-webmcp-enabled so visiting agents can call search_warp_knowledge_sources. Hide only the default floating widget button so the custom React Ask chat stays the human entry point. No consent flow changes; CSP already allowlists the widget host. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds a Kapa WebMCP loader to the docs head, centralizes the widget attributes, documents the public env behavior, and adds focused tests for conditional emission and attribute values.
Concerns
- No blocking concerns found in the changed files.
- Security pass: no diff-tied security findings; the new script origin is already allowed by the existing CSP, and the integration ID remains public configuration.
- Spec alignment: no approved or repository spec context was provided, so no spec-drift review was applicable.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
WebMCP only works with Website Widget integrations. Stop reading the custom React frontend ID for the widget script and require PUBLIC_KAPA_WEBSITE_WIDGET_INTEGRATION_ID instead. Keep data-button-hide so the custom Ask launcher stays the human chat entry point. Co-Authored-By: Warp <agent@warp.dev>
|
thanks @hongyi-chen! confirmed the new WebMCP protocol is enabled and working on the docs site. Agents can now search the docs autonomously.
|

Summary
search_warp_knowledge_sourcestool.PUBLIC_KAPA_WEBSITE_WIDGET_INTEGRATION_IDis configured, keeping it separate from the custom React chat integration ID.This follows Kapa's WebMCP launch guidance. Unsupported browsers ignore the WebMCP attribute and continue using the docs normally.
Related issues
None; source context: Kapa now supports WebMCP.
Validation
npm run test:kapa-webmcp- passed, 2/2 testsnpm run test:heading-vars- passed, 5/5 testsnpm run typecheckwith the Website Widget integration ID - passed with 0 errorsnpm run buildwith the Website Widget integration ID - passednpm run test:homepage-json-ld- passednpm run test:heading-tocs- passed, 3,381 TOC entries across 397 HTML filesdata-webmcp-enabled="true", anddata-button-hide="true"Screenshots
Not applicable; this intentionally adds no visual UI and preserves the existing custom Ask AI entry points.
Follow-ups
Docs WidgetWebsite Widget integration ID to production, preview, and development builds; no new Kapa integration is required.Co-Authored-By: Warp agent@warp.dev
Warp artifacts