Claude Kapture Browser Automation connectorWhat Claude can do in your browser with Kapture.
The Claude Kapture Browser Automation connector exposes 21 tools. 7 read what a browser tab shows, 14 act in it, from clicking to closing tabs, and 0 are left undocumented. Below: what Claude sees, what it can do in the page, and the setup it needs first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can drive your browser
Instead of describing a web page to Claude or pasting screenshots, you let it work in the browser tab itself. Kapture, a Claude Desktop extension paired with a Chrome DevTools panel, lets Claude open pages, click, type into fields, take screenshots and read the page's HTML or console, while you watch it happen.
Test a form the way a visitor would. A product manager checking a sign-up page asks Claude to try it: Claude uses navigate to open the page, fill to enter an email, click on the submit button, then screenshot to show the result.
Debug what the page is really saying. When a button seems dead, console_logs returns the tab's console messages and uncaught errors, newest first, and dom pulls the HTML around the element so Claude can explain the problem.
Gather information across tabs. list_tabs shows which tabs are connected, new_tab opens another, and elements collects matching items on a page, such as every external link.
What it does not do: it only reaches tabs where the Kapture DevTools panel is open and connected, not your whole browser. Its interaction tools act on the first element a selector matches. Nothing runs on its own either: no tool watches a page and reacts to a change; Claude acts only while it answers you. For scheduled browser jobs, the Integrations hub covers automation platforms.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and something outside it, here your browser, so Claude can use it while it answers you.
- Tool
- One named capability a connector gives Claude. Claude chooses the ones it needs on its own, and the directory sheet lists all of them.
- Approval
- The confirmation Claude waits for before an action that changes something, shown in the conversation at the moment it applies.
- Directory
- The official catalogue of connectors, where each one has a sheet with its publisher, its purpose and the tools it exposes.
- MCP
- The shared standard behind connectors: it lets an assistant like Claude work with an outside program, here a browser extension.
Connect Kapture to Claude in three steps
- 01
Find Kapture in Claude Desktop
Kapture is a desktop extension, so this happens in Claude Desktop. Anthropic's general steps go through Customize then Connectors; no Claude page describes this extension's own screens, so they may differ. On a Team or Enterprise workspace, an Owner or Primary Owner enables it before members each connect.
- 02
Start the connection
In Anthropic's general flow, you start from Connect on the connector's row and, if the link breaks, Disconnect and connect again. Kapture's own guide adds its setup in the browser, covered in the tip below.
- 03
Check what you grant
If a screen asks you to grant access, read it before accepting: it is not Claude's, and it defines what the access covers. Whatever it shows, Anthropic's default rule is that Claude asks before each action.
The 21 tools, split by what they do
Kapture Browser Automation gives Claude 21 tools: 7 that read your account, 14 that change something in it.
Seven tools read a tab, fourteen act in it. Names stay exactly as Claude shows them.
- 7 read
- 14 write
What Claude reads (7)
7 toolsSeven tools that look at tabs and pages and leave them as they are.
list_tabs
Returns every browser tab currently connected to Kapture, the starting point Claude needs before it can work in any of them.
tab_detail
Gives comprehensive information about one connected tab, so Claude can confirm where it is before reading or acting on the page.
screenshot
Captures the page or a single element as an image, with compression options, so Claude and you can see the visual result rather than guess it.
dom
Pulls the HTML content of the page, which lets Claude read the structure behind what is displayed.
elements
Collects every element matching a selector, filtered by visibility, so Claude can count or list items on a page in one go instead of one by one.
elementsFromPoint
Reports all the elements sitting at given screen coordinates, useful to find out what really lies under a spot on the page.
console_logs
Reads the tab's console as DevTools shows it, including messages, uncaught exceptions and browser entries, listed newest first, so recent problems come up at the top.
What Claude does in the browser (14)
14 toolsFourteen tools that act in the browser: navigation, clicks, typing, tabs. No source details their confirmation, so the general rule below applies.
navigate
Approval: see the ruleLoads a web address in a connected tab, with an optional time limit for the page to load. The tab leaves whatever it was showing.
back
Approval: see the ruleGoes back in the tab's browsing history. Kapture's guide documents back and forward together, as history navigation, and says nothing more about either.
forward
Approval: see the ruleGoes forward in the tab's browsing history, the second half of the pair the guide calls history navigation, with no further detail.
reload
Approval: see the ruleReloads the current page, much like pressing F5, so Claude sees a fresh version of it.
show
Approval: see the ruleBrings a tab to the foreground and focuses it, so the page Claude is working on is the one you see.
click
Approval: see the ruleClicks an element, or blindly at a screen coordinate, which can reach inside frames. It returns the selector of what was clicked.
hover
Approval: see the rulePlaces the pointer over an element, by selector or coordinate, to trigger whatever the page shows on hover, such as a menu or a tooltip.
focus
Approval: see the ruleGives focus to an element. Kapture's guide documents focus and blur together, as managing element focus, and says nothing more about either.
blur
Approval: see the ruleRemoves focus from an element, the second half of the pair the guide calls managing element focus, with no further detail.
fill
Approval: see the ruleWrites a value straight into a text input, which is fast. Kapture's guide notes that some inputs ignore this method.
select
Approval: see the ruleChooses an option in a dropdown list, so a form can be completed end to end.
keypress
Approval: see the ruleSends keyboard events to the page, with support for modifier keys.
new_tab
Approval: see the ruleOpens a fresh browser tab; according to the guide, it lands on Kapture's how-to page.
close
Approval: see the ruleCloses a browser tab, one of the two tools that manage tabs, alongside new_tab.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on your behalf. The request appears in the conversation when it is relevant.
On Team and Enterprise workspaces, owners decide whether a member may let some actions pass without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping screenshots and reading on while blocking clicks and typing. That setting binds everyone, and nobody lifts it from a personal account. Claude also acts with the rights of the person who connected, and in a browser that means whatever that person is signed in to.
Which plans include it
None of the 819 sheets in the official directory states its plan availability. That answer is published nowhere, connector by connector.
What Anthropic publishes is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like Kapture install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can connect. The connector's sheet in the official directory is the only place showing its current state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when a page changes or a price moves.
Only its publisher, William Kapke, documents this connector; neither the Claude help center nor Anthropic's developer docs has a page on it. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses a publisher's tools nor guarantees how they behave. With a tool that clicks inside your logged-in sessions, connect only what you trust. Kapture is a desktop extension: it works from Claude Desktop, not from Claude on the web.
Need help connecting Kapture Browser Automation to Claude?
A person reads every message.