Skip to main content
Glama
flarewand

freeqrcode-mcp-server

by flarewand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Free QR Code Generator MCP Server

A Model Context Protocol (MCP) server that provides QR code generation capabilities through AI assistants like Cursor, Claude, and other MCP-compatible clients.

Features

  • ๐ŸŽฏ Multiple QR Code Types: URL, text, vCard, WiFi, email, phone

  • ๐ŸŽจ Customization Options: Size, colors, error correction levels

  • ๐Ÿš€ High Performance: Built with TypeScript and optimized for production

  • ๐Ÿ”’ Secure: No local file system access, cloud-based API calls

  • ๐Ÿ“ฑ Cross-Platform: Works on Windows, macOS, and Linux

Related MCP server: QRzap MCP Server

Installation

Global Installation (Recommended)

npm install -g freeqrcode-mcp-server

Local Installation

npm install freeqrcode-mcp-server

Usage

1. Cursor IDE Configuration

Add this to your mcp.json:

{
  "mcpServers": {
    "freeqrcode": {
      "command": "npx",
      "args": ["freeqrcode-mcp-server"]
    }
  }
}

2. VS Code Configuration

Add this to your VS Code MCP settings:

{
  "servers": {
    "freeqrcode": {
      "command": "npx",
      "args": ["freeqrcode-mcp-server"]
    }
  }
}

3. Environment Variables

You can customize the API endpoint:

export QR_API_BASE_URL=https://your-custom-domain.com

Content Formats

The MCP server supports multiple content formats for different QR code types:

URL QR Codes

// Object format (recommended)
{
  type: 'url',
  content: { url: 'https://example.com' }
}

// String format (legacy)
{
  type: 'url',
  content: 'https://example.com'
}

Text QR Codes

{
  type: 'text',
  content: 'Hello, World!'
}

vCard QR Codes

{
  type: 'vcard',
  content: {
    firstName: 'John',
    lastName: 'Doe',
    email: 'john@example.com',
    phone: '+1-555-123-4567'
  }
}

Email QR Codes

{
  type: 'email',
  content: {
    email: 'contact@example.com',
    subject: 'Hello',
    body: 'Message body'
  }
}

Phone QR Codes

{
  type: 'phone',
  content: { phone: '+1-555-123-4567' }
}

WiFi QR Codes

{
  type: 'wifi',
  content: {
    ssid: 'MyWiFi',
    password: 'password123',
    encryption: 'WPA',
    hidden: false
  }
}

Customization Options

All QR code generation tools support these options:

  • size: QR code size in pixels (64-1024, default: 256)

  • foregroundColor: Foreground color in hex format (default: #000000)

  • backgroundColor: Background color in hex format (default: #FFFFFF)

  • errorCorrectionLevel: Error correction level (L, M, Q, H, default: M)

Error Correction Levels

  • L (Low): 7% recovery capacity

  • M (Medium): 15% recovery capacity (default)

  • Q (Quartile): 25% recovery capacity

  • H (High): 30% recovery capacity

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests

  5. Submit a pull request

License

MIT License - see LICENSE file for details.

Available Tools

1 tool
generate_and_save_qrC

Generate a QR code and save it to a file with detailed information

ParametersJSON Schema
NameRequiredDescriptionDefault
typeYesType of QR code to generate
contentYesContent to encode in the QR code - format depends on type
filenameYesFilename to save the QR code (without extension)
optionsNo

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only states the basic action (generate and save) but fails to disclose side effects like file overwrite behavior, file location, permissions, or output format. Minimal behavioral context beyond what the schema implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single 12-word sentence that is front-loaded with the primary action. It is concise, though the phrase 'with detailed information' is somewhat vague and could be more precise without increasing length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (6 content types, nested options, no output schema), the description is insufficient. It does not describe the file format, return value, or behavior nuances like error handling. The schema handles much detail, but the description fails to integrate it into a coherent overview.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (75%), so parameters are mostly described in the schema. The description adds 'with detailed information,' which does not clarify parameter usage or relationships. It meets the baseline but provides no extra semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (generate and save) and the resource (QR code). It identifies the primary output (file), but 'with detailed information' is vague and does not add clear differentiation from potential alternatives, though none are listed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, limitations, or exclusions. For a tool with no siblings, this is a missed opportunity to provide context about its applicability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.1
    • First observedgenerate_and_save_qr
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of confusion or overlap.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (generate_and_save_qr) and is descriptive.

Tool Count2/5

A single tool for QR code generation is minimal; users might expect additional tools for customization (e.g., size, format, or returning data).

Completeness2/5

The tool covers only basic generation and saving, missing common QR code parameters (e.g., error correction, size) or other operations like reading or styling.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers