What is Quey?
Quey is a Chrome extension + local MCP server that gives your coding agents live browser context before they edit code. Instead of describing UI problems in chat, you click the element, type your instruction, and send a structured capture directly to Claude Code, Codex, Cursor, or any MCP-aware agent.
How it works
There are three moving parts:
01
Chrome extension
Overlays a toolbar on any web page. Click an element, type an instruction, and send a capture — all without leaving the browser.
02
Local MCP bridge
Runs inside your repo. Receives captures from the extension and exposes them to your coding agent via HTTP and MCP tools.
03
Your coding agent
Reads the capture through MCP, edits the right file at the right line, and resolves the request with a summary.
Key concepts
Capture — the structured payload sent when you select a UI element. It includes the selector path, source file hint, your instruction, and a snapshot of the visible element. Captures can be in one of four states: pending, acknowledged, resolved, or dismissed.
Session — a logical grouping of captures for a single browser tab or workspace. The MCP bridge maintains per-session FIFO queues so agents never race themselves.
Provider — the agent that processes your captures. Quey supports Claude (via Claude Code CLI or SDK), OpenAI Codex, and Cursor. You choose the provider per capture from the agent panel.
Approval mode — controls whether the agent runs immediately or waits for your approval. Ask always pauses, Smart pauses for file-editing runs, Allow runs immediately.
server) by default — this keeps the HTTP bridge and MCP stdio in the same process so captures are shared. See MCP server modes for the full picture.