Skip to main content
Glama
skeleton-svelte-mcp

skeleton-svelte-mcp

by mxmauro

Skeleton Svelte MCP

A local, stdio MCP server that gives coding agents searchable access to the official Skeleton documentation, with a focus on Svelte usage.

What it provides

  • search_skeleton_docs: ranked official documentation sections for a task or API query.

  • get_skeleton_section: a full named section, such as Accordion or Installation.

  • skeleton_svelte_guidance: Svelte-oriented excerpts for an implementation task.

  • skeleton://documentation/full: the complete official documentation as an MCP resource.

Documentation is retrieved only from Skeleton's published llms-full.txt, kept in memory for one hour, and refreshed after that. If a refresh fails, the last successful copy remains available for the process lifetime.

Related MCP server: @particle-academy/docs-mcp

Install and build

Requires Node.js 20 or later.

npm install
npm run build

Codex configuration

Add this server to your Codex MCP configuration, replacing {base-folder} with the directory containing this project:

[mcp_servers.skeleton-svelte]
command = "node"
args = ["{base-folder}\\dist\\index.js"]

For development, use npx tsx {base-folder}\\src\\index.ts as the command and arguments instead.

The server uses stdout exclusively for MCP JSON-RPC; operational logs must go to stderr.

Run directly from GitHub

The compiled dist/ folder is intentionally committed, so Codex can download and run a tagged GitHub release without a local clone. Create and push a Git tag that matches the release, for example:

git tag v0.1.1
git push origin v0.1.1

Then configure Codex to install and run that immutable release through npx:

[mcp_servers.skeleton-svelte]
command = "npx"
args = [
  "--allow-git=all",
  "--yes",
  "--package=github:mxmauro/mcp-skeleton-dev#v0.1.1",
  "skeleton-svelte-mcp"
]

v0.1.1 is a Git tag, not merely the version value in package.json. Every tagged release must include package.json, package-lock.json, and a freshly built dist/ directory. Node.js, npm, GitHub access, and network access are required on the machine where Codex starts the server.

License

Licensed under the MIT License. Copyright (c) 2026 Mauro H. Leggieri.

Available Tools

3 tools
get_skeleton_sectionGet a Skeleton documentation sectionA

Returns a specific official Skeleton documentation section by its top-level title, such as "Accordion", "Installation", or "Themes".

Inputs: title (required).

search_skeleton_docsSearch Skeleton documentationA

Searches the official Skeleton documentation and returns the most relevant top-level sections. Use for Svelte components, Tailwind utility classes, themes, installation, or APIs.

Inputs: query (required), limit.

skeleton_svelte_guidanceGet Svelte-oriented Skeleton guidanceA

Finds the official Skeleton documentation most relevant to a Svelte UI task and returns implementation-oriented excerpts. This does not generate unverified APIs.

Inputs: task (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that gives AI agents access to developer tooling — GitHub (read-only), documentation search, and web research — via stdio transport.
      MIT