Verfy

MCP serverlar / @sveltejs/mcp

MCP tool o'zgarishlari

@sveltejs/mcp

Oxirgi 5 ta yangilanishning 1 tasi agent o'qiydigan narsani o'zgartirdi: 1 ta tool tavsifi qayta yozilgan, 0.1.30 gacha.

npm paketi · oxirgi marta 2026-yil 13-noyabr kuni soxta sozlamalar bilan toza mashinada yozib olingan; faqat tools/list yuborilgan. O'zgargan tavsif zaiflik emas. npm sahifasi · Usul va cheklovlar · bu ma'lumot JSON ko'rinishida.

Relizma-reliz

0.1.29 → 0.1.30

patch reliz, 2026-yil 4-noyabr

Birorta tool ta'rifi o'zgarmadi.

0.1.28 → 0.1.29

patch reliz, 2026-yil 3-noyabr

Birorta tool ta'rifi o'zgarmadi.

0.1.27 → 0.1.28

patch reliz, 2026-yil 26-oktabr

Birorta tool ta'rifi o'zgarmadi.

0.1.26 → 0.1.27

patch reliz, 2026-yil 19-oktabr
list-sections: tavsif o'zgardi
Oldin (0.1.26)
Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once.
Keyin (0.1.27)
Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get-documentation to fetch ALL relevant sections at once.

svelte-autofixer: kiritma sxemasi o'zgardi

0.1.25 → 0.1.26

patch reliz, 2026-yil 7-avgust

Birorta tool ta'rifi o'zgarmadi.

Sinalgan relizlar: 0.1.25 (2026-06-26); 0.1.26 (2026-08-07); 0.1.27 (2026-10-19); 0.1.28 (2026-10-26); 0.1.29 (2026-11-03); 0.1.30 (2026-11-04).

0.1.30 dagi tool'lar

Pin — tool nomi, tavsifi va kiritma sxemasining SHA-256 qiymati, verfy.lock uni shunday yozadi. Lock'ingizda xuddi shu pin bo'lsa, agentingiz aynan shu ta'rifni o'qiydi. Verfy 0.16.0 va yangilari server yuborsa, tool sarlavhasi, annotatsiyalari va chiqish sxemasini ham qotiradi, shuning uchun bunday tool'ning lock'ingizdagi pin'i boshqacha bo'ladi.

0.1.30 dagi tool'lar
ToolTavsifPin
get-documentationRetrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.92a45dfd10e2
list-sectionsLists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get-documentation to fetch ALL relevant sections at once.1565e842c210
playground-linkGenerates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.abf9e952ac3e
svelte-autofixerGiven a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the usera2cc4054a792
prompt:svelte-taskUse this Prompt to ask for any svelte related task. It will automatically instruct the LLM on how to best use the autofixer and how to query for documentation pages.a8014ba5dd85

Bu tool'larni qotiring

@sveltejs/mcp bugun sizga beradigan narsani qotiring, lock'ni commit qiling, va tool o'zgarganda pull request oldingi va keyingi matn bilan yiqiladi. MCP sozlamangizdagi paket versiyasini ham qotiring.

$ pip install verfy
$ verfy lock check --update   # har bir tool'ni ko'rsatadi, keyin verfy.lock ni yozadi
$ git add verfy.lock
# .github/workflows/verfy.yml, actions/checkout dan keyin
- uses: verfy-dev/verfy-action@v1

Bu serverni yuritasizmi? O'z relizlaringizda xuddi shu tekshiruvni ishga tushiring va README'ga Locked by Verfy belgisini qo'shing.