WebMCP Designer

Use this skill when the project needs WebMCP design doctrine, not just ad hoc tool registration.

Layout

• doctrine/ contains the portable doctrine for designing WebMCP on an existing human-facing product.
• stack/ contains the house blueprint for instrumenting a React or JavaScript SPA with WebMCP/ directories, module-local tool wrappers, and thin execute bodies.

First move

Do not guess the runtime surface or memorize API details.

1. Ask whether the MCP-B docs server at docs.mcp-b.ai/mcp is available in the user's MCP client.
2. If it is available, inspect that server and use it as the source of truth for exact tool syntax and package details.
3. If it is not available, read the first-party docs at https://docs.mcp-b.ai/ before making implementation claims.
4. Use this skill for architecture, tool shape, workflow design, and scope decisions.
5. Use the docs server or first-party docs for exact package names, hook signatures, polyfill choices, and annotation details.