QR Studio
Trustflow v0.1.4
Design and export QR codes
From the developer
Declared capabilities
- Interactive
Declared limitations
- Unrelated questions must not open the studio.
- Do not invent preset ids or file paths.
- A missing design must return an error, not a fabricated design.
Not specified in the available declarations: pricing & account requirements.
Onboarding example
Open QR Studio and make a styled QR code for my Wi-Fi network.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.
Description
From the marketplace listing
QR Studio is a creative design tool for making custom QR codes in ChatGPT. Create QR codes for links, text, Wi-Fi networks, contact cards, emails, SMS messages, phone numbers, locations, and calendar events. Choose a preset and customize the colors, gradients, dot and corner shapes, background, and center logo. Preview your design, adjust its quiet zone and error correction, then export a PNG or SVG or copy a PNG. Save designs in the current session library. The interface supports 54 locales, including right-to-left layouts. Scan a code before sharing or printing it to confirm it works for your content and chosen design.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 18, 2026. Last seen Nov 18, 2026.
Similar plugins
Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
qr-studio4.5 KB
---
name: qr-studio
description: Use when the user wants to create, restyle, save, open, or export a QR code — a link, Wi-Fi network, contact card, email, SMS, phone number, location, calendar event, or plain text — especially when they want a designed QR with colors, shapes, or a center logo.
---
# QR Studio
QR Studio is a design studio for styled QR codes. The hosted MCP server runs at `https://iplugin.dev/qr/mcp`; a self-hosted copy can run at `http://127.0.0.1:8801/mcp`. The preview and editor are an MCP App, and saved designs and exports stay in the current MCP session (the local copy uses `~/.iplugin-qr`). There is no account, analytics, or separate model call.
The code is rendered by the vendored [qr-code-styling](https://github.com/kozakdenys/qr-code-styling) library, so the encoded payload is a real QR code, not a picture of one.
## Opening the studio
Call `qr_home` when the user wants to design, preview, or manage QR codes interactively. It opens the fullscreen studio, resumes the active design, and returns `{ design, designs }`. It is the main render tool. Do not call it in a loop.
`qr_state` is the same data without opening another view; the studio uses it while booting. `qr_list` returns only the library summaries.
## Creating and changing
- `qr_create` — build, save, and open a new design. Provide either `data` (the exact payload) or `content` (a structured object such as `{ "type": "wifi", "ssid": "Home", "password": "secret", "encryption": "WPA" }`).
- `qr_update` — change a saved design by `id`. Only the supplied fields change.
- `qr_open` — open a saved design by `id`.
- `qr_delete` — permanently delete a design.
- `qr_save` — internal tool for the studio editor. Models should not call it.
Structured content types and their fields:
| Type | Fields |
| --- | --- |
| `url` | `url` |
| `text` | `text` |
| `wifi` | `ssid`, `password`, `encryption` (`WPA`/`WEP`/`nopass`), `hidden` |
| `vcard` | `firstName`, `lastName`, `org`, `title`, `phone`, `email`, `url`, `address`, `note` |
| `email` | `to`, `subject`, `body` |
| `sms` | `phone`, `message` |
| `phone` | `phone` |
| `geo` | `lat`, `lng`, `label` |
| `event` | `title`, `location`, `start`, `end`, `description` (datetime-local values) |
Use `data` when the user already has a payload. The server builds the correct escaping for Wi-Fi and vCard; do not hand-assemble those strings when `content` will do it. Never invent a URL, password, phone number, or contact detail the user did not give you.
## Choosing a look
Call `qr_presets` before choosing a style; do not invent preset ids. Presets: `violet`, `ink`, `ocean`, `sunset`, `forest`, `candy`, `gold`, `midnight`, `mono`.
A style is `preset` plus optional overrides: `dotType` (`square`, `rounded`, `dots`, `classy`, `classy-rounded`, `extra-rounded`), `cornerSquareType`, `cornerDotType`, `fg`, `accent`, `bg` (hex or `transparent`), `gradient`, `gradientType`, `gradientRotation`, `shape` (`square`/`circle`), `margin` (quiet zone px at 1024 reference), and `ecc` (`L`/`M`/`Q`/`H`).
Keep the QR scannable:
- Use dark dots on a light background, or the `midnight` preset for light-on-dark. Avoid low-contrast palettes.
- Keep a logo at or below 35% (`logo.size` ≤ 0.35) and leave `ecc` at `H` when a logo is present.
- Do not set `margin` to 0 for print use. The default is 36 px at 1024, about 3.5%.
- If the user asks for a tiny QR, prefer the `ink` or `mono` preset and a larger export size.
## Logos
`logo` accepts `{ enabled, kind: "mark" | "monogram" | "custom", initials, size, margin, hideDots, plate }`. `mark` is the QR Studio glyph, `monogram` draws the user's 1–3 initials on a gradient tile, and `custom` needs an image. For a custom image, use the studio's upload control. Do not claim an upload succeeded unless the tool returned a saved design.
## Exporting
`qr_export` renders a saved design to `png` or `svg` at 256–4096 px and returns a download URL and filename. The hosted service stores the export oPreview of the first 4,000 characters. Read full instructions →
Release notes
0.1.6 lists Trustflow as the developer and retains the anonymous usage statistics introduced in 0.1.5. 0.1.5 adds anonymous browser UUID daily active-user counts (Asia/Shanghai) and sanitized per-MCP-call events with best-effort UUID/context association. Analytics exclude tool arguments, results, game/puzzle/QR content and network identifiers. Events/context mappings expire after 400 days; daily activity hashes are retained until deletion is requested. New UI CSP permits https://iplugin.dev. The previously published UI resource remains available with unchanged HTML and CSP. Analytics failures do not block core tools. Unsupported interface.screenshots is removed; upload screenshots separately. See the updated plugin privacy policy and data deletion page.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- Trustflow
- Keywords
- See keywords
- Listing translations
- af-ZA, am-ET, ar-SA, bg-BG, bn-BD, ca-ES, cs-CZ, da-DK, de-DE, el-GR, en-GB, en-US, es-ES, et-EE, fa-IR, fi-FI, fr-FR, gu-IN, he-IL, hi-IN, hr-HR, hu-HU, id-ID, it-IT, ja-JP, kn-IN, ko-KR, lt-LT, lv-LV, ml-IN, mr-IN, ms-MY, nb-NO, nl-NL, pl-PL, pt-BR, pt-PT, ro-RO, ru-RU, sk-SK, sl-SI, sr-RS, sv-SE, sw-KE, ta-IN, te-IN, th-TH, tr-TR, uk-UA, ur-PK, vi-VN, zh-CN, zh-TW, es-419, fil-PH
- Getting started skill
- ./skills/qr-studio/SKILL.md
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Interactive
Package observed Nov 18, 2026.
Technical details
- First seen
- Nov 18, 2026 · 06:00 UTC
- Last seen
- Nov 18, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6aea9bfd38848191a10127c8ca8e368e
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.