Ermöglicht es Claude Code, deinen lokalen Chrome-Browser über eine private Verbindung ohne Third-Party-Relays zu lesen und zu steuern.
Auch bekannt als guchaorui/cctether
- Stars
- 0
- Tools
- 20
- Downloads, 30 Tage
- —
- Neueste Version
- —
- Letzter Commit
- 9. Nov. 2026
- Lizenz
- MIT
Was ist cctether MCP?
Ermöglicht es Claude Code, deinen lokalen Chrome-Browser über eine private Verbindung ohne Third-Party-Relays zu lesen und zu steuern. Er stellt 20 Tools bereit, etwa list_tabs, open_tab, close_tab.
Zusammenfassung generiert aus dem README des Projekts
Über cctether MCP server
cctether ermöglicht es dir, deinen lokalen Chrome-Browser direkt aus Claude Code heraus zu steuern – und zwar über eine private, direkte Verbindung. Dieses Setup wurde für Entwickler entwickelt, die den offiziellen Anthropic-Relay umgehen müssen, besonders wenn sie API-Keys, Amazon Bedrock, Google Cloud oder Microsoft Foundry nutzen. Es löst zudem Verbindungsprobleme für Nutzer, die Claude Code in WSL oder auf Remote-Servern ausführen, während ihr Browser auf einer lokalen Maschine läuft.
Das System funktioniert, indem eine Chrome-Extension mit einem lokalen Service auf deinem Computer verbunden wird. Diese Architektur stellt sicher, dass alle Daten auf deiner eigenen Verbindung bleiben, ohne Third-Party-Relays. Nutzer können Browser-Aufgaben mit zwanzig spezifischen Tools verwalten, darunter navigate, screenshot, click, type und evaluate. Der Setup-Prozess erfordert Node.js 22 oder neuer und beinhaltet das Ausführen eines Setup-Commands, um den Service zu installieren und ihn mittels eines eindeutigen Connection-Codes mit der Extension zu koppeln.
Was du damit machen kannst
- 1Web-Interaktionen automatisierenLass deinen AI-Client Websites navigieren, Buttons klicken und Text in Formulare tippen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du cctether MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügencctether MCP in Claude Code installieren
$ claude mcp add cctether -- npx -y cctethercctether MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"cctether": {
"command": "npx",
"args": [
"-y",
"cctether"
]
}
}
}cctether MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"cctether": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cctether"
]
}
}
}cctether MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"cctether","type":"stdio","command":"npx","args":["-y","cctether"]}'cctether MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"cctether": {
"command": "npx",
"args": [
"-y",
"cctether"
]
}
}
}cctether MCP in Codex installieren
$ codex mcp add cctether -- npx -y cctethercctether MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.cctether] command = "npx" args = ["-y", "cctether"]
cctether MCP in Gemini CLI installieren
$ gemini mcp add -s user cctether npx -- -y cctethercctether MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"cctether": {
"command": "npx",
"args": [
"-y",
"cctether"
]
}
}
}cctether MCP tools 20
Erkannt aus dem READMElist_tabsopen_tabclose_tabnavigateread_pagefindscreenshotclicktypepress_keyscrollhover
| list_tabs | — | |
| open_tab | — | |
| close_tab | — | |
| navigate | — | |
| read_page | — | |
| find | — | |
| screenshot | — | |
| click | — | |
| type | — | |
| press_key | — | |
| scroll | — | |
| hover | — |
Alle 20 Tools anzeigenWeniger Tools anzeigen
select_optionwait_forevaluateconsole_messagesnetwork_requestshandle_dialoglist_extensionsreload_extension
| select_option | — | |
| wait_for | — | |
| evaluate | — | |
| console_messages | — | |
| network_requests | — | |
| handle_dialog | — | |
| list_extensions | — | |
| reload_extension | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarguchaorui/cctether is public and reachablegithub.com/guchaorui/cctether ↗Bestanden
- Paket nennt dieses Repository als Quellecctether names guchaorui/cctether as sourcenpmjs.com/package/cctether ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for cctethernpmjs.com/package/cctether/v/0.3.3#provenance ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-09github.com/guchaorui/cctether ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from cctetherBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell20 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNo tool named like delete, drop or execBestanden
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehencctether
English | 简体中文
Chrome Web Store · npm · Releases
cctether lets Claude Code (or any MCP client) read and drive your own Chrome browser. A Chrome extension connects out to a small server that runs on the computer where Claude Code runs. The server gives Claude browser tools over MCP: read pages, take screenshots, click, type, and look at the console and network requests. Everything goes over your own connection. There is no Anthropic or third-party relay in between.
Why it exists
The official "Claude in Chrome" integration goes through Anthropic's relay (bridge.claudeusercontent.com). That doesn't work if you:
- log in to Claude Code with an API key or
claude setup-token; - use Claude through Amazon Bedrock, Google Cloud or Microsoft Foundry;
- run Claude Code in WSL;
- are on a network that can't reach the relay;
- run Claude Code on a remote server while the browser is on your own computer.
cctether works in all of these, because the browser connects to a service that you run yourself.
How it works
Browser Computer that runs Claude Code
+--------------------+ +--------------------------+ +-------------+
| cctether extension | -----> | cctether service | <----> | Claude Code |
+--------------------+ wss +--------------------------+ MCP +-------------+
(or ws to 127.0.0.1)
- The extension connects out to the service, so the browser computer needs no open port.
- The extension only connects to another computer over
wss://(HTTPS, through a reverse proxy or a tunnel service). Plainws://is only allowed to this same computer (127.0.0.1), which also covers an SSH tunnel. - After a handshake that proves both sides hold the same key, every message is encrypted.
Quick start
You need Node.js 22 or newer on the computer that runs Claude Code.
-
On that computer, open a terminal and run:
npx cctether@latest setupIt asks a few questions and then:
- installs cctether for your user (
npm install -g cctether); - makes a key;
- asks how your browser will reach this computer (see Ways to connect);
- optionally installs a background service (systemd user service on Linux);
- adds cctether to Claude Code (
claude mcp add -s user ...), and if you like, tells Claude to use it by itself for every browser task; - checks that the address works;
- prints a connection code that starts with
cctether1:.
- installs cctether for your user (
-
Install the extension from the Chrome Web Store. More on this below.
-
Open the extension's settings and paste the connection code.
-
Restart Claude Code if it was open, and ask it to use the browser.
Treat the connection code like a password. It contains the key.
Rather have Claude do it? Paste the prompt from docs/setup-with-claude.md into Claude Code. Claude runs setup, and you only paste the connection code into the extension yourself.
Install the extension
- Open cctether on the Chrome Web Store and click Add to Chrome. Chrome lists what the extension may do, including a strong-sounding warning that comes with its debugger permission: see Permissions. After you confirm, the extension's settings page opens by itself. Leave it open.
- Click the puzzle-piece icon in Chrome's toolbar, then the pin next to cctether, so the button stays visible. A plain grey icon means you haven't paired yet.
- On the settings page, paste the connection code from
cctether setup(or fromcctether pair) into the box under "Pair with your server" and click Pair. - The page shows "Connected" and the toolbar icon turns teal. Done.
The store version updates itself.
Notes:
- Edge and other Chromium browsers probably work, but they aren't tested. Firefox and Safari are not supported.
- If a proxy app (Clash and similar) runs on the browser computer, add a direct rule for your server's domain. Otherwise a proxy problem also cuts cctether.
Or load it yourself
If you can't use the store, or want to run exactly the files from a release:
- Download
cctether-extension-<version>.zipfrom the GitHub Releases page (not the one ending in-store). - Unzip it. You get a folder called
cctether-extension. - Put that folder somewhere permanent, such as your Documents folder. Chrome reads the extension from there every time it starts, so don't delete or move it.
- In Chrome, open
chrome://extensions. - Turn on Developer mode (top right).
- Click Load unpacked and pick the
cctether-extensionfolder. A cctether card appears, and the extension's settings page opens. - Pin the button and pair, as in steps 2 to 4 above.
Keep only one of the two installed. They don't share their pairing, and two copies in one browser compete for the same connection (one of them shows "Another browser took over"). To switch, remove the old one on chrome://extensions, install the new one, and pair again: cctether pair shows the same code.
Ways to connect
| Setup | Address the extension uses | setup choice |
|---|---|---|
| Chrome and Claude Code on the same computer | ws://127.0.0.1:27182/cctether |
1 |
| Claude Code on a server, through an SSH tunnel | ws://127.0.0.1:27182/cctether (the tunnel carries it) |
2 |
| Claude Code on a server, over HTTPS with your own domain (Caddy, Cloudflare Tunnel, nginx, ...) | wss://browser.example.com/cctether |
3 |
| Chrome on Windows, Claude Code in WSL | ws://127.0.0.1:27182/cctether |
1 |
Step-by-step instructions for each are in docs/connect.md.
Daily use
- Claude can only use tabs in the cctether tab group. Tabs that Claude opens join the group by themselves.
- To let Claude see a page you already have open, click the cctether button in the toolbar and click Share. Or drag the tab into the cctether group.
- To take a tab back, click Stop sharing, or drag it out of the group.
- While Claude works on a page, Chrome shows a bar: "“cctether” started debugging this browser". That is normal. Chrome requires it and it can't be hidden. If you click Cancel on that bar, cctether pauses.
- You can Pause at any time from the toolbar button. While paused, Claude can't touch any page. Click Resume to continue.
- The popup lists recent activity: what Claude clicked, typed, read or captured.
- If you answered yes to "use cctether by itself" in setup, Claude reaches for cctether whenever a task needs a browser. Otherwise, ask it to ("use the browser to check…"). The setting is a short marked note in
~/.claude/CLAUDE.md; delete it to undo.
The toolbar icon
| Icon | Meaning | What to do |
|---|---|---|
| Teal | Connected | Nothing |
| Grey with a blue dot | Connecting | Wait a few seconds |
| Grey with a red dot | Can't connect | Click the icon to see why. It keeps retrying by itself. Usual causes: the server isn't running, or a network or proxy problem |
| Grey with an orange dot | Another browser took over | The service works with one browser at a time. Click Reconnect here to use this one |
| Pause symbol | Paused | Click the icon, then Resume |
| Plain grey | Not paired yet | Paste a connection code in Settings |
Commands
Run cctether help for the full text.
| Command | What it does |
|---|---|
cctether setup |
Sets everything up, step by step. Start here. Safe to run again. |
cctether init [--port N] [--url URL] |
Creates the key and settings. Done automatically on first use. |
cctether pair [--url URL] |
Shows the connection code to paste into the extension. |
cctether check |
Tests that the extension's address reaches this computer's service. |
cctether status [--json] |
Is the service running? Is a browser connected? |
cctether rotate |
Makes a new key. The old connection code stops working at once. |
cctether daemon [--takeover] |
Runs the service in the foreground. The systemd service runs it with --takeover, so it replaces a copy that Claude Code started. |
cctether stop |
Stops the running service. |
cctether mcp |
MCP server on stdin/stdout. Claude Code runs this. |
cctether version |
Prints the version. |
Options: --url URL is the address the extension should connect to (saved for next time), --port N is the local port (default 27182). For scripts, setup also takes --yes, --mode local|ssh|https, --no-install, --no-service, --no-mcp, --claude-md / --no-claude-md and --lang en|zh.
Settings live in $CCTETHER_HOME, else $XDG_CONFIG_HOME/cctether, else ~/.config/cctether.
Tools
Claude gets these 20 tools:
| Tool | What it does |
|---|---|
list_tabs |
Lists the tabs in the cctether group, plus browser info. |
open_tab |
Opens a new tab in the group and makes it the current tab. |
close_tab |
Closes a tab in the group. |
navigate |
Loads a URL, or goes back, forward or reloads. Waits for the page to load. |
read_page |
Reads the page: visible text, a numbered list of interactive elements, or the HTML of a selector. Long output is split. |
find |
Finds elements by CSS selector. |
screenshot |
Screenshots the visible area, the full page, or one element. |
click |
Clicks an element or a point with real mouse events. |
type |
Types text into an element or the focused element. |
press_key |
Presses a key or combination, such as Enter or Control+A (Meta+A when the browser is on a Mac). |
scroll |
Scrolls the page, or scrolls an element into view. |
hover |
Moves the mouse over an element or a point. |
select_option |
Chooses options in a <select>. |
wait_for |
Waits until text or an element appears (or disappears). |
evaluate |
Runs JavaScript in the page and returns the result as JSON. |
console_messages |
Reads console messages and uncaught errors. |
network_requests |
Lists network requests, or shows headers and body of one. |
handle_dialog |
Accepts or dismisses an alert, confirm or prompt. |
list_extensions |
Lists installed browser extensions. |
reload_extension |
Reloads an extension (useful when developing one). |
Permissions
The extension asks for these Chrome permissions, and nothing else:
| Permission | Why |
|---|---|
debugger |
All page work: real mouse and keyboard input, screenshots, console, network, JavaScript dialogs, running scripts in the page. This is also why Chrome shows its debugging bar. |
tabs |
Read tab titles and addresses; open and close tabs. |
tabGroups |
Create the cctether tab group and tell which tabs are in it. |
storage |
Keep the connection code, your settings and the recent-activity list. |
alarms |
Check the connection on a timer and reconnect by itself. |
management |
List and reload extensions (list_extensions, reload_extension). |
When you install it, Chrome warns that the extension can "Read and change all your data on all websites" and "Access the page debugger backend". Chrome shows this for any extension with the debugger permission, because that permission really is that powerful. The limit is in cctether's own code: every tool that works on a page first checks that the tab is in the cctether tab group (extension/background/tabs.js). The code isn't minified, so you can read it. The extension asks for no separate website (host) permissions and has no content scripts: the code that reads pages ships inside the extension and only runs when a tool is called.
Security and privacy
- Both sides prove they hold the same 256-bit key (a challenge-response handshake). The extension accepts no commands until the server has proved it has the key.
- After the handshake, every message is encrypted with AES-256-GCM. A proxy that can read HTTPS traffic still can't read or inject commands.
- To another computer, the extension only connects over
wss://. Plainws://is only allowed to this computer. - Claude can only use tabs in the cctether tab group. You can pause at any time.
- The service accepts only this extension, rate-limits failed attempts, and serves only the path
/cctether. - No analytics, no telemetry. Nothing is sent anywhere except to your own service.
- The connection code is a secret. If it leaks, run
cctether rotateon the server, then pair again.
Web pages can contain hidden instructions meant for an AI (prompt injection), and Claude acts in your logged-in browser. Keep sensitive tabs (banking, email, admin panels) out of the cctether group, and look at what Claude is doing in the popup.
More: SECURITY.md, PRIVACY.md and docs/PROTOCOL.md.
Updating
The extension from the Chrome Web Store updates itself. New versions reach the store after its review, so it can be a little behind the service. That's fine: if the two can't work together, the popup says which side to update.
The service you update yourself, on the Claude Code computer:
npm install -g cctether@latest- Restart it. With the background service:
systemctl --user restart cctether. Without it:cctether stop. It starts again by itself when Claude Code needs it.
If you loaded the extension yourself: download the new zip, replace the contents of your cctether-extension folder with the new files, then click the reload button on the cctether card at chrome://extensions.
Your pairing is kept either way.
Troubleshooting
- On the Claude Code computer, run
cctether check. It connects to the address in your connection code the way the extension does, and says in plain words what's wrong. Runcctether statusto see whether the service runs and a browser is connected. - "Can't reach the server": the service isn't running, or the network blocks it. Check
cctether status. A proxy app on the browser computer may need a direct rule for your domain. - "This server couldn't prove it's yours", or "The server no longer accepts this browser": the key changed (for example after
cctether rotate). Runcctether pairand pair again with the new code. - "Another browser took over": the service works with one browser at a time. Click Reconnect here to switch back.
- "Please update the extension" or "Please update cctether on your server": see Updating.
- More about each connection setup: docs/connect.md.
Does it cost much?
- Claude's context: the 20 tool descriptions take about 4,000 tokens, around 2% of a 200k context. Recent Claude Code versions load MCP tools on demand when there are many of them, so until Claude actually uses the browser, only the tool names (about 150 tokens) and a short note (about 120 tokens) sit in the context.
- Memory on the Claude Code computer: the service uses about 75 MB, and each open Claude Code window adds a small relay process of about 55 MB.
- The browser: the extension does nothing while Claude isn't using it, apart from a tiny heartbeat every 10 seconds.
Known limitations
- Elements, console messages and network requests inside cross-origin iframes aren't available.
- CSS selectors don't reach into shadow DOM. The interactive list from
read_pagedoes see inside. reload_extensionapplies code changes, but notmanifest.jsonchanges. For those, click reload onchrome://extensionsyourself.- Very long full-page screenshots are scaled down (to stay under the image size limit), so they come out narrow.
- One browser per service at a time.
- The service doesn't run on Windows directly. Use WSL.
Not tested yet
- macOS as the computer that runs Claude Code.
- WSL (Chrome on Windows, Claude Code in WSL).
Both should work, but nobody has tried them yet. Feedback is welcome: open an issue.
Uninstall
claude mcp remove -s user cctether, and if setup added it, the cctether note in~/.claude/CLAUDE.md- If you installed the background service:
systemctl --user disable --now cctether, then delete~/.config/systemd/user/cctether.service. npm uninstall -g cctether- Delete the config folder:
~/.config/cctether(or$CCTETHER_HOMEif you set it). - In Chrome, remove the extension on
chrome://extensions. If you loaded it yourself, also delete thecctether-extensionfolder.
Development
extension/ the browser extension (MV3, no dependencies, no build step)
server/ the npm package "cctether": CLI, service, MCP
test/e2e/ end-to-end tests: headless Chrome for Testing + extension + service
docs/ design (SPEC), connection guides
deploy/ example Caddyfile and systemd unit
scripts/ icons, screenshots, extension packaging, store images
store/ Chrome Web Store listing text and images
- Server unit tests:
cd server && npm test - End-to-end tests:
node --test test/e2e/*.test.mjs(needs Chrome for Testing, or setCHROME_PATH) - Build the extension zip:
node scripts/pack-extension.mjs(reproducible: the same source gives the same zip, so you can check a release yourself)
License
cctether MCP Fragen
Wie füge ich cctether MCP zu Claude Code hinzu?
Führe claude mcp add cctether -- npx -y cctether in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich cctether MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet cctether MCP?
Er stellt 20 Tools bereit, darunter list_tabs, open_tab, close_tab, navigate, read_page.
Nutzt cctether ein Third-Party-Relay?
Nein, alles läuft über deine eigene Verbindung, ohne dass Anthropic oder ein Third-Party-Relay dazwischengeschaltet ist.
Kann ich cctether mit Claude Code in WSL nutzen?
Ja, cctether funktioniert in WSL, indem es sich mit dem Service verbindet, der auf deiner lokalen Maschine läuft.
Welche Browser-Funktionen kann Claude steuern?
Claude kann Aktionen wie Klicken, Tippen, Scrollen, Screenshots erstellen, Seiteninhalte lesen und Network Requests inspizieren.
Ist die Verbindung sicher?
Ja, nach einem Handshake, der verifiziert, dass beide Seiten denselben Key besitzen, wird jede Nachricht verschlüsselt.