Local browser collection gateway for Asklear — a stdio MCP server that drives your Chrome browser via the Asklear extension.
Page content and login state never leave your computer. All browser operations run locally; the Asklear service never sees your cookies, credentials, or page data.
Six browser tools, usable from any MCP-compatible agent (Claude Code, Codex, WorkBuddy, Trae, …):
| Tool | Purpose |
|---|---|
navigate |
Open a URL in a background tab |
observe |
Snapshot the current page's accessibility tree |
click |
Click an element |
fill |
Type into an input |
scroll |
Scroll the page |
extract |
Extract structured text/markdown from the page |
uv tool install git+https://github.com/Asklear/asklear-browser-mcp.gitOr, if you prefer pip:
pip install git+https://github.com/Asklear/asklear-browser-mcp.gitAdd this to your MCP client configuration:
{
"mcpServers": {
"asklear-local": {
"command": "asklear-browser-mcp",
"args": []
}
}
}- Google Chrome installed
- Asklear Chrome extension installed and bound to your account
- Verify:
curl http://127.0.0.1:8765/health→{"extension_connected": true}
Agent (Claude Code / Codex / …)
│ stdio JSON-RPC
▼
asklear-browser-mcp (this package)
│ loopback HTTP (127.0.0.1:8765)
▼
asklear-browser-connector (auto-started)
│ WebSocket
▼
Asklear Chrome extension → your Chrome tab
The local Connector is bundled in this distribution and auto-started on first use. A second Agent reuses the Connector already listening on loopback; its session is isolated by session_id. No separate Connector installation or manual process management is needed.
This package provides browser collection only. For data queries (JD/Tmall/PDD/Douyin market data), use the hosted Asklear MCP:
| Connection | Purpose | Transport |
|---|---|---|
asklear |
Data queries, market research | Remote HTTP (OAuth) |
asklear-local (this package) |
Browser collection, page extraction | Local stdio |
Both can coexist. Your agent picks the right tool automatically.
Apache-2.0. See LICENSE.