Cursor with MCP: Set up Same-QR in the editor and manage QR codes

Cursor and MCP in brief

Cursor is a code editor with a built-in AI assistant that knows your project and performs tasks across multiple files. Through MCP, it also uses tools from other services. For web developers and agencies, this means: websites and QR codes pointing to them can be maintained in the same tool.

Step 1: Create key

In the Same-QR dashboard under Account, section "Access for CLI, scripts and agents", you create a key, "read only" for evaluations, "read + write" for creation, or "full" if targets are also to be changed. Make it available as the environment variable SAMEQR_API_KEY before starting Cursor.

Step 2: Entry in mcp.json

Open the file ~/.cursor/mcp.json or create it, and add Same-QR:

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

The entry refers only to the environment variable; the key itself is not in the file. If there are already other servers there, you add sameqr within mcpServers. "sameqr mcp" also shows you the entry.

Step 3: Test

Restart Cursor and ask the assistant: "Which QR codes do I have at Same-QR?" If the list appears, the connection is established.

Step 4: Relaunching a client page

During a relaunch, addresses change. You keep track of the redirects on the website, but printed QR codes are easily forgotten. With Cursor, this becomes part of the same task:

• Have the assistant list all of the customer's codes with their current target.
• Have the list compared with the mapping of old and new addresses in the project.
• Request a plan: which code should go to which new address.
• Review the plan, confirm it, and only then have it implemented.
• Scan some codes after the migration with your mobile phone.

If the website is connected to Same-QR, which is possible from the Pro plan onwards, Same-QR will additionally suggest the new address itself after a relaunch. Changes are only made after confirmation.

Security

• Use a "read only" key for evaluations, so the assistant does not see any write tools.
• Never write the key directly in mcp.json or in project files.
• Have changes to printed codes shown as a plan first.
• Revoke the key when the project is complete.

Conclusion: why Same-QR

Same-QR brings your QR codes into the editor with a single entry in mcp.json. You get the full range of functions, clear rights, and the certainty that no printed code will lead to a dead end after a relaunch. In every plan.

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