Asklear Browser MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateC | Run the local Chrome browser navigate operation. Page results stay local to the Agent. |
| observeC | Run the local Chrome browser observe operation. Page results stay local to the Agent. |
| clickC | Run the local Chrome browser click operation. Page results stay local to the Agent. |
| fillD | Run the local Chrome browser fill operation. Page results stay local to the Agent. |
| scrollB | Run the local Chrome browser scroll operation. Page results stay local to the Agent. |
| extractC | Run the local Chrome browser extract operation. Page results stay local to the Agent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool name maps to a distinct browser action: navigate, click, fill, scroll, observe, and extract are mostly unambiguous. There is minor potential overlap between observe and extract since both involve reading page state, but their names and typical usage in browser automation are distinguishable.
All six tools follow the exact same single-word lowercase verb pattern. This is fully consistent and easy to predict.
Six tools is a well-scoped size for a browser automation server. Each tool covers a core interaction or observation action without unnecessary bloat.
The toolset covers the main browser workflow: navigate, observe/extract, click, fill, and scroll. Minor gaps such as explicit wait, back/forward navigation, reload, hover, or select operations are missing, but agents can work around most of these for common tasks.