Asklear Browser MCP
A local stdio MCP server that drives your Chrome browser through the Asklear extension, offering six browser tools for navigation, observation, clicking, filling, scrolling, and extraction — all operations remain on your machine.
README
Asklear Browser MCP
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.
What you get
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 |
Install
uv tool install git+https://github.com/Asklear/asklear-browser-mcp.git
Or, if you prefer pip:
pip install git+https://github.com/Asklear/asklear-browser-mcp.git
Configure
Add this to your MCP client configuration:
{
"mcpServers": {
"asklear-local": {
"command": "asklear-browser-mcp",
"args": []
}
}
}
Prerequisites
- Google Chrome installed
- Asklear Chrome extension installed and bound to your account
- Verify:
curl http://127.0.0.1:8765/health→{"extension_connected": true}
How it works
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.
Two connections, one Asklear
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.
License
Apache-2.0. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.