FAQ

Is this an official Contentstack package?

No. @timbenniks/contentstack-webmcp is a personal, experimental project by Tim Benniks. It is not published, maintained, or supported by Contentstack.

Why not build this into the Delivery SDK?

WebMCP requires browser-native tool registration, JSON schemas, lifecycle management, and cleanup — a layer above HTTP request interception. Delivery SDK plugins shape HTTP traffic; WebMCP shapes browser capabilities.

Will this replace @contentstack/mcp?

No. Different use case: in-browser agents on public sites vs external MCP clients. See comparison.

Is direct mode safe for production?

Not as the default. Proxy mode keeps delivery tokens server-side and centralizes controls. See Execution modes.

Is React or Next.js required?

No. The default path is framework-free. React and Next.js are optional adapters.

Does proxy mode require a stack on the client?

No. Pass { mode: 'proxy', contentTypes } only. Credentials belong in the server handler config. See Credentials.

How do I run custom Contentstack queries?

Three paths:

1. createCdaClient() — SDK access in custom tools
2. customRoutes — custom server proxy endpoints
3. contentTypes[].serialize — transform built-in tool output

See Custom CDA queries.

How do I disable WebMCP?

Set CONTENTSTACK_WEBMCP_ENABLED=false. See Environment variables.

Why aren't tools showing in DevTools?

1. Confirm document.modelContext exists — join the Chrome origin trial (149+) or enable #enable-webmcp-testing. This package does not use the deprecated navigator.modelContext.
2. Check isWebMcpSupported() returns true
3. Verify CONTENTSTACK_WEBMCP_ENABLED is not false
4. Look for registration errors in the dev console (development builds only)

Can I use this with draft/preview content?

Not in v0.1. Preview-token support is planned as future gated work.

Where is the reference implementation?

Live on developers.contentstack.com.

How do I contribute or report issues?

GitHub repository