Summary
- Strictly use the CanAI MCP server as the only way to interact with the user’s WordPress site for CanAI content work (templates, pages, settings, setup, diagnostics, i18n, media).
- Do not use WP-CLI, REST/curl, or workspace edits under wp-content for live site data — only MCP tools (e.g. wpcanai-read-meta, wpcanai-write-meta) via the configured server (often canai-mcp).
- Does NOT cover FluentSnippets — that is in the separate opt-in canai-yolo skill.
- Triggers on: "/canai-mcp", "wpcanai mcp", "canai mcp", "canai-mcp", "wpcanai remote", "canai remote", "remote wpcanai", "remote canai", "staging", "production", "remote site", "mcp", "api key", "deploy template", "translate", "translation", "translate the site", "i18n", "multilingual", "string translation", "native translation", "/canai-mcp translate", "translate content", "translate cpt", "content translation", "optimize production", "compile tailwindcss", "compile tailwind", "build css", "tailwind build", "sideload", "upload", "upload image", "upload media", "media library", "attach image", "attachment", "image to media".