Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Create a Scandit account, get trial license keys and set up the Scandit SDK in your app.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://ssl.scandit.com/mcp在终端中运行这条命令
claude mcp add --transport http scandit https://ssl.scandit.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"scandit": {
"url": "https://ssl.scandit.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"scandit": {
"type": "http",
"url": "https://ssl.scandit.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://ssl.scandit.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 scandit.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI agent skills for integrating the Scandit Data Capture SDK.
Each skill is specific to a product and a framework (e.g. SparkScan iOS), and bundles the recommended integration code, up-to-date setup, permissions and license-key wiring, common customization recipes (modes, callbacks, UI tweaks), and migration guidance, SDK version upgrades and, for some products, replacing a third-party scanner, all grounded in Scandit's own documentation. Install once, then just ask your agent for the feature instead of pasting docs snippets into your AI editor.
Install the plugin. One command, and your agent gets all 87 skills:
npx plugins@1.3.4 add scandit/skills
It detects which coding agents you have and installs into each of them. Re-run the same command to pull the latest skills.
Or install from your agent's own marketplace:
| Agent | Install | Updates |
|---|---|---|
| Codex / ChatGPT App | One click install, or search Scandit SDK in the plugin directory | When Scandit publishes a new directory version |
| Claude Code | /plugin install scandit-sdk@claude-plugins-official, or search Scandit SDK in /plugin → Discover | Automatic, on each Scandit release |
| Cursor | One click install, or /add-plugin scandit-sdk in the editor | Automatic, on each Scandit release |
| Codex CLI | codex plugin marketplace add scandit/skills codex plugin add scandit-sdk@scandit-plugins | codex plugin marketplace upgrade scandit-plugins | | Copilot CLI | copilot plugin marketplace add scandit/skills copilot plugin install scandit-sdk@scandit-plugins | copilot plugin update scandit-sdk | | Everyone else | npx plugins@1.3.4 add scandit/skills | Re-run npx plugins@1.3.4 add scandit/skills |
Just one skill? Your agent only loads the skills your prompt needs, so the full bundle is the right choice — install once with npx plugins@1.3.4 add scandit/skills.
Describe what you want in plain language. Your agent loads the right skill on its own, or you can call one explicitly with /skill-name followed by your task.
Not sure which Scandit product you need? Start with data-capture-sdk. It is an advisor, not an integration skill: it asks a few questions about your workflow, recommends the right product, then hands off to the matching implementation skill for your platform. Describe your app, paste a screenshot of the screen you want to add scanning to, or drop in a photo of the label, package or ID you need to capture.
/data-capture-sdk I need to scan barcodes in a warehouse picking app - which Scandit product should I use?
/data-capture-sdk here is a photo of the labels we want to capture - what fits best?
Already know the product? Go straight to its skill.
/sparkscan-ios add a barcode scanner to the home screen of my app
/label-capture-web capture the expiry date and lot number from these pharmacy labels
Migrating? Most implementation skills carry version migration guidance alongside first integration. The Barcode Capture, SparkScan and MatrixScan Batch skills add a guide for replacing a third-party scanner.
/barcode-capture-android migrate this app from the Scandit SDK v6 API to v8
/matrixscan-batch-web we use BarcodeTracking, move us to BarcodeBatch /sparkscan-android replace our current third-party barcode scanner with SparkScan
These skills write the integration; they don't provision the licence key by themselves. The Scandit MCP server does that part — connect it (claude mcp add --transport http scandit https://ssl.scandit.com/mcp) alongside the skills (npx plugins@1.3.4 add scandit/skills) and each implementation skill's ## Licence key section will use it to fetch a trial key and write it into your app's licence-key call, showing only a masked preview in chat. The skills never look for a key on your machine: it comes from the MCP server or from you. The key ends up as a literal in your source code, so keep any non-trial key out of version control.
Keys provisioned this way are trials only, and the MCP server's auth is browser-based, so it does not work headless or in CI. Without it, the dashboard flow at https://ssl.scandit.com still works — every skill falls back to that. The Linux skill (scandit-linux-sdk) uses only that flow: the MCP server provisions no Linux keys.
The skills themselves send nothing anywhere. The bundled Scandit MCP server (https://ssl.scandit.com/mcp) talks to your Scandit account to provision trial licence keys; Scandit's privacy policy is at https://www.scandit.com/privacy/.
| Skill | Description |
|---|---|
data-capture-sdk | Product-selection advisor — recommends the right Scandit product for your use case and hands off to the matching implementation skill. |
sparkscan-{framework} | SparkScan integration & migration. Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
barcode-capture-{framework} | BarcodeCapture (single-barcode scanning) integration & migration — BarcodeCaptureSettings, listener wiring, DataCaptureView + BarcodeCaptureOverlay, camera lifecycle, plus 6→7 and 7→8 deltas. Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
barcode-selection-kmp | Barcode Selection (tap or aim to pick one barcode among many) integration — selection types and strategies, session counts, basic-overlay brushes. Available for kmp (Kotlin Multiplatform). |
matrixscan-ar-{framework} | MatrixScan AR (Barcode AR) integration & BarcodeBatch → BarcodeAr migration. Available for android, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
matrixscan-count-{framework} | MatrixScan Count (BarcodeCount) integration — counting against a list, status overlays, capture-list and not-in-list workflows, plus pre-7.6 → 7.6 constructor migration. Available for cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
matrixscan-count-{framework} | MatrixScan Count (BarcodeCount) native integration — bulk counting with the built-in AR counting UI, the explicitly-managed camera lifecycle, highlight customization (Icon/Dot styles), status mode, clustering, and scanning against a capture list (progress, not-in-list accept/reject). Available for ios, android. |
matrixscan-batch-{framework} | MatrixScan Batch (BarcodeBatch, formerly BarcodeTracking) integration — tracking sessions, basic-overlay brushes, and per-barcode AR annotations via the advanced overlay. Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
matrixscan-find-kmp | MatrixScan Find (BarcodeFind) integration — search-and-find against an item list, found-item handling, barcode transformers, AR find view. Available for kmp (Kotlin Multiplatform). |
matrixscan-pick-{framework} | MatrixScan Pick (BarcodePick) integration — guided picking against a list of products and quantities, resolving scanned barcodes against a product database, plus highlight styling. Available for ios, kmp (Kotlin Multiplatform). |
label-capture-{framework} | Smart Label Capture integration & migration (regex renames v7.6→v8.0, Validation Flow redesign v8.1→v8.2, optional update callback v8.2→v8.4). Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
id-capture-{framework} | ID Capture (identity-document scanning — passports, driver's licenses, ID cards, MRZ/VIZ/barcode/mobile documents) integration & v7→v8 migration (scannerType→scanner wrapper, AamvaBarcodeVerifier removal), plus the three add-on capability modules (voided-ID detection, European driving-license decoding, AAMVA barcode verification). Available for web, flutter, cordova, rn (React Native), capacitor, kmp (Kotlin Multiplatform). |
id-bolt | ID Bolt — Scandit's hosted, drop-in ID scanning for websites (a thin wrapper around ID Capture that runs in a Scandit-hosted pop-up, so you don't build a UI workflow). IdBoltSession.create(...) + start(), DocumentSelection, scanner/validators/anonymization, onCompletion/onCancellation, theming & localization. Uses @scandit/web-id-bolt (not the ID Capture SDK). Web only. |
parser-kmp | Parser — parse GS1 AI, HIBC, AAMVA, EPC, Swiss QR and other structured barcode data into typed fields. Available for kmp (Kotlin Multiplatform). |
scandit-linux-sdk | Linux SDK (low-level C API, usable from C++, plus Python bindings; amd64 and arm64) — single barcode scanning from images, V4L2 cameras or your own frames (OpenCV, GStreamer), MatrixScan multi-barcode tracking, parser and barcode generator; JSON settings, troubleshooting status codes, 7→8 migration, replacing ZBar/pyzbar, ZXing, libdmtx or OpenCV, and why a code doesn't scan (pixels per module, camera and lens planning). Linux keys come from the dashboard, not the MCP server. |
scandit-xamarin-to-net-migration | Migrate the Scandit SDK integration after a Xamarin app has already been moved onto the supported .NET stack — .NET for Android, .NET for iOS, or .NET MAUI (e.g. after Microsoft's .NET app-modernization tooling; Xamarin support ended May 2024). A post-migration, Scandit-only companion: it swaps Scandit.DataCapture.*.Xamarin(.Forms) packages for their .NET/*.Maui equivalents, fixes SDK-8 init, the .Unified namespaces and views, verifies scanning, and hands off to the matching *-net-android / *-net-ios / *-net-maui skill. The general app migration stays with Microsoft's tooling (the GitHub Copilot app-modernization agent, successor to the deprecated .NET Upgrade Assistant). Produces a Scandit migration report. |
We welcome feedback that improves the quality of these skills:
Branches: development happens on main, so target it with pull requests. The default dist branch is an install-only copy (no evals or internal tooling) that CI regenerates on every push to main; changes pushed to it are overwritten. Because main is not the default branch, Fixes #N in a PR does not close the issue on merge: close it by hand.
Pre-push check: in a main clone, run git config core.hooksPath internal/githooks once. Every push then runs the skill-auditor structure lint and its tests, and is refused whil
只显示了开头部分;其余内容请在仓库中阅读