Big News: Socket Selected for OpenAI's Cybersecurity Grant Program.Details
Socket
Book a DemoSign in
Socket

@avavilov/yandex-browser-control

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@avavilov/yandex-browser-control

Control Yandex browser tabs, windows, and navigation

latest
Source
npmnpm
Version
0.0.1
Version published
Maintainers
1
Created
Source

Yandex Browser Control

An MCP server for controlling Yandex Browser. You can connect it to Claude Desktop (or any MCP-capable host) to manage tabs, windows, and navigation.

Installation

To use as an npm package:

npm install @avavilov/yandex-browser-control

Or use as a Claude Desktop MCP server:

  • If distributed via the Claude Desktop Extensions catalog: open Claude Desktop → Extensions and install "Yandex Browser Control" (when available).
  • For local development today: add it as a custom MCP server in Claude Desktop.
    • Build or run from source (see Development below).
    • In Claude Desktop, go to Settings → Extensions → Model Context Protocol → Add server (Command), and point it to either:
      • Dev: run command npm run dev in this repository directory
      • Prod: run command node dist/index.js in this repository directory

Usage

Once connected, you can control Yandex Browser directly through Claude Desktop.

Logging

  • All logs are emitted to stderr only (never stdout) to comply with MCP over stdio.
  • In addition, logs are duplicated to a temp file. The absolute path to this file is printed to stderr on startup, for example:
logging to file: /var/folders/…/yandex-browser-control.log.12345

You can control verbosity with the LOG_LEVEL env variable (default: info).

Contributing

See contributing.md for development, build, and code quality instructions.

Project Structure

  • src/ — TypeScript source code for the server.
  • dist/ — Compiled JavaScript output (generated on build).
  • src/tools/ — MCP tools, one directory per tool with an index.ts that exports metadata, input schema (when needed), handler, and types.

Tools

  • Each tool lives in src/tools/<tool-name>/index.ts and should export:
    • name and description strings
    • inputSchema (Zod raw shape) when the tool takes parameters; omit inputSchema entirely for no-arg tools
    • handler function returning { content: [{ type: 'text', text: string }] } or structured content
    • any types (e.g., Input, Output)
  • Register all tools in src/tools/index.ts via registerTools(server), which is invoked from src/index.ts.

License

MIT

Keywords

yandex

FAQs

Package last updated on 25 Aug 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts