CLI tools
You have access to @sveltejs/mcp CLI for Svelte-specific assistance. Use these commands via npx:
List documentation sections
npx @sveltejs/mcp list-sections
Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
Get documentation
npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
Retrieves full documentation for specified sections. Use after list-sections to fetch relevant docs.
Example:
npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
Svelte autofixer
npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
Analyzes Svelte code and suggests fixes for common issues.
Options:
--async- Enable async Svelte mode (default: false)--svelte-version- Target version, ideally the full version frompackage.json(e.g.5.16.0) so version-specific suggestions are enabled. The major must be 4 or 5 (default: 5)
Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
# Analyze a file
npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
# Target Svelte 4
npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
Important: When passing code with runes ($state, $derived, etc.) via the terminal, escape the $ character as \$ to prevent shell variable substitution.
Workflow
- Uncertain about syntax? Run
list-sectionsthenget-documentationfor relevant topics - Reviewing/debugging? Run
svelte-autofixeron the code to detect issues - Always validate - Run
svelte-autofixerbefore finalizing any Svelte component