"Svelte" matching MCP tools:

• svelte-autofixer

  Svelte MCP

  Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user

  Connector

• playground-create

  Anima MCP Server

  Create an Anima playground from a prompt, website URL, or Figma design — or an empty one for code you author yourself. Returns a playground URL where the generated code can be viewed and edited. **Input types (set via "type" field):** - "p2c": Generate from a text prompt. Requires: prompt. Styling: tailwind, css, inline_styles. - "l2c": Convert a website URL to code. Requires: url. Styling: tailwind, inline_styles. uiLibrary: shadcn only. - "f2c": Convert Figma frames to code. Requires: fileKey, nodesId (also requires X-Figma-Token header). Styling: tailwind, plain_css, css_modules, inline_styles. uiLibrary: mui, antd, shadcn, clean_react. - "blank": An EMPTY playground for code you wrote yourself. Requires: framework. Pair with project-get_git_token to push your code over git. **Common fields:** framework — ONLY html and react are supported (no vue, svelte, angular, etc.); defaults to html, REQUIRED for blank. styling (see per-type options above). **React-only fields:** language (typescript or javascript), uiLibrary (see per-type options above) — both require framework "react". **Returns:** { success, sessionId, playgroundUrl, previewUrl, name }

  Connector

• list-sections

  Svelte MCP

  Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once.

  Connector

• playground-link

  Svelte MCP

  Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.

  Connector

• get-documentation

  Svelte MCP

  Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.

  Connector

• review_files

  Rams

  Run a Rams design review over UI files (React, Vue, Svelte, CSS). Returns a 0-100 score (any critical issue caps it at 59), issues with severity, category, file:line, and concrete fixes. Use before committing UI changes to catch accessibility and design problems. TOKEN COST WARNING: reading and sending files consumes the CALLING agent's context and token budget, roughly proportional to the code sent. Reviewing a handful of changed screens is cheap; a whole-codebase audit in many batches can consume a large share of the user's model allowance — warn the user and get their OK before starting one, and prefer reviewing the highest-traffic screens.

  Connector

• review_files

  Rams

  Run a Rams design review over UI files (React, Vue, Svelte, CSS). Returns a 0-100 score (any critical issue caps it at 59), issues with severity, category, file:line, and concrete fixes. Use before committing UI changes to catch accessibility and design problems. TOKEN COST WARNING: reading and sending files consumes the CALLING agent's context and token budget, roughly proportional to the code sent. Reviewing a handful of changed screens is cheap; a whole-codebase audit in many batches can consume a large share of the user's model allowance — warn the user and get their OK before starting one, and prefer reviewing the highest-traffic screens.

  Connector