
Vk Ads Mcp
io.github.ai-hub-openPublished by GitHub account ai-hub-openv0.8.0Updated Oct 24, 2026
MCP server for VK Ads API: campaigns, audiences, budgets, stats. Click.ru, token or OAuth.
Overview
Lets an assistant work with VK Ads advertising data — campaigns, audiences, budgets and statistics — through the VK Ads API.
- What you can do
- This local MCP server exposes the VK Ads API to an assistant, covering campaigns, audiences, budgets and statistics. It supports two access paths: a primary mode through Click.ru, and an alternative mode using a static VK Ads token or OAuth credentials. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when an assistant needs to read or manage VK Ads advertising data — reviewing campaigns, audiences, budgets or performance statistics — from a desktop MCP client. It is not useful if you do not run VK Ads or Click.ru accounts.
- Requirements
- Runs locally over stdio, started with bunx from the npm package @ai-hub-open/vk-ads-mcp, so a JavaScript runtime and network access are needed. Desktop only. Credentials are supplied by environment variable: CLICK_RU_ACCOUNT_ID and CLICK_RU_TOKEN for the Click.ru mode, or VK_ADS_ACCESS_TOKEN, or VK_ADS_CLIENT_ID with VK_ADS_CLIENT_SECRET for OAuth.
Installation
In SourceWeft
- Open Vk Ads Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.8.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.