VK chat-reading plugin via the browser
vk-api-mcp
A Claude Code plugin: a browser extension captures the VK web messenger token and exposes read-only chat access via MCP
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- It reads the user's personal messages via a web-session token rather than the official API
- Using the web messenger's internal token may conflict with VK's terms of service
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/vk-api-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add thisloginalsotaken/vk-mcp
/plugin install vk-chats@vk-mcpIn Claude Code, run /plugin marketplace add thisloginalsotaken/vk-mcp and /plugin install vk-chats, then install the extension from the extension/ folder in your browser and open the messages section on vk.ru so the bridge can capture the token.
Other ways from the author
/plugin marketplace add thisloginalsotaken/vk-mcp
/plugin install vk-chatsInstalling the plugin and MCP bridge; the browser extension is installed separately by hand.
This is third-party code. Review the repository files before installing.
What it does
The plugin gives read-only access to VK conversations without a separate login: a Chrome extension captures the access token the VK web messenger already uses for its own requests, calls the VK API from that same browser session, and hands the result to a local bridge that talks to Claude Code over MCP via stdio. Pairing happens automatically on the extension's first connection, with no manual code entry. The vk-chats skill installs as a Claude Code plugin, while the browser extension is installed manually as a signed .crx or an unpacked developer-mode extension.
Who it is for. For people who want an agent to read their own VK personal messages with no password and no official API app, accepting the risks that come with it.
Good fit when
- You only need an agent to view VK conversations, not send messages
- A Chrome extension plus local bridge setup instead of the official VK API works for you
- You already use Claude Code with plugins and are willing to install a browser extension manually
Not a fit when
- You need to send messages or take any action in VK: access is strictly read-only
- You do not want to install a browser extension with access to the VK messenger token
- You need to work through the official VK API with your own app, not by capturing the web client's token
Example request
Find the latest message from a colleague about this week's meeting in my VK conversationsLimitations
The tool uses the token the VK web messenger applies to its own requests, not an official API app token, so its use may conflict with VK's terms and could stop working if the web client changes. The browser extension installs manually and does not go through the Chrome extension store; for Edge a separate path is described via a signed .crx, registry and policy. Access is strictly read-only: sending messages and other actions are not supported.
How to disable. Remove the plugin with claude plugin uninstall vk-chats in Claude Code and remove the extension from your browser.
Security check
- It reads the user's personal messages via a web-session token rather than the official API
- Using the web messenger's internal token may conflict with VK's terms of service
README in short
The English README describes the architecture: Claude Code talks to a local bridge, bridge.mjs, over stdio, which talks to the browser extension over WebSocket, and the extension calls api.vk.com in its own session. The repository doubles as a Claude Code plugin marketplace, gives step-by-step plugin and separate extension installation, including a proper Edge path with a signed .crx, and explains automatic bridge-extension pairing with no manual code entry.
FAQ
Can the plugin send messages?
No, the README explicitly describes it as read-only access to conversations.
Do I need a separate login or API key?
No, the extension captures the token from the VK web messenger session already open in the browser.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills