get_svelte_full_docsLABSCO SUMMARY
The whole documentation, or just the paragraph you needed.
Pulling an entire framework's documentation into context is a real option here and occasionally the right one — the search tools exist because usually it is not. Both are backed by the same local copies, so search results and full reads never disagree. The component snippets are a separate, smaller library of curated Svelte examples rather than generated ones.
What it is
A documentation server carrying full local copies of the Svelte and SvelteKit documentation and the Tailwind CSS documentation. It returns either corpus whole, searches within them for matching sections with their surrounding context, and serves curated Svelte component snippets by category.
What you get
- The complete Svelte and SvelteKit documentation in one call, in the format the Svelte team publishes for models
- The complete Tailwind CSS documentation in one call, covering every utility class
- Search within either corpus, returning matching sections with context and a result limit you set
- Svelte component snippets fetched by category and name, with the categories and their contents listable
- Older topic-by-topic lookups for both frameworks, kept for compatibility
- Content cached and file access bounded, with paths validated before anything is read
Requirements
Nothing to build: the server runs on Smithery, added with the Smithery CLI or by its URL — the repository's own build script produces a Smithery bundle, not a local server. No account, no key. The documentation is refreshed by a script in the repository that pulls from the upstream sources.
Setup effort
One command — npx -y @smithery/cli install @CaullenOmdahl/tailwind-svelte-assistant --client claude
USE CASES
01
Answering a SvelteKit question correctly
Search the official documentation for the section that covers it and read the matching passage with its context.
02
Getting a Tailwind utility right
Search the complete utility documentation rather than relying on what the model remembers.
03
Giving a model the whole framework to work from
Pull the full corpus in one call when the task spans the framework rather than one feature.
04
Starting from a component that already works
Browse the snippet categories and fetch the one closest to what you are building.
05
Seeing what snippets exist in a category
List a category's contents before deciding which example to pull.
11 tools
Listed in project docs. Your client may show a different list.
get_tailwind_full_docssearch_svelte_docssearch_tailwind_docsget_sveltekit_docget_tailwind_infolist_sveltekit_topicslist_tailwind_info_topicsget_component_snippetlist_snippet_categorieslist_snippets_in_categoryBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
npx
Claude Desktop — Smithery
TERMINAL
npx -y @smithery/cli install @CaullenOmdahl/tailwind-svelte-assistant --client claudeHosted endpoint
ENDPOINT URL
https://server.smithery.ai/@CaullenOmdahl/tailwind-svelte-assistant/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Any MCP client — HTTP
ANY MCP CLIENT — HTTP · JSON
{
"mcpServers": {
"tailwind-svelte-assistant": {
"url": "https://server.smithery.ai/@CaullenOmdahl/tailwind-svelte-assistant/mcp",
"type": "http"
}
}
}
