SvelteLS.MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | No | Optional path to the Svelte project root. If omitted, use the load_project tool at runtime to set it. | |
| SVELTELS_TIMEOUT | No | LSP request timeout in ms (default: 30000) | 30000 |
| SVELTELS_SERVER_PATH | No | Override path to the svelteserver entry script |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_definitionC | Find the definition of a symbol by name in a file. |
| find_referencesC | Find all references to a symbol across the workspace. |
| get_hoverC | Get hover documentation and type info for a symbol. |
| go_to_implementationC | Find implementations of an interface or abstract method. |
| go_to_type_definitionB | Jump to the type definition of a symbol (e.g. find the class/interface of a variable). |
| find_document_symbolsC | List all symbols defined in a file. |
| find_workspace_symbolsC | Search for symbols across the entire workspace. |
| get_diagnosticsA | Get compiler errors, warnings, and diagnostics for a file. Opens the document to trigger computation if needed. |
| rename_symbolB | Rename a symbol across the workspace. Applies changes to disk. |
| format_documentC | Format a file (or a range of lines) using the project's formatting rules. |
| get_code_actionsC | List available code actions (quick fixes, refactorings) for a line or range in a file. |
| apply_code_actionA | Apply a code action (quick fix, refactoring) by its title. Use get_code_actions first to see available actions. |
| get_completionB | Get code completion suggestions at a symbol position. Useful for discovering available members, methods, and types. |
| get_signature_helpC | Get method signature overloads and parameter info at a symbol position. |
| incoming_callsB | Find all functions/methods that call the specified symbol. |
| outgoing_callsC | Find all functions/methods called by the specified symbol. |
| load_projectA | Load a Svelte project by its root directory. Restarts the language server pointed at the new workspace. Call this to switch between projects at runtime. |
| restart_lspA | Restart the Svelte language server. Use when the server is in a bad state or returning stale results. |
| get_compiled_codeB | Get the compiled JavaScript and CSS output for a Svelte component. Useful for debugging compilation issues. |
| get_component_referencesB | Find all files that use/import a Svelte component. |
| get_file_referencesC | Find all files that reference/import the specified file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool has a clearly distinct purpose targeting specific language server operations like definitions, references, completions, diagnostics, and project management. There is no overlap in functionality; for example, find_definition, find_references, and get_completion serve unique roles without ambiguity.
Tool names follow a consistent verb_noun pattern throughout, such as find_definition, get_diagnostics, and rename_symbol. All tools use snake_case with clear action verbs like 'find', 'get', 'apply', and 'load', making the set predictable and readable.
With 21 tools, the count is slightly high but reasonable for a comprehensive language server covering code navigation, refactoring, diagnostics, and project management. It feels heavy but each tool earns its place in the Svelte development domain, avoiding redundancy.
The tool set provides complete coverage for Svelte language server operations, including CRUD-like actions (e.g., rename_symbol, apply_code_action), navigation (e.g., find_definition, go_to_type_definition), diagnostics, completions, and project lifecycle management (e.g., load_project, restart_lsp). No obvious gaps exist for the stated purpose.