Chromium Style QR Code Generator

io.github.chromium-style-qrcodePublished by GitHub account chromium-style-qrcodev1.0.2Updated Oct 27, 2026

MCP server for generating Chromium-style QR codes with optional Dino logo or custom center image

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Local MCP server that generates Chromium-style QR codes as PNG images, with an optional Dino logo or custom center image.

What you can do
  • Generate a QR code from text or a URL and return it as a PNG image
  • Render it in Chromium style with circular modules and rounded locator corners
  • Keep the default Chrome Dino logo in the center, or turn the center image off for a plain code
  • Replace the center image with a Base64-encoded custom logo
When to use it
Useful when an assistant needs to turn a link or short text into a scannable QR code image, especially one that matches Chrome's visual style or carries a custom center logo.
Requirements
Runs locally over stdio; Node.js 22.14.0 or newer. Install via npx, bunx or a global npm install of the package. No accounts, API keys or environment variables are declared.
Before you install
The custom center image is passed as Base64 data to the local process, so avoid embedding sensitive images. Generated codes are returned as images; verify scannability before publishing, since a large center logo can reduce reliability.

Installation

In SourceWeft

  1. Open Chromium Style QR Code Generator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@chromium-style-qrcode/mcp

中文文档

An MCP (Model Context Protocol) server for generating Chromium-style QR codes with circular modules, rounded locators, and an optional center image (Dino logo or custom).

Features

  • Chromium-style rendering — circular dot modules, rounded locator corners, matching the QR codes generated by Google Chrome
  • Dino logo — the iconic Chrome Dino is drawn in the center by default
  • Custom center image — supply a Base64-encoded image to replace the Dino
  • Toggle center image — set showLogo: false to generate a plain QR code
  • MCP-native — communicates over stdio, works with any MCP-compatible client

Installation

Note: The type: "stdio" field is not required — it's the default transport for MCP servers configured with command and args.

Using npx (recommended)

No installation required:

jsonc
{  "mcpServers": {    "io.github.chromium-style-qrcode/mcp": {      "command": "npx",      "args": ["-y", "@chromium-style-qrcode/mcp"]    }  }}

Using bunx

jsonc
{  "mcpServers": {    "io.github.chromium-style-qrcode/mcp": {      "command": "bunx",      "args": ["@chromium-style-qrcode/mcp"]    }  }}

Global install

bash
npm install -g @chromium-style-qrcode/mcp

Then configure the MCP client:

jsonc
{  "mcpServers": {    "io.github.chromium-style-qrcode/mcp": {      "command": "chromium-style-qrcode-mcp"    }  }}

Tool

generate_qr_code

Generate a Chromium-style QR code and return it as a PNG image.

Parameters
ParameterTypeRequiredDefaultDescription
textstringYes—The text or URL to encode
showLogobooleanNotrueWhether to show a center logo
customLogostringNo—Base64-encoded image to use as the center logo instead of the Dino
Examples

Basic QR code with Dino logo:

json
{  "text": "https://example.com"}

Plain QR code (no center image):

json
{  "text": "https://example.com",  "showLogo": false}

QR code with custom center image:

json
{  "text": "https://example.com",  "customLogo": "<base64-encoded image data>"}

Development

bash
# Install dependenciesbun install
# Run in developmentbun run start
# Buildbun run build
# Lint & formatbun run lintbun run format

Requirements

  • Node.js >= 22.14.0

License

MIT

Source: README.md at commit eb23c1e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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