Limitations & FAQ

What the Avonni MCP server and Skills do not cover, and fixes for common setup problems.

🚧 Early access. Build with AI is rolling out gradually and improving with every release. Something unclear, missing, or broken? Tell us: your feedback directly shapes what we improve next.

Limitations

These tools are focused and deliberately narrow. Knowing where they stop saves you from expecting things they were never built to do.

• Your component, not your org. The avonni-lwc-components skill edits the HTML, JavaScript, and CSS of the component you point it at. Apex classes, permission sets, and org configuration stay in your hands.
• Nothing is deployed. The skill writes or edits files locally and stops there. It never pushes to an org. Deploying is your responsibility, using the Salesforce CLI or your usual deployment process.
• The MCP server is a hard dependency. The skills refuse to run without it rather than guess. There is no offline mode: if the server is unreachable, the skill stops and asks you to connect it.
• The MCP server documents the latest release, which may be ahead of your installed package. The documentation service updates automatically with each Avonni package release. If your org is on an older package version, the assistant may confidently use a component or attribute you don't yet have. Keep your installed Avonni packages up to date to stay in sync.
• Node.js and an authenticated Salesforce CLI are the working foundation, in every client. The skills run local scripts that require Node.js 18+, and the Salesforce CLI connects them to your org for documentation lookups and component-version queries, then carries your deployment. Without that foundation, the assistant can read documentation but cannot produce anything usable, including in the Claude desktop app.
• avonni-architect does not orchestrate this skill. The architect coordinates the Flow, Dynamic Component, and Experience skills for multi-artifact use cases. avonni-lwc-components is a direct-edit workflow you invoke on your own code.

Troubleshooting

Problem	Cause	Fix
The skill doesn't activate	The skills aren't installed in the assistant or project you have open. The npx skills add avonni/skills command installs into the current project only.	Re-run the install command from the open project, copy the skill folders into your assistant's skills directory (.claude/skills/ for Claude Code), or add them again from your assistant's Skills settings.
The skill doesn't activate	The prompt is too vague to trigger the right skill.	Mention an avonni-* component by name, or invoke the skill directly. In Claude, type /avonni-lwc-components.
The assistant guesses attributes instead of looking them up	The MCP server isn't connected.	Check your assistant's MCP status (in Claude Code, run claude mcp list) and verify the server URL. Then test with "List the available Avonni LWC components."
The skill runs but cannot look up org data	Node.js is missing, or the Salesforce CLI isn't installed or isn't authenticated to your org.	Install Node.js 18+, install the Salesforce CLI, then run sf org login web and retry.
The MCP connection fails	Wrong URL, wrong transport, or the server was added to a different project. The claude mcp add command registers it for the current project only.	Confirm the URL is https://mcp.avonnicomponents.com over HTTP transport. Re-run the command from the right project, or add it at a wider scope (in Claude Code, claude mcp add --scope user …).
The assistant can't find a component I know exists	A ?toolsets= filter excludes the component's package. With ?toolsets=lwc, flow, dynamic, and experience components are invisible.	Remove the filter or add the missing package to the list.
The generated markup uses an attribute my org doesn't have	Your installed package is older than the latest release the MCP server documents.	Update the Avonni LWC Components package, or tell the assistant your installed version so it avoids newer attributes.