svelte/svelte-server — Svelte MCP MCP Resource
svelte/svelte-server
is one of 197 resources on the
Svelte MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach svelte/svelte-server from your client
- Claude Code Svelte MCP Resource/svelte/svelte-server run in your project directory
- Claude Desktop Svelte MCP Resource/svelte/svelte-server ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Svelte MCP Resource/svelte/svelte-server ~/.cursor/mcp.json
- VS Code Svelte MCP Resource/svelte/svelte-server .vscode/mcp.json
- Zed Svelte MCP Resource/svelte/svelte-server ~/.config/zed/settings.json
- Windsurf Svelte MCP Resource/svelte/svelte-server ~/.codeium/windsurf/mcp_config.json
- Cline Svelte MCP Resource/svelte/svelte-server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Svelte MCP Resource/svelte/svelte-server ~/.gemini/settings.json
- Grok Svelte MCP Resource/svelte/svelte-server .mcp.json (in your project root)
- ChatGPT Svelte MCP Resource/svelte/svelte-server Settings → Connectors → Advanced → Developer mode
- Claude.ai Svelte MCP Resource/svelte/svelte-server Settings → Connectors → Add custom connector
- LangChain Svelte MCP Resource/svelte/svelte-server pip install langchain-mcp-adapters
Other resources on this server
- playground-link-ui
- ai/overview
- ai/instructions
- ai/mcp
- ai/local-setup
- ai/remote-setup
- ai/tools
- ai/resources
- ai/prompts
- ai/cli
- ai/skills
- ai/subagent
- ai/claude-plugin
- ai/opencode-plugin
- ai/cursor-plugin
- ai/copilot-plugin
- ai/codex-plugin
- cli/overview
- cli/faq
- cli/sv-create
- cli/sv-add
- cli/sv-check
- cli/sv-migrate
- cli/ai-tools
- cli/better-auth
- cli/drizzle
- cli/eslint
- cli/experimental
- cli/mdsvex
- cli/paraglide
- cli/playwright
- cli/prettier
- cli/storybook
- cli/sveltekit-adapter
- cli/tailwind
- cli/vitest
- cli/community
- cli/sv
- cli/sv-utils
- kit/introduction
Svelte MCP also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.