MCP server distributed as a Python package on PyPI (bach-qr_code_by_api_ninjas) that provides access to the API Ninjas QR Code generation API
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., "@QR Code By API Ninjas MCP Server create a QR code for https://example.com with size 300 and blue foreground"
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.
用于访问 Qr Code By Api Ninjas API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-qr_code_by_api_ninjas）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: freeqrcode-mcp-server
这是一个 MCP 服务器，用于访问 Qr Code By Api Ninjas API。
PyPI 包名: bach-qr_code_by_api_ninjas
版本: 1.0.0
传输协议: stdio
pip install bach-qr_code_by_api_ninjaspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-qr_code_by_api_ninjas bach_qr_code_by_api_ninjas
# 或指定版本
uvx --from bach-qr_code_by_api_ninjas@latest bach_qr_code_by_api_ninjaspython server.py# 安装
pip install bach-qr_code_by_api_ninjas
# 运行（命令名使用下划线）
bach_qr_code_by_api_ninjas此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-qr_code_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-qr_code_by_api_ninjas", "bach_qr_code_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-qr_code_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-qr_code_by_api_ninjas", "bach_qr_code_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
v1qrcodeAPI Ninjas QR Code API endpoint. Returns a QRCode image binary specified by input parameters.
端点: GET /v1/qrcode
参数:
data (string) 必需: data to encode in the QR code.
format (string) 必需: image format to return. Must be one of the following: png, jpg, jpeg, eps, svg.
size (number): size of the QR code image to generate. The output will be a square image with (size x size) dimensions.
fg_color (string): foreground color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is 000000 (black)
bg_color (string): background color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is ffffff (white)
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
API Ninjas QR Code API endpoint. Returns a QRCode image binary specified by input parameters.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | data to encode in the QR code. | |
| format | Yes | image format to return. Must be one of the following: png, jpg, jpeg, eps, svg. | |
| size | No | size of the QR code image to generate. The output will be a square image with (size x size) dimensions. | 0 |
| fg_color | No | foreground color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is 000000 (black) | |
| bg_color | No | background color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is ffffff (white) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool 'returns a QRCode image binary,' which implies a read-only operation, but doesn't disclose important behavioral traits like rate limits, authentication requirements, error handling, or what 'binary' means in practice (e.g., base64 encoding, raw bytes). The description is minimal and leaves critical behavioral aspects unspecified.
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?
The description is a single, efficient sentence that gets straight to the point: 'API Ninjas QR Code API endpoint. Returns a QRCode image binary specified by input parameters.' It's appropriately sized and front-loaded, with no wasted words. However, it could be slightly more structured by explicitly mentioning the core function first, so it doesn't achieve a perfect score.
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?
Given that there are no annotations and no output schema, the description is incomplete for a tool with 5 parameters. It doesn't explain what the return value looks like (e.g., format of the binary, potential errors), nor does it provide behavioral context. The description is too minimal to adequately support an AI agent in using this tool correctly.
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?
The input schema has 100% description coverage, with all 5 parameters well-documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter info in the description.
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?
The description clearly states the tool's purpose: 'Returns a QRCode image binary specified by input parameters.' It specifies the verb (returns), resource (QRCode image binary), and scope (specified by input parameters). However, it doesn't distinguish from siblings since there are none, so it cannot achieve the full differentiation required for a score of 5.
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?
The description provides no guidance on when to use this tool versus alternatives. It simply states what the tool does without mentioning any context, prerequisites, or exclusions. There are no siblings to compare against, but the description still lacks basic usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0v1qrcodeWith only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'v1qrcode' follows a clear pattern without deviations.
A single tool is too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. Typically, a well-scoped server should have 3-15 tools to cover basic operations effectively.
The server is severely incomplete for generating QR codes, as it only provides a basic creation tool without options for customization, error correction, or different output formats, which are common in QR code APIs.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Generate QR codes for URLs, PIX, Wi-Fi, vCards, WhatsApp and more. For AI agents.
Free styled QR code generator API. Create QR codes with custom colors, logos, and frame templates. Supports URL, WiFi, Email, Phone, SMS. No API keys required.
Generate static QR codes (URL, WiFi, vCard, pixel art) and decode QR images. Codes never expire.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-qr-code-by-api-ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server