Svelte 5 changed enough that a model trained before it will answer confidently in Svelte 4 idiom. This is a URL you paste into a client config — no key, no install, no local process — and the documentation it serves is maintained by the service rather than by you. The SSE endpoint exists so clients without Streamable HTTP support are not left out.
The MCP endpoint of svelte-llm, a service that packages Svelte 5 and SvelteKit documentation as LLM presets. You point a client at a URL; there is no package to install and nothing running on your machine.
- Svelte 5 and SvelteKit documentation presented for a model to consume, served over the Model Context Protocol
- Two transports so older clients are not excluded — Streamable HTTP at `https://svelte-llm.stanislav.garden/mcp/mcp` for Claude Desktop and most current clients, and SSE at `https://svelte-llm.stanislav.garden/mcp/sse` for clients that do not support it
- A browsable site at svelte-llm.stanislav.garden alongside the endpoint
Nothing — it is a hosted endpoint, and `server.json` lists both remotes with no headers, so no account and no key. Running the service yourself is a different matter: it needs Docker Compose, a Postgres connection string in `DB_URL`, and a classic GitHub token with `public_repo` permission in `GITHUB_TOKEN`, after which `npm run dev` starts it and a visit to the migration route sets up the database.