Scandit
com.scanditPublished by scandit.comOfficial publisherv1.0.1Updated Oct 28, 2026
Create a Scandit account, get trial license keys and set up the Scandit SDK in your app.
Overview
Scandit's remote MCP endpoint that connects an assistant to a Scandit account to provision trial license keys for the Scandit Data Capture SDK.
- What you can do
- Provision trial license keys against a Scandit account
- Support setup of the Scandit Data Capture SDK in an app
- Companion to Scandit's agent skills for barcode, label and ID capture integration
- No individual tools are listed in the manifest, so capabilities beyond license provisioning are not documented
- When to use it
- Useful when you are integrating the Scandit Data Capture SDK into an app and want an assistant to obtain trial license keys and help with setup, rather than pasting documentation snippets.
- Requirements
- A remote streamable HTTP endpoint at ssl.scandit.com; OAuth authentication is required, so a Scandit account is needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Scandit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.scandit%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"scandit": {
"type": "http",
"url": "https://ssl.scandit.com/mcp"
}
}
}README
Agent Skills for the Scandit SDK
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.
Installation
Install the plugin. One command, and your agent gets all 87 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:
Just one skill? Your agent only loads the skills your prompt needs, so the full bundle is the right choice — install once with npx [email protected] add scandit/skills.
How to use it
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.
Already know the product? Go straight to its skill.
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.
Licence keys
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 [email protected] 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.
Privacy
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/.
Available skills
Contributing
We welcome feedback that improves the quality of these skills:
- Report issues. File bugs, outdated SDK patterns, or incorrect guidance in the issue tracker.
- Request new skills. If a Scandit product, framework, or workflow you need isn't covered, open a feature request.
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 while either reports a finding.
License
See the LICENSE file for licensing information.
Source: README.md at commit 3d02475
Tools
0Version history
2- v1.0.1LatestOct 20, 2026
- v1.0.0Oct 12, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts