MCP Svelte Docs Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| svelte_definitionC | Lookup Svelte 5 & SvelteKit definitions from TypeScript declarations. Covers all runes ($state, $derived, $props, $effect), features (snippets, onclick, component-events), and patterns. Supports syntax/quick/full format for varying detail levels. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming since there are no other tools to compare against. The tool name 'svelte_definition' follows a clear noun-based pattern.
One tool is too few for a server that appears to cover Svelte 5 and SvelteKit definitions comprehensively. A single lookup tool feels thin and may not adequately support varied agent workflows, suggesting an incomplete or overly narrow implementation.
The server's domain is Svelte documentation, but with only a definition lookup tool, there are significant gaps. Missing are tools for examples, tutorials, API references beyond definitions, or interactive features, which limits agent effectiveness in handling broader documentation tasks.