ME-QR MCP Server

Overview

The ME-QR MCP Server is a cloud-hosted bridge that lets AI assistants create, update, and manage QR codes on me-qr.com on your behalf. Connect once via OAuth, and your assistant can generate QR codes for links, Wi-Fi, vCards, PDFs, images, and more — without leaving the chat.

Related MCP server: mcp-server-dashform

Key Capabilities

Authentication

The server uses OAuth 2.1 with PKCE. When you connect, your AI client opens a browser window where you log in to your me-qr.com account and approve access. No API keys or passwords are shared with the AI client — the client only ever holds an access token scoped to your account email, valid for 30 days.

Clients that can't complete a browser-based OAuth flow can authorize instead with a me-qr.com API key.

Compatible Clients

Claude Code, Claude.ai, Cursor, Windsurf, and ChatGPT (via custom connectors / Developer Mode).

Connecting

Claude Code

claude mcp add me-qr -s user --transport http https://mcp.me-qr.com/mcp

Cursor / other clients supporting .mcp.json

{
  "mcpServers": {
    "me-qr": {
      "type": "http",
      "url": "https://mcp.me-qr.com/mcp"
    }
  }
}

ChatGPT

Enable Developer Mode, add a custom connector pointing to https://mcp.me-qr.com/mcp, then authorize with your me-qr.com account.

After connecting, authorize the server once — your client will prompt you to log in to me-qr.com in a browser.

What this repository contains

This repository holds the public pieces of the ME-QR MCP Server: documentation, client manifests (.mcp.json), and the MCP registry entry (server.json).

The server itself is a hosted service at mcp.me-qr.com. Its source code, OAuth implementation, and token storage are maintained privately by the ME-QR team — see SECURITY.md for how that's handled and how to report issues.

Support

Questions or issues with the MCP server? Open an issue in this repository, or contact ME-QR support through me-qr.com.