Add Xquik plugin

[kriptoburak]

Summary

• Add Xquik as a Memoh plugin manifest.
• Register the remote HTTP MCP endpoint with user-provided API key auth.
• Use public Xquik docs and icon URLs.

Validation

• Duplicate gate: no existing Xquik PR or issue in memohai/supermarket.
• YAML parse check passed for plugins/xquik/plugin.yaml.
• Link checks: icon 200, docs 200, MCP endpoint 401 expected without auth.
• bun install --frozen-lockfile
• bun run build

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1044b582bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the required x-api-key header mapping

For API-key installs, Xquik's MCP docs show clients must send the secret as the x-api-key header (for example, .mcp.json uses headers: { "x-api-key": ... }). This manifest records XQUIK_API_KEY via auth_ref, but the HTTP MCP resource has no headers mapping, so consumers downloading this plugin can prompt for the secret yet have no machine-readable way to attach it, and connections to https://xquik.com/mcp will be unauthenticated/401 unless the user hand-edits config. Please add the header mapping or switch to the OAuth auth requirement if that is the intended path.

Useful? React with 👍 / 👎.