Home / Directory / Svelte / playground-link
Playground link
An MCP tool from the Svelte server, run by Svelte.
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.
Name on the gateway: svelte__playground-link.
Parameters
| Name | Type | Description |
|---|---|---|
name required | string | The name of the Playground, it should reflect the user task |
tailwind required | boolean | If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code |
files required | object | An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '<script>...</script>', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level. |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "svelte__playground-link",
"arguments": {
"name": "…",
"tailwind": true,
"files": "…"
}
}The first call connects Svelte to your account automatically; nothing to set up. About this server.
Try asking
Use the playground link tool with name set to ….