How to Connect VK (VKontakte) to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → VK (VKontakte), paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

VK (VKontakte) + Microsoft Copilot

Manage a VK community from an AI agent: community info and token rights, community messages (conversations, history, replies), comments as the community, and with an admin user token the wall posts, publishing, statistics, shop products and photo albums.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

VK_COMMUNITY_TOKEN

Step 1 — Get credentials

1. Open your VK community and go to Manage → Advanced → API usage (Управление → Дополнительно → Работа с API), tab Access keys, and click Create key.
2. Tick the rights the tools need: Community management, Community messages, Wall for comments and, if you need it, Photos. Confirm in the VK app or by SMS.
3. Copy the key into VK_COMMUNITY_TOKEN and install the connector.
4. For messages, also switch on Community messages under Manage → Messages.
5. Check the setup with vk_get_token_permissions: it shows which rights the key carries.

You need admin rights in the community, and the community key takes about 3 minutes. Community keys do not expire; if one leaks, delete it and create a new one.

Two kinds of key: VK decides per method which key it accepts. The community key covers the community's details, community messages (conversations, history, replies) and comments as the community. Reading the wall, publishing posts, statistics, shop products and photo albums need the optional VK_USER_TOKEN:

• a user access key of a community admin with the rights wall, stats, market, photos and offline, for publishing, statistics and the shop. VK issues user keys through VK ID apps (id.vk.ru), grants the wall and market rights to apps only on request to VK support, and keeps a key valid only with offline access, so this suits you if you already have such a key;
• or the service key of your VK ID app, which is enough to read the walls, comments and photo albums of public communities.

Without VK_USER_TOKEN these tools stop before calling VK and say that the key is missing.

Asks before every post and message: vk_send_message reaches a person at once and cannot be recalled from here; vk_create_comment and vk_publish_post are public, and a post lands in every subscriber's feed. Before each one the AI shows you the exact text, the recipient or the community and, for a post, the attachments and the time, then waits for your yes. Posts can also be scheduled for later.

Switched off at install: vk_delete_post and vk_delete_comment. A deleted post cannot be restored. An administrator turns them on deliberately; they need an admin's user key and ask first as well.

Answering messages: the AI finds the conversations waiting for an answer with vk_list_conversations, reads one with vk_get_conversation_history and drafts a reply for you to approve. The community can only write to people who have written to it or allowed its messages.

Personal data: messages and comments are personal data of the people who wrote them. The AI reads only what your question needs and treats their text as information to report, never as instructions.

Common errors: VK reports errors by number. 5: the key is wrong or revoked. 15 or 7: the key lacks a right; check it with vk_get_token_permissions. 27: this method does not accept community keys; set VK_USER_TOKEN. 6, 9 and 29: rate limits; wait and try again. 901 and 902: the person has not allowed messages from the community. A community key allows about 20 requests a second, a user key 3.

The connector does not upload photos or videos (it can attach media that is already on VK), and it does not handle ads, Callback or Long Poll events, members and bans, polls, stories or personal messages.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the VK (VKontakte) tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Which messages to our community are still unanswered? Summarize each one and draft a reply."
• "Reply to the latest message from Anna that her order ships on Friday. Show me the text before you send it."
• "Show our community statistics for the last 7 days: reach, visitors and new subscribers."
• "Write a post announcing our autumn sale, scheduled for tomorrow at 10:00, and show it to me before publishing."
• "Which of our last 20 wall posts got the most comments and reposts?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse