Vk MCP Server

What bulatko/vk-mcp-server MCP server does

The bulatko/vk-mcp-server MCP server connects an MCP-compatible client to VKontakte’s API. It provides 19 tools covering user lookup and search, wall reading and publishing, comments, post editing and deletion, community discovery and membership, friend lists, the token owner’s newsfeed, photo uploads and album browsing, likes, and community statistics.

The read tools can resolve users or communities by numeric ID or short name, inspect profile or community details, search by filters, and retrieve paginated results. Wall responses include engagement counters such as likes, reposts, comments, and views. Write operations include publishing posts, adding comments, editing posts, deleting posts, and uploading photos for later attachment.

How it works

The server translates MCP tool calls into VK API requests and returns structured, typed results. List operations report match counts and continuation offsets, allowing a client to request additional pages instead of treating the first response as complete. Prompts are also included for workflows such as community digests, engagement reports, audience snapshots, and community searches.

VK access depends on the token type and the account or community behind it. User tokens are needed for a user’s communities, friends, and personal newsfeed. Community statistics require the token owner to administer the target community. Posting, editing, and photo uploads require a community token with the relevant permissions. Public profile, wall, and community reads can use a service token or a token obtained through the VK ID login flow, but that login token does not provide the broader operations.

Hosts that support MCP Apps can render walls, communities, and profiles as cards. Other MCP clients still receive the same structured tool data without those visual renderings.

Setup and configuration

Install and run the package with npx -y vk-mcp-server. MCP client configuration supplies the access token through VK_ACCESS_TOKEN. The server can start and expose its tools without a token, but tool calls require one. The repository documents configurations for Claude Desktop and Claude Code, and also provides a one-click installation path for VS Code.

VK_TIMEOUT_MS controls the request timeout and defaults to 30,000 milliseconds. VK_API_BASE can replace the default VK API endpoint with a mirror or proxy. The --check option identifies the token type and tests which operations it can reach without invoking write methods. The --login <APP_ID> option starts the VK ID sign-in flow for a reading token.

Tools and capabilities

• Resolve users and communities by ID or short name.
• Search users and communities with filters and pagination.
• Read, publish, edit, comment on, and delete wall posts.
• Upload photos for wall attachments and list album photos.
• List community members, joined communities, friends, and the token owner’s newsfeed.
• Read reactions and community reach, visitor, and activity statistics.

Limitations and notes

VK’s permissions are not uniform across token types. A service token cannot call user methods, private profiles may deny access, and communities can hide their member lists. Friend retrieval only works when the target profile exposes its friends. Statistics are restricted to community administrators.

User tokens are rate-limited to a few requests per second. The server retries rate-limit responses with backoff up to three times, and it reports timeout, captcha, HTTP, and VK API errors with explanatory messages. Deleting a wall post is irreversible, while editing replaces the existing text or attachments rather than appending to them.

The bulatko/vk-mcp-server MCP server is therefore best suited to VK workflows where the required token permissions are known in advance. Use numeric negative owner IDs for community walls, positive IDs for personal walls, and positive group IDs when uploading community photos.