01
Structured payloads
Expose the same capture model to tools that understand MCP.
MCP bridge
Bring live UI context into MCP workflows.
Quey packages selected element details into agent-ready context. A stable, structured capture contract that any MCP-compatible tool can consume — Claude Code, Codex, Cursor, ChatGPT, and beyond.
Why it matters
Built for the browser-to-agent handoff.
02
Tool-neutral
Keep the browser capture layer separate from any single agent provider.
03
Schema-first
Use stable fields for element identity, location, design, and metadata.
Workflow
The same simple loop on every page.
Each product surface uses the same structure so visitors can compare capabilities without relearning the page.
01
Connect
Run the provider
Start the local bridge that exposes Quey context to compatible tools.
02
Select
Capture the UI
Choose the element or region from the browser page.
03
Consume
Use the payload downstream
Let MCP-aware tools read the structured context and act on it.
Portable context
Designed around a stable capture contract.
Quey acts as the browser context layer for agent ecosystems — a stable, structured capture contract that any MCP-compatible tool can consume.
Mode-aware payloads
Element location
Design tokens
Region metadata
Bridge the browser
Make selected UI available to MCP tools.
Use Quey to capture the real page state, then pass it into your agent workflow.
Add to Chrome