QRay

link.qrayPublished by qray.linkOfficial publisherv0.2.3Updated Nov 1, 2026

Create and edit dynamic QR codes from AI assistants via the QRay agent MCP endpoint.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote QRay MCP endpoint that lets an AI assistant create and edit dynamic QR codes through the QRay service.

What you can do
  • Create dynamic QR codes from an assistant conversation.
  • Edit existing dynamic QR codes, such as changing where they point.
  • Work with the QRay account tied to the supplied API key.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to generate or update dynamic QR codes for links, campaigns or printed material without leaving the chat, and you already have a QRay account.
Requirements
A remote MCP endpoint at go.qray.link over streamable HTTP. A QRay API key from the QRay dashboard, sent as a bearer token in the Authorization header. No local runtime or environment variables are declared.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. Editing dynamic QR codes changes where already-distributed codes point, so changes can affect live campaigns. QR code data and account actions are handled by the QRay service.

Installation

In SourceWeft

  1. Open QRay in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/link.qray%2Fqray/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "qray": {
      "type": "http",
      "url": "https://go.qray.link/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.3LatestNov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.