MCP QR Code Server
Connects to GitHub for package repository access, specifically for the mcp.el Emacs package installation.
Provides integration with npm for package installation and execution of the QR code server through the npm registry.
Offers integration with Emacs Org mode through mcp.el, allowing QR code generation directly within Emacs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP QR Code Servercreate a QR code for my website https://myportfolio.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
#+TITLE: MCP QR Code Server
Overview Generate QR codes seamlessly using the Model Context Protocol (MCP). This server connects large language models to QR code generation capabilities across multiple client interfaces.
Features
Generate QR codes for multiple content types:
URLs and website links
WiFi network credentials
Contact information (vCard)
Plain text
Calendar events (iCal)
Multiple output formats:
PNG images (base64-encoded)
ASCII/text representation
Data URL format
Customization options:
Size adjustment (100-1000px)
Error correction levels (L, M, Q, H)
Format selection (image, text)
Quick Examples
#+begin_example Please generate a QR code for https://example.com #+end_example
#+begin_example Generate a QR code for the Wi-Fi network "GuestWiFi" with password "Welcome123" #+end_example
#+begin_example Create a QR code for my contact information: Name: John Doe Email: john@example.com Phone: 555-123-4567 #+end_example
Installation
#+begin_src bash npm install -g @jwalsh/mcp-server-qrcode #+end_src
Usage
** Claude Desktop #+begin_src json { "mcpServers": { "qrcode": { "command": "npx", "args": [ "-y", "@jwalsh/mcp-server-qrcode" ] } } } #+end_src
For detailed setup instructions, please refer to:
[[https://modelcontextprotocol.io/quickstart/user][MCP for Claude Desktop Users]]
[[https://modelcontextprotocol.io/quickstart/server][Building MCP Servers]]
[[https://docs.anthropic.com/en/docs/agents-and-tools/mcp][Anthropic MCP Documentation]]
** Claude Desktop
#+begin_src json { "mcpServers": { "qrcode": { "args": [ "-y", "@jwalsh/mcp-server-qrcode" ], "command": "npx" } } } #+end_src
** Emacs with mcp.el #+begin_src elisp :results silent ;; Basic installation with straight.el (use-package mcp :straight (mcp :type git :host github :repo "lizqwerscott/mcp.el")) #+end_src
#+begin_src elisp :results silent ;; Connect to the QR code server (mcp-connect-server "qrcode" "npx" '("-y" "@jwalsh/mcp-server-qrcode") :initial-callback (lambda (connection) (message "Connected to %s" (jsonrpc-name connection))) :tools-callback (lambda (connection tools) (message "Available tools: %s" tools))) #+end_src
#+begin_src elisp :results raw :wrap example ;; Generate a QR code (let ((connection (gethash "qrcode" mcp-server-connections))) (mcp-call-tool connection "generate-qrcode" '(:content "https://example.com" :format "text"))) #+end_src
#+RESULTS: #+begin_example (:content [(:type text :text QR Code for "https://example.com":
█████████████████████████████████ █████████████████████████████████ ████ ▄▄▄▄▄ █▄▀ █ ▀ █▀█ ▄▄▄▄▄ ████ ████ █ █ █▄ ▄█▀ ▀█▄█ █ █ ████ ████ █▄▄▄█ █▀ █ ▀█ ███ █▄▄▄█ ████ ████▄▄▄▄▄▄▄█▄▀▄█ █ ▀ █▄▄▄▄▄▄▄████ ████ ▀▄▀▀▀▄▄▀▀ ▄▀▄▀▀ █▀▄▀ ████ ████▄▀█▄▀ ▄▄▀ ▀▀█▄▀▄█▀▄ ▄█▄████ █████▀▀▄ ▄▄▄ ▀ █ ▄█ █ ███▀ ████ ████▄▄▄█▄▄▄▀▄▀█▀ ▄ ▄ ▄▀▀ ▄█▄████ ████▄▄██▄█▄▄▀▄███ █ ▄▄▄ ██▄▀████ ████ ▄▄▄▄▄ █▄█▄▄█▀█▀ █▄█ ██▀ ████ ████ █ █ ██ █▄ ▄█▄▄ ▄▄ █▀ ▄████ ████ █▄▄▄█ █▄ █▀ ▄ ▀ ▄█▄▄████ ████▄▄▄▄▄▄▄█▄▄▄██▄▄█▄█▄██▄██▄████ █████████████████████████████████ █████████████████████████████████ )]) #+end_example
** MCP Inspector
#+begin_src bash npx -y @modelcontextprotocol/inspector npx -y @jwalsh/mcp-server-qrcode #+end_src
** NPM Package CLI
#+begin_src bash
Verify installation
echo '{"method":"tools/list","params":{},"id":1,"jsonrpc":"2.0"}' | mcp-server-qrcode | jq -r '.result.tools[]|.name' #+end_src
#+RESULTS: : generate-qrcode
#+begin_src bash :results raw :results raw
Generate QR code via JSON-RPC
echo '{"method":"tools/call","params":{"name":"generate-qrcode","arguments":{"content":"https://example.com","format":"text"}},"id":1,"jsonrpc":"2.0"}' | mcp-server-qrcode | jq -r '.result.content[0].text' #+end_src
#+RESULTS: QR Code for "https://example.com":
█████████████████████████████████ █████████████████████████████████ ████ ▄▄▄▄▄ █▄▀ █ ▀ █▀█ ▄▄▄▄▄ ████ ████ █ █ █▄ ▄█▀ ▀█▄█ █ █ ████ ████ █▄▄▄█ █▀ █ ▀█ ███ █▄▄▄█ ████ ████▄▄▄▄▄▄▄█▄▀▄█ █ ▀ █▄▄▄▄▄▄▄████ ████ ▀▄▀▀▀▄▄▀▀ ▄▀▄▀▀ █▀▄▀ ████ ████▄▀█▄▀ ▄▄▀ ▀▀█▄▀▄█▀▄ ▄█▄████ █████▀▀▄ ▄▄▄ ▀ █ ▄█ █ ███▀ ████ ████▄▄▄█▄▄▄▀▄▀█▀ ▄ ▄ ▄▀▀ ▄█▄████ ████▄▄██▄█▄▄▀▄███ █ ▄▄▄ ██▄▀████ ████ ▄▄▄▄▄ █▄█▄▄█▀█▀ █▄█ ██▀ ████ ████ █ █ ██ █▄ ▄█▄▄ ▄▄ █▀ ▄████ ████ █▄▄▄█ █▄ █▀ ▄ ▀ ▄█▄▄████ ████▄▄▄▄▄▄▄█▄▄▄██▄▄█▄█▄██▄██▄████ █████████████████████████████████ █████████████████████████████████
Developer Documentation For detailed setup, installation, contribution guidelines, and additional integration methods, please refer to [[file:DEVELOPERS.org][DEVELOPERS.org]].
Available Tools
1 toolgenerate-qrcodeB
Generate QR codes in various formats with customizable error correction levels and sizes
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Size of the QR code (1-10) | |
| format | No | Output format: 'image' for PNG QR code, 'text' for terminal-friendly output | image |
| content | Yes | The text content to encode in the QR code | |
| errorCorrectionLevel | No | Error correction level (L: 7%, M: 15%, Q: 25%, H: 30%) | M |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so description carries full burden. It doesn't disclose side effects, read-only nature, or return behavior. 'Generate' implies creation but unclear if it's side-effect-free or returns data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no wasted words. Immediately states the primary action and key features. Efficient and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Minimal description for a 4-param tool with no output schema. Doesn't explain return format, provide examples, or cover edge cases. Adequate but could be more helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for each parameter. The description adds 'various formats' and 'customizable' but doesn't go beyond schema details. Baseline 3 due to high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb 'Generate' and resource 'QR codes', and highlights key customizations (formats, error correction, sizes). Without siblings, no need for differentiation, but it accurately captures the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use vs alternatives (though no siblings exist), no prerequisites, typical use cases, or exclusions. Purely functional description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
There is only one tool, so no risk of confusion or overlap with other tools.
The single tool uses a clear verb_noun pattern (generate-qrcode), and with only one tool, consistency is not an issue.
One tool is perfectly appropriate for a server dedicated solely to generating QR codes, as the scope is narrow and focused.
The tool covers the core functionality of generating QR codes with customization options, but lacks features like batch generation or output validation, though these are not essential for a basic server.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
A Model Context Protocol server for Wix AI tools
The BigQuery remote MCP server is a fully managed service that uses the Model Context Protocol to connect AI applications and LLMs to BigQuery data sources. It provides secure, standardized tools for AI agents to list datasets and tables, retrieve schemas, generate and execute SQL queries through natural language, and analyze data—enabling direct access to enterprise analytics data without requiring manual SQL coding.
Related MCP Servers
- AlicenseAqualityAmaintenanceA Model Context Protocol server that provides LLM Agents with a comprehensive toolset for IP geolocation, network diagnostics, system monitoring, cryptographic operations, and QR code generation.543718Apache 2.0
- AlicenseAqualityDmaintenanceEnables generation of QR codes from text or URLs in multiple formats (DataURL, SVG, terminal display) with customizable options like error correction, colors, and size. Supports batch processing of multiple QR codes and integrates seamlessly with MCP-compatible clients.44MIT
- FlicenseNot gradedqualityDmaintenanceEnables the generation of QR codes in PNG, SVG, Base64, and ASCII formats via Model Context Protocol clients. Users can save codes directly to local files or display them as terminal-friendly art through natural language commands.
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to generate QR codes for URLs, WiFi, contacts, and more with structured parameters.3,9584MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jwalsh/mcp-server-qrcode'
If you have feedback or need assistance with the MCP directory API, please join our Discord server