VKontakte MCP server for Make

MCP VKontakte Server

A 42-tool VKontakte MCP server for the Make MCP Client: posts, stories, photo albums, group moderation and webhooks

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-vkontakte-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport http 'MCP VKontakte Server' https://your-app-name.railway.app/mcp --header 'Authorization: Bearer <your VK_ACCESS_TOKEN>'

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "type": "http",
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"MCP VKontakte Server","type":"http","url":"https://your-app-name.railway.app/mcp","headers":{"Authorization":"Bearer <your VK_ACCESS_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "MCP VKontakte Server": {
      "type": "http",
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.codex/config.toml, for all projects

[mcp_servers."MCP VKontakte Server"]
url = "https://your-app-name.railway.app/mcp"
http_headers = { Authorization = "Bearer <your VK_ACCESS_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "httpUrl": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "serverUrl": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "type": "streamableHttp",
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "MCP VKontakte Server": {
      "type": "streamable-http",
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "MCP VKontakte Server": {
      "type": "remote",
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "MCP VKontakte Server": {
      "url": "https://your-app-name.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <your VK_ACCESS_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

VK_ACCESS_TOKENsecret, required: VK Access Token для авторизации в MCP VKontakte Server

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Checked against the repository on Sep 25, 2026, commit 8402004.

Text for your agent

Deploy the server on Railway from a fork of the repository, get a VK token per the README via vkhost.github.io, and pass it in the Make MCP Client's request headers.

This is third-party code. Review the repository files before installing.

What it does

The server wraps the VK API in 42 tools by group: publishing posts on a personal profile and in groups, handling several of a user's groups, creating stories with photos and video, pinning and unpinning posts, reposting with comments, managing photo albums, searching and managing followers and subscriptions, group moderation with user blocking, basic analytics, and content search. The architecture is stateless: the VK token is passed in request headers rather than stored on the server, transport is HTTP or SSE built specifically for the Make MCP Client, and there are webhook notifications for Make.com automation.

Who it is for. For people automating VK through Make.com scenarios who want broad action coverage: posts, stories, albums and moderation.

Good fit when

You need the broadest possible set of VK actions in one server: posts, stories, albums, moderation
You need integration specifically with the Make MCP Client via HTTP/SSE and webhooks
A stateless architecture with the token in headers instead of server storage works for you

Not a fit when

You need a plain stdio MCP client like Claude Desktop with no adaptation: the server is built for Make and HTTP headers
You are not comfortable getting a token via the third-party service vkhost.github.io, which the README calls a proven method
You need English documentation: the README is entirely in Russian

Example request

Publish a story with this video in my VK group and pin the latest post

Limitations

The README recommends getting a VK token through the third-party service vkhost.github.io and the VK Admin app, which grants broad personal-account permissions rather than a narrower app-specific token. The token is passed in request headers on every call, which suits the Make MCP Client but is less typical for plain stdio MCP clients. The author field in package.json is unfilled (Your Name), and there are few signs of active maintenance.

How to disable. Stop the Railway deployment or the server process and remove it from your Make scenario or MCP client configuration.

MCP

Transport: http, sse
Authentication: API key

Security check

It can publish, pin and repost posts and stories on behalf of a profile or group
It can moderate a community: block and unblock users

README in short

The emoji-heavy Russian README lists 42 tools by group (wall, stories, albums, groups, analytics, users, utility), a way to get a token via vkhost.github.io and the VK Admin app, and a quick-start Railway deploy with a repository fork and Make MCP Client setup.

FAQ

How do I get a VK token for the server?

The README describes a method via vkhost.github.io and the VK Admin app, copying the token from the address bar after granting access.

Does the server store the token?

No, the architecture is stateless: the token is passed in each request's headers rather than stored on the server.

Humanizer

Editors’ pick

A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts

SkillLow riskNo VPN needed52.7K

Marketing Skills for AI agents

Marketing Skills for AI Agents

Editors’ pick

About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents

SkillLow risk51.8K

SendPulse MCP server

SendPulse MCP

Official

SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat

MCP serverHigh riskRussian stack1

Yandex Direct MCP generated from a machine-readable schema

yandex-direct-mcp

Editors’ pick

An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand

MCP serverHigh riskRussian stackNo VPN needed1

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Humanizer

Marketing Skills for AI agents

SendPulse MCP server

Yandex Direct MCP generated from a machine-readable schema