skeleton-svelte-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_skeleton_docsA | Searches the official Skeleton documentation and returns the most relevant top-level sections. Use for Svelte components, Tailwind utility classes, themes, installation, or APIs. |
| get_skeleton_sectionA | Returns a specific official Skeleton documentation section by its top-level title, such as "Accordion", "Installation", or "Themes". |
| skeleton_svelte_guidanceA | Finds the official Skeleton documentation most relevant to a Svelte UI task and returns implementation-oriented excerpts. This does not generate unverified APIs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| skeleton-full-documentation | The current official Skeleton llms-full.txt document. |
TDQS
Scored across 3 tools
get_skeleton_section is clearly distinct, but search_skeleton_docs and skeleton_svelte_guidance both perform relevance-based retrieval from the same documentation. The difference between returning top-level sections and implementation-oriented excerpts is present but subtle enough that an agent could easily choose the wrong tool.
Two tools follow a clear verb_noun pattern: search_skeleton_docs and get_skeleton_section. The third, skeleton_svelte_guidance, reads as a noun phrase rather than a verb-driven action, creating a mild inconsistency in the set.
Three tools is well-scoped for a documentation-focused MCP server. Each tool has a clear function, and there is no unnecessary bloat or redundancy that would weigh down the server.
The domain is Skeleton documentation lookup, and the set covers searching, retrieving specific sections, and getting task-oriented guidance. A direct listing or browsing of all available sections is missing, but the existing tools can likely cover most documentation needs.