QRX

Option A: plugin (MCP server plus the QRX skill)

/plugin marketplace add qrxcodes/qrx-mcp
/plugin install qrx@qrx

When you enable the plugin, Claude Code asks for your QRX API key and keeps it in your system's credential store. The plugin also adds the qrx skill, which teaches Claude how to write good art prompts, wait for the code and prepare it for print.

Option B: MCP server only

claude mcp add --transport http qrx https://qrx.codes/mcp \
  --header "Authorization: Bearer $QRX_API_KEY" --scope user

Or commit this to a project's .mcp.json so the whole team gets it (each person sets their own QRX_API_KEY):

{
  "mcpServers": {
    "qrx": {
      "type": "http",
      "url": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer ${QRX_API_KEY}" }
    }
  }
}

When OAuth is live: claude mcp add --transport http qrx https://qrx.codes/mcp, then run /mcp and sign in.

Claude Desktop uses the same connector settings as claude.ai; you don't edit claude_desktop_config.json for a remote server.

1. Open Customize → Connectors, select + Add, then Add custom connector. On Team and Enterprise, an Owner adds it under Organization settings → Connectors first.
2. Name: QRX. URL: https://qrx.codes/mcp.
3. Authentication:
   • Now: choose the fixed-credentials option and, under Request headers, add Authorization with the value Bearer qrx_live_….
   • When OAuth is live: choose Sign in when needed; Claude shows a Connect button the first time you make a code.
4. Save, then turn QRX on in a chat from the connectors menu.

Free Claude plans can add one custom connector.

ChatGPT's custom MCP servers take OAuth or no authentication, not API keys, so QRX in ChatGPT needs the OAuth release.

When OAuth is live:

1. Open chatgpt.com/plugins on the web, select +, then Add custom MCP server.
2. Name: QRX. Server URL: https://qrx.codes/mcp.
3. Authentication: OAuth. Accept the risk warning and select Create as a plugin.
4. Ask for a QR code; ChatGPT asks you to sign in to QRX the first time.

Workspace admins can restrict custom MCP servers on Business and Enterprise plans.

Use the Install in Cursor button above, or add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "qrx": {
      "url": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer ${env:QRX_API_KEY}" }
    }
  }
}

When OAuth is live: drop the headers block; Cursor prompts you to sign in.

Use the Install in VS Code button above (it asks for your key and stores it securely), or add this to .vscode/mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "qrx-api-key",
      "description": "QRX API key (starts with qrx_)",
      "password": true
    }
  ],
  "servers": {
    "qrx": {
      "type": "http",
      "url": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer ${input:qrx-api-key}" }
    }
  }
}

From a terminal:

code --add-mcp '{"name":"qrx","type":"http","url":"https://qrx.codes/mcp","headers":{"Authorization":"Bearer ${input:qrx-api-key}"},"inputs":[{"type":"promptString","id":"qrx-api-key","description":"QRX API key","password":true}]}'

When OAuth is live: {"type": "http", "url": "https://qrx.codes/mcp"} is enough.

Edit mcp_config.json (macOS/Linux ~/.config/devin/mcp_config.json, Windows %APPDATA%\devin\mcp_config.json; older Windsurf installs use ~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "qrx": {
      "serverUrl": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer ${env:QRX_API_KEY}" }
    }
  }
}

Note the key is serverUrl, not url.

Open MCP Servers → Configure MCP Servers and add to cline_mcp_settings.json:

{
  "mcpServers": {
    "qrx": {
      "type": "streamableHttp",
      "url": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer qrx_live_…" },
      "disabled": false,
      "autoApprove": ["list_styles", "get_qr_code", "list_qr_codes", "get_account", "get_profile"]
    }
  }
}

When OAuth is live: remove headers and use Authorize OAuth on the server.

Add to settings.json:

{
  "context_servers": {
    "qrx": {
      "url": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer qrx_live_…" }
    }
  }
}

When OAuth is live: leave out headers; Zed runs the MCP sign-in flow when no Authorization header is set.

Run goose configure → Add Extension → Remote Extension (Streamable HTTP), enter https://qrx.codes/mcp, and add the header Authorization: Bearer qrx_live_…. Or edit config.yaml (macOS/Linux ~/.config/goose/config.yaml, Windows %APPDATA%\Block\goose\config\config.yaml):

extensions:
  qrx:
    name: qrx
    type: streamable_http
    enabled: true
    uri: https://qrx.codes/mcp
    headers:
      Authorization: "Bearer qrx_live_…"
    timeout: 300

Add to ~/.codex/config.toml:

[mcp_servers.qrx]
url = "https://qrx.codes/mcp"
bearer_token_env_var = "QRX_API_KEY"

When OAuth is live: codex mcp add qrx --url https://qrx.codes/mcp, then codex mcp login qrx.

gemini mcp add --transport http --header "Authorization: Bearer $QRX_API_KEY" qrx https://qrx.codes/mcp

Or in ~/.gemini/settings.json (note httpUrl, which selects Streamable HTTP):

{
  "mcpServers": {
    "qrx": {
      "httpUrl": "https://qrx.codes/mcp",
      "headers": { "Authorization": "Bearer $QRX_API_KEY" }
    }
  }
}

The skills/qrx folder follows the Agent Skills standard, so the same skill works in Codex, Gemini CLI, GitHub Copilot, Cursor, Goose and others. Install it with the cross-agent installer:

npx skills add qrxcodes/qrx-mcp

The skill expects the QRX MCP server to be connected (see your client above), or a QRX_API_KEY for the REST API.

gemini extensions install https://github.com/qrxcodes/qrx-mcp

The extension asks for your QRX API key and stores it in your system keychain.

Point a Streamable HTTP client at https://qrx.codes/mcp and send Authorization: Bearer qrx_… (or X-API-Key: qrx_…). Clients that only speak stdio can use a bridge such as mcp-remote:

{
  "mcpServers": {
    "qrx": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://qrx.codes/mcp", "--header", "Authorization:Bearer ${QRX_API_KEY}"],
      "env": { "QRX_API_KEY": "qrx_live_…" }
    }
  }
}