Yandex Browser MCP Server
Server 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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_to_browserC | Подключиться к уже открытому Яндекс Браузеру |
| list_tabsB | Получить список всех открытых вкладок с их индексами и заголовками |
| navigateC | Перейти по URL в указанной вкладке |
| clickC | Кликнуть по элементу в указанной вкладке |
| typeC | Ввести текст в поле в указанной вкладке |
| scrollC | Прокрутить страницу или к элементу |
| get_textB | Получить текстовое содержимое страницы или элемента |
| get_htmlC | Получить HTML содержимое страницы или элемента |
| get_attributesC | Получить атрибуты элемента |
| get_console_logsC | Получить логи консоли браузера |
| hoverC | Навести курсор на элемент |
| key_pressC | Нажать клавишу или комбинацию клавиш |
| fill_formC | Заполнить форму данными |
| wait_for_elementC | Ждать появления элемента |
| get_page_infoC | Получить информацию о странице (URL, заголовок, мета-теги) |
| screenshotC | Сделать скриншот указанной вкладки |
| evaluateC | Выполнить JavaScript код в указанной вкладке |
| execute_testC | Выполнить тест в указанной вкладке: выбрать ответы и отправить |
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 18 tools
Most tools have distinct purposes, such as navigate for URL navigation, click for clicking, and get_html for retrieving HTML. However, some overlap exists between fill_form and type (both involve inputting data) and between get_text and get_html (both retrieve content), which could cause minor confusion for an agent.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as connect_to_browser, list_tabs, and wait_for_element. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 18 tools, the count is slightly high but reasonable for a browser automation server, covering a wide range of interactions like navigation, input, and inspection. It might feel a bit heavy, but each tool appears to serve a specific function in the domain.
The toolset provides comprehensive coverage for browser automation, including core actions like navigation, interaction (click, type), inspection (get_html, get_attributes), and utilities (screenshot, wait_for_element). There are no obvious gaps, supporting full workflows from setup to testing.