MCP server for QR codes: Use Same-QR in Claude, ChatGPT, Cursor, and Codex

What an MCP server is

MCP stands for Model Context Protocol, an open standard for connecting AI assistants to other services. An MCP server describes the tools of a service, such as "create code" or "read statistics." The assistant sees these tools and calls them when a task requires them.

What the Same-QR MCP server provides

The server is located at https://sameqr.com/api/mcp and offers exactly the tools of the REST API, with the same names, checks, and tariff limits:

• Query account and plan so the assistant knows what is possible.
• List, read, create, modify, delete QR codes, and retrieve their statistics.
• Create, read, modify, publish, take offline, and delete hosted pages, including the list of designs.
• Read menus and price lists from photos or PDFs.
• Manage labels and customer projects, and read enquiries from contact forms.

Read-only tools are marked as such; delete tools are final. Anyone who wants to change targets, take a page offline, or delete it must ask the user and send along the previously read state. At most 10 such operations occur per hour via API and MCP.

Two types of authentication

ChatGPT and Claude.ai add the server as a connector. Authentication is via OAuth: You log in to Same-QR in the browser and check boxes to specify whether the app may only read, also create and edit text, or additionally change targets and delete.

Claude Code, Cursor, and Codex connect using an API key. You create it in the dashboard under Account, "Access for CLI, scripts and agents", select "read only", "read + write" (create, change names and text), or "full" (additionally change targets, take offline, delete), and store it as the environment variable SAMEQR_API_KEY. A key with "read only" has a nice side effect: The assistant will not see the write tools at all.

Setup overview

For Claude Code, a single command in the terminal is sufficient:

claude mcp add --transport http sameqr https://sameqr.com/api/mcp --header "Authorization: Bearer $SAMEQR_API_KEY"

For Cursor, an entry in ~/.cursor/mcp.json:

{ "mcpServers": { "sameqr": { "url": "https://sameqr.com/api/mcp", "headers": { "Authorization": "Bearer ${env:SAMEQR_API_KEY}" } } } }

For Codex, a section in ~/.codex/config.toml:

[mcp_servers.sameqr]
url = "https://sameqr.com/api/mcp"
bearer_token_env_var = "SAMEQR_API_KEY"

If you have installed the sameqr command line, you can display this information at any time with "sameqr mcp". Test each connection first with a read-only question, such as "Which QR codes do I have?".

Security and permissions

• For assistants that should only evaluate, use a key with "read only" access.
• Never write keys in project files; instead, set them as environment variables.
• Before making changes to printed codes, have the plan displayed.
• Revoke keys no longer needed in the dashboard. They become invalid immediately.

Conclusion: why Same-QR

Same-QR provides a complete MCP server instead of a handful of toy features: codes, statistics, menus, hosted pages, labels, and projects, equally suitable for chat assistants and coding agents. It is included in every plan, with clear permissions and the same checks as in the dashboard.

Get started right away: sign up for free at sameqr.com, two dynamic QR codes are free forever. API, CLI and MCP server are included in every plan, and the documentation is at sameqr.com/entwickler.

Frequently asked questions