Set up Qreates in your agent
How connecting works
Open the toolkit page without an account and paste its message into your agent. Your agent handles commands and settings and shows you any required clicks. Sign in or create a Qreates account when prompted, then choose Allow. After sign-in, your agent reads Qreates' instructions, checks the connected account, asks for the image to fix (a reference image showing the correct version is optional: simple text or number changes work from your words, and it helps most with logos and special lettering), pre-selects the area, and sends you the Qreates link. Check the box and press Continue there to start the repair.
Claude Code
Connect Qreates for me and handle the setup yourself. Never ask me to open a terminal or edit a settings file. If you need a click from me, name the button and where it is. Before setup, inspect the effective existing server named "qreates". Parse its URL hostname; if it is not qreates.com, or its address differs from the intended endpoint below, stop and warn me with both addresses. Never silently replace it. Intended endpoint: https://review.qreates.com/api/mcp. 1) Check claude mcp list first; if this endpoint is already installed, keep its exact server name and skip installation. Otherwise: Run this command yourself: claude mcp add --scope user --transport http qreates https://review.qreates.com/api/mcp. 2) Complete this required permission step yourself: Required: Check claude mcp list and the existing permissions.allow entries first. The rule is mcp__ followed by the exact server name that claude mcp list shows for the Qreates server (for the install this message performs, qreates gives mcp__qreates). Merge that single entry into permissions.allow in ~/.claude/settings.json (user settings). If that name is not covered, add its matching rule without reinstalling or renaming the server. Preserve every existing key and permissions.allow entry; never replace the file. Confirm in one line: Qreates tools will run without a prompt each time; Qreates' own spending limits still apply. 3) Then tell me to start a new chat and say 'connect me to Qreates' — do not tell me to quit or use a terminal. 4) In that new chat, start the Qreates sign-in; when a browser page opens I'll sign in (or create my account) and choose Allow. Tell me where to check: In the Claude desktop app's Code tab, Qreates will not appear under /mcp. It's connected when 'connect me to Qreates' or listing your projects works. In the terminal, claude mcp list or /mcp shows it. 5) After sign-in, read Qreates' instructions and call get_account, then confirm in one plain sentence which account is connected using account_label (say you can't tell if it is null); never print my email or any ID. 6) Then ask me for the image to fix. A reference image is optional: for simple text or number changes, start from my words; for a logo, special lettering or a product's exact look, if I haven't given one, ask me once if I have an image of the correct version, then start either way. Start the repair: pre-select the area, then open the Qreates repair page yourself in your built-in browser; send me the link only if it will not open, and say why. Stay in this same turn: keep calling wait_for_detail_fix until I've pressed Continue and the repair finishes (about 10 minutes at most), then show me the result in chat. If I haven't acted by then, say one plain line telling me to say 'check' once I have pressed Continue so you can show the result. If the page asks me to sign in, I will. I'll check the box and press Continue there; that's my approval. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools.
Paste once. Your agent handles the setup and shows you any required clicks. Sign in and choose Allow when prompted. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Required: Check claude mcp list and the existing permissions.allow entries first. The rule is mcp__ followed by the exact server name that claude mcp list shows for the Qreates server (for the install this message performs, qreates gives mcp__qreates). Merge that single entry into permissions.allow in ~/.claude/settings.json (user settings). If that name is not covered, add its matching rule without reinstalling or renaming the server. Preserve every existing key and permissions.allow entry; never replace the file. If an existing qreates connection uses a non-qreates.com or different address, stop and check it before replacing it.
Codex
Connect Qreates for me and handle the setup yourself. Never ask me to open a terminal or edit a settings file. If you need a click from me, name the button and where it is. Before setup, inspect the effective existing server named "qreates". Parse its URL hostname; if it is not qreates.com, or its address differs from the intended endpoint below, stop and warn me with both addresses. Never silently replace it. Intended endpoint: https://review.qreates.com/api/mcp. 1) Add Qreates to my Codex configuration yourself, keeping my other settings: [mcp_servers.qreates] url = "https://review.qreates.com/api/mcp" 2) Tell me to quit and reopen Codex, then to open the MCP servers list and click Authenticate next to Qreates. 3) When a browser page opens I'll sign in (or create my account) and choose Allow. 4) After sign-in, read Qreates' instructions and call get_account, then confirm in one plain sentence which account is connected using account_label (say you can't tell if it is null); never print my email or any ID. 5) Then ask me for the image to fix. A reference image is optional: for simple text or number changes, start from my words; for a logo, special lettering or a product's exact look, if I haven't given one, ask me once if I have an image of the correct version, then start either way. Start the repair: pre-select the area, then open the Qreates repair page yourself in your built-in browser; send me the link only if it will not open, and say why. Stay in this same turn: keep calling wait_for_detail_fix until I've pressed Continue and the repair finishes (about 10 minutes at most), then show me the result in chat. If I haven't acted by then, say one plain line telling me to say 'check' once I have pressed Continue so you can show the result. If the page asks me to sign in, I will. I'll check the box and press Continue there; that's my approval. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts.
Paste once. Your agent handles the setup and shows you any required clicks. Sign in and choose Allow when prompted. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts. If an existing qreates connection uses a non-qreates.com or different address, stop and check it before replacing it.
Cursor
Connect Qreates for me and handle the setup yourself. Never ask me to open a terminal or edit a settings file. If you need a click from me, name the button and where it is. Before setup, inspect the effective existing server named "qreates". Parse its URL hostname; if it is not qreates.com, or its address differs from the intended endpoint below, stop and warn me with both addresses. Never silently replace it. Intended endpoint: https://review.qreates.com/api/mcp. 1) Merge Qreates into my Cursor mcp.json yourself, keeping my other servers: { "mcpServers": { "qreates": { "url": "https://review.qreates.com/api/mcp" } } }. 2) Tell me only if Cursor needs a reload and name the exact button. 3) Tell me to click sign in next to qreates in Cursor's MCP settings. When a browser page opens I'll sign in (or create my account) and choose Allow. 4) After sign-in, read Qreates' instructions and call get_account, then confirm in one plain sentence which account is connected using account_label (say you can't tell if it is null); never print my email or any ID. 5) Then ask me for the image to fix. A reference image is optional: for simple text or number changes, start from my words; for a logo, special lettering or a product's exact look, if I haven't given one, ask me once if I have an image of the correct version, then start either way. Start the repair: pre-select the area, then open the Qreates repair page yourself in your built-in browser; send me the link only if it will not open, and say why. Stay in this same turn: keep calling wait_for_detail_fix until I've pressed Continue and the repair finishes (about 10 minutes at most), then show me the result in chat. If I haven't acted by then, say one plain line telling me to say 'check' once I have pressed Continue so you can show the result. If the page asks me to sign in, I will. I'll check the box and press Continue there; that's my approval. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts.
Paste once. Your agent handles the setup and shows you any required clicks. Sign in and choose Allow when prompted. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts. If an existing qreates connection uses a non-qreates.com or different address, stop and check it before replacing it.
Claude
Before connecting, check any existing qreates connection against the address above. If its hostname is not qreates.com or its address differs, stop and check it before replacing it. 1. In Claude, open Customize → Connectors → Add custom connector.
2. Name it Qreates, paste this address, then Connect.
3. Sign in with your Qreates account and choose Allow. Then ask Claude for a repair.
https://review.qreates.com/api/mcp
Works in the Claude desktop app and claude.ai. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts. If an existing qreates connection uses a non-qreates.com or different address, stop and check it before replacing it.
ChatGPT
Before connecting, check any existing qreates connection against the address above. If its hostname is not qreates.com or its address differs, stop and check it before replacing it. On ChatGPT web, check that your plan and workspace allow custom apps with actions. Open Settings → Apps → Create, paste this address and choose OAuth. Select Scan Tools, sign in, then Create. If Create is missing, your workspace owner may need to enable it.
https://review.qreates.com/api/mcp
Advanced. Sign in with your Qreates account and choose Allow when prompted. Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Use your client's server-specific approval controls to always allow Qreates tools if you want fewer prompts. If an existing qreates connection uses a non-qreates.com or different address, stop and check it before replacing it.
Advanced connection setup
Keep creative work in Projects. Generate with generate_image, or open_prompt_bar to review and press Send; use named-video tools for video. Never drive the Qreates website or guess URLs; open only links returned by tools. Before setup, check any existing qreates server. If its hostname is not qreates.com or it differs from the address shown here, stop and confirm the intended endpoint before replacing it.
Claude Code manual setup
claude mcp add --scope user --transport http qreates https://review.qreates.com/api/mcp
- Run the command in a terminal where Claude Code is installed.
- Required: Check claude mcp list and the existing permissions.allow entries first. The rule is mcp__ followed by the exact server name that claude mcp list shows for the Qreates server (for the install this message performs, qreates gives mcp__qreates). Merge that single entry into permissions.allow in ~/.claude/settings.json (user settings). If that name is not covered, add its matching rule without reinstalling or renaming the server. Preserve every existing key and permissions.allow entry; never replace the file.
- Qreates tools will run without a prompt each time; Qreates' own spending limits still apply.
- Start a new chat and say 'connect me to Qreates'. Complete sign-in and choose Allow.
- In the Claude desktop app's Code tab, Qreates will not appear under /mcp. It's connected when 'connect me to Qreates' or listing your projects works. In the terminal, claude mcp list or /mcp shows it.
Codex manual setup
[mcp_servers.qreates] url = "https://review.qreates.com/api/mcp"
- Add this server block to your Codex configuration, keeping your other settings.
- Quit and reopen Codex, then open the MCP servers list and click Authenticate next to Qreates. Sign in and choose Allow.
Cursor manual setup
https://review.qreates.com/api/mcp
- In Cursor, open Settings → MCP and add a new server.
- Copy the address above and paste it as the server URL. Keep your other servers.
- Click sign in next to qreates, sign in with your Qreates account and choose Allow. Reload only if Cursor requests it.
Key fallback
Create an agent key in Settings → Agents & API. Keep it private and configure it locally. Use this header form with your key.
claude mcp add --scope user --transport http qreates https://review.qreates.com/api/mcp --header "Authorization: Bearer your key"
Not yet verified
Grok Bot
Qreates setup in Grok Bot is not yet verified. Use another listed agent for now.
https://review.qreates.com/api/mcp
Before paid work
You approve each repair by pressing Continue on the Qreates page.
Where things land
Repairs land in Assets, and charges appear in Credits. The region step and finished work live in Your repairs.