mcp-svelte-docs

An MCP (Model Context Protocol) server that provides a single tool to look up authoritative Svelte 5/SvelteKit definitions extracted from TypeScript declarations, with caching and fuzzy matching for identifier queries.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ DevTools mcp model-context-protocol svelte sveltekit documentation developer-tools typescript search caching
⚙ Agent Friendliness
63
/ 100
Can an agent use this?
🔒 Security
31
/ 100
Is it safe for agents?
⚡ Reliability
36
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
70
Error Messages
0
Auth Simplicity
95
Rate Limits
10

🔒 Security

TLS Enforcement
30
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
55
Secret Handling
70

No auth/TLS guarantees are described; MCP is likely local stdio transport, reducing network exposure but not eliminating risk from running untrusted npm packages. Includes a SQLite dependency (better-sqlite3) for caching; ensure local file permissions and avoid running with elevated privileges. No details provided about logging of queries or secret handling.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
40
Error Recovery
50
AF Security Reliability

Best When

You want assistant-integrated, type-driven reference lookups for Svelte 5 concepts during development or migration.

Avoid When

You need guaranteed up-to-date content without verifying source extraction, or you require OAuth/user-scoped access controls.

Use Cases

  • Get syntax/quick/full documentation for Svelte 5 runes and concepts inside an MCP-capable assistant
  • Answer Svelte 4-to-5 migration questions with structured guidance
  • Provide type-signature-level reference for Svelte template features (e.g., snippets, await expressions, remote functions)
  • Reduce documentation lookup latency via built-in caching

Not For

  • Direct execution of Svelte code or project scaffolding
  • Authoritative legal/compliance guidance (it’s documentation lookup)
  • Production API usage requiring REST/GraphQL interfaces

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication is described in the provided README/manifest; MCP server is likely run locally via stdio (npx).

Pricing

Free tier: No
Requires CC: No

Appears to be an MIT-licensed npm package; costs would be environment/hosting-related for your own usage, not described by the package.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Single-tool design means correct identifier selection is important; fuzzy matching exists but may still return unexpected related concepts for ambiguous queries.
  • Response size depends on requested format (syntax/quick/full); agents should choose a smaller format for brief answers.
  • Because it’s extracted from TypeScript declarations, behavior depends on the bundled/installed version of the underlying definitions/cached data.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-svelte-docs.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered