Skip to content

docs: enable Kapa WebMCP - #928

Open
dannyneira wants to merge 1 commit into
mainfrom
danny/enable-kapa-webmcp
Open

dannyneira wants to merge 1 commit into
mainfrom
danny/enable-kapa-webmcp

Conversation

@dannyneira

Copy link
Copy Markdown
Member

Summary

  • Enable Kapa WebMCP across the docs site so supported visiting agents can call the read-only search_warp_knowledge_sources tool.
  • Load Kapa's official Website Widget script only when PUBLIC_KAPA_INTEGRATION_ID is configured.
  • Hide Kapa's default floating button so Warp's existing custom React Ask AI experience remains the only human-facing chat entry point.
  • Add focused tests for conditional script emission and the required WebMCP attributes.

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 tests
  • npm run test:heading-vars - passed, 5/5 tests
  • npm run typecheck - passed with 0 errors
  • npm run build with PUBLIC_KAPA_INTEGRATION_ID configured - passed
  • npm run test:homepage-json-ld - passed
  • npm run test:heading-tocs - passed, 3,381 TOC entries across 397 HTML files
  • Trunk checks on all touched files - passed
  • Generated HTML contains exactly one Kapa widget script with data-webmcp-enabled="true" and data-button-hide="true"

Screenshots

Not applicable; this intentionally adds no visual UI and preserves the existing custom Ask AI entry points.

Follow-ups

  • Runtime tool registration depends on WebMCP-capable browsers and agents. Unsupported browsers ignore the attribute.
  • Kapa WebMCP calls retain Kapa's existing captcha behavior and analytics.

Co-Authored-By: Warp agent@warp.dev

Warp artifacts

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>
@cla-bot cla-bot Bot added the cla-signed label Oct 16, 2026
@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Oct 16, 2026 8:44pm UTC

Request Review

@warp-for-oss

warp-for-oss Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

@dannyneira

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 /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

This branch was successfully deployed

1 active deployment
Preview — c54900b3 Deployed Oct 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant