Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Qiksy Bridge: your open Chrome tab for AI agents

    1

    Free MCP server that gives Claude Code, Cursor, Codex and other agents the Chrome tab you already have open: your logins, live page, failed requests with server bodies, forms in one call, screenshots.

    Free

    Security scanned
    Qiksy Bridge: your open Chrome tab for AI agents

    Qiksy Bridge: your open Chrome tab for AI agents

    Example session with this skill installed

    I'm logged in to our staging admin in Chrome. Open the tab with /settings/billing, fill the billing form with a Polish company (NIP 5260250995, Warsaw), press Save, and tell me why it fails.

    • Read your context and instructions
    • Compiled the qiksy bridge

    What happened

    I worked in your open tab (staging admin, already signed in), not in a new browser.

    1. qa_tabs found the tab /settings/billing.
    2. qa_fill_json filled the form in one call:
    FieldValueTook it
    Company nameKowalski Sp. z o.o.yes
    CountryPoland (custom dropdown)yes
    NIP5260250995yes
    CityWarsawyes
    Postal code00-950yes
    1. qa_click { name: "Save" } pressed Save. The page showed a red toast «Something went wrong» for two seconds.
    2. qa_findings caught the request behind it:
    POST /api/billing/profile  422
    {"error":"vat_id_format","detail":"expected PL prefix, got 5260250995"}
    

    Why it fails

    The backend wants the VAT id with the country prefix (PL5260250995), while the form label says «NIP» and accepts digits only. The UI swallows the 422 and shows a generic toast, so a user never learns what to fix.

    Suggested fix

    • Add the PL prefix on the client before sending, or accept both forms on the server.
    • Show the server's detail under the NIP field instead of the generic toast.

    Want me to retry with PL5260250995 to confirm?

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Your agent can already write the code. What it usually cannot do is look at the app the way you do: signed in, on staging, with the data you set up an hour ago. Playwright and Puppeteer start a fresh, empty browser, so the agent ends up testing a login page.

    Qiksy Bridge connects the agent to the Chrome you already have open. Same profile, same cookies, same tab. It works in a background tab and never steals focus.

    What the agent gets

    • The page as an accessibility tree with refs, plus boxes in CSS pixels when it needs geometry.
    • Console errors and failed requests together with the server's error body, so "something went wrong" turns into the real 422 and its message.
    • A whole form in one call: qa_fill_json with field labels as keys. Custom dropdowns, calendars, cascaders, trees, tags and time pickers included.
    • Screenshots of the page or one element, with password and card fields covered first.
    • Computed styles with the design token behind them, an accessibility audit, a tab order walk.
    • qa_mock to answer the page's own requests from a rule: a 500, an empty list, a slow reply.
    • qa_watch for things that happen later: a toast, a request on a timer, a late row.

    Safety

    Reading is on by default. Clicking, typing and navigating need a separate "Agent control" switch in the extension popup, and the agent is told to stop and ask when it is off. No arbitrary JavaScript runs in your page: every verb names an element, never a program.

    Price

    Free. The Chrome extension, the npm package qiksy-mcp and this skill cost nothing. Made by Qiksy, a small studio from Ukraine.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Needs the free Qiksy Chrome extension, so Chrome only. No arbitrary JavaScript in the page and no captcha solving. Clicking, typing and navigating need a one time "Agent control" switch in the extension popup. Screenshots need the tab in front.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    • Free with an Agensi account

    Software
    Qiksy Chrome extension (free)qiksy-mcp (npm)Node.js 18+Google Chrome

    Permissions

    Terminal / Shell
    Browser
    Network Access
    Environment Variables
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    Playwright and Puppeteer start their own browser, with no cookies and no logins. Qiksy Bridge works in the Chrome you already have open, so the agent sees the app the way you do: signed in, on the right environment, with your data.

    Any agent that speaks MCP: Claude Code, Cursor, Codex, VS Code, Windsurf, Cline and others. On the browser side you need Google Chrome with the free Qiksy extension, and Node.js 18 or newer for npx qiksy-mcp.

    Install the Qiksy extension from the Chrome Web Store, open its popup, switch on "Agent bridge · MCP" and press Generate to get a token. Then add the server to your agent with npx qiksy-mcp and that token (the exact lines are in the skill). qa_status answering with your page means it works.

    Reading the page as an accessibility tree, text, computed styles and tables of values; console errors and failed requests with the server's error body; screenshots; filling a whole form in one call, custom dropdowns and date pickers included; clicks and key presses; answering the page's requests from a rule to test errors; watching for things that happen later.

    The bridge listens only on your own machine (127.0.0.1) and needs the token from your extension. Reading is on by default; acting on the page needs a separate switch in the popup. It never runs arbitrary JavaScript in your page and covers password and card fields before any screenshot.

    New in Agents & Orchestration

    Free