Use your workspace API key
Create an API key in your user center when your plan includes API access. Choose read access for viewing assets and analytics; add write access only when the client should create or edit content. Keep the key private.
Connection details
Add a remote MCP server using this URL. Your client must support HTTP JSON responses and an Authorization header.
https://qrcodetransfer.com/api/mcp Authorization: Bearer YOUR_API_KEY
For local testing, use the same endpoint on your local backend address. A connected client can list assets, get an asset, create an asset, update an asset and read analytics. Workspace permissions, plan limits and asset validation still apply.
Check before sharing
Review destinations and form content before publishing or printing. An API key gives access to its own workspace only. Revoke the key in your user center when you no longer need the connection.
The endpoint is available, but compatibility must be checked with the client you choose. Direct client sign-in is not available; do not assume a marketplace connector is active merely because it supports MCP.