Tailwind Svelte Assistant MCP Server

How to use

You connect your MCP client to the server using the provided HTTP endpoint or run the server locally in stdio (direct process) mode. In HTTP mode, your client interacts with a remote MCP URL to retrieve full documentation and snippets for SvelteKit and Tailwind CSS. In stdio mode, you launch the server locally and communicate over standard input/output, which is useful for development and embedded integrations. Use the HTTP endpoint for production deployments and the stdio option for local development or constrained environments.

How to install

Prerequisites you need before installation: Node.js 20+ for ES modules support, npm or yarn, and Git for cloning or managing dependencies.

Option 1 — Install via Smithery (recommended):

npx -y @smithery/cli install @CaullenOmdahl/tailwind-svelte-assistant --client claude

This installs the MCP server, configures it for the Claude Desktop client, and sets up all required dependencies.

Option 2 — Install via direct URL (for MCP clients that support a remote URL):

https://server.smithery.ai/@CaullenOmdahl/tailwind-svelte-assistant/mcp

Add this to your MCP client configuration to connect via HTTP transport.

{
  "mcpServers": {
    "tw_svelte_assistant": {
      "url": "https://server.smithery.ai/@CaullenOmdahl/tailwind-svelte-assistant/mcp",
      "transport": "http"
    }
  }
}

Configuration and setup

The server supports secure defaults and can be customized through the ServerConfig interface. Typical options include file size limits, cache duration, and content base paths. Use the following example as a guide to configure your environment. In most cases you can start with the defaults and adjust only what you need.

const CONFIG = {
  maxFileSize: 3 * 1024 * 1024,    // 3MB max file size for full docs
  cacheTimeout: 5 * 60 * 1000,     // 5 minutes cache timeout
  contentBasePath: './content',
  svelteFullDocsPath: './content/docs/svelte-sveltekit-full.txt',
  tailwindFullDocsPath: './content/docs/tailwind-docs-full.txt',
  // ... other paths
};

Documentation updates are handled automatically with a script that downloads and updates the full Svelte and Tailwind docs and regenerates content.

Security and performance notes

Security features include input validation, path sanitization, strict length checks, and audit logging to monitor for anomalies. The server uses an in-memory LRU cache to speed up responses for frequently requested content and enforces file size limits to prevent resource exhaustion.

Available tooling and snippets

A set of tools and endpoints provide complete documentation access, search capabilities, and component snippets. Access tools to fetch complete docs, search within docs, or retrieve snippets as described in the tooling section.

get_svelte_full_docs

Fetch complete Svelte & SvelteKit documentation (1MB, 100% coverage) in a single response.

get_tailwind_full_docs

Fetch complete Tailwind CSS documentation (2.1MB, 100% coverage) including all 249 files.

search_svelte_docs

Search within Svelte documentation with a query and optional limit, returning matching sections.

search_tailwind_docs

Search within Tailwind documentation with a query and optional limit.

get_component_snippet

Fetch a Svelte component snippet by category and name.

list_snippet_categories

List available snippet categories.

list_snippets_in_category

List all snippets within a specific category.

get_sveltekit_doc

Retrieve a specific SvelteKit topic (legacy access).

get_tailwind_info

Retrieve specific Tailwind information (legacy access).

list_tailwind_info_topics

List available Tailwind topics (legacy access).