SkillFoxx

MCP publishing connectors without manual OAuth

Personal Content Connectors

An MCP server posts to YouTube, Instagram, VK and Dzen through self-hosted Nango: account connection in a couple of clicks, no developer console

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Publishes content on behalf of the owner of connected VK, YouTube and Instagram accounts
  • Stores OAuth tokens in self-hosted Nango on the user's machine
All reasons and checks
Russian stack

fireguardspb/agent-content-connectorsAuthor:FIREguardSPB

Meta, the owner of Facebook, Instagram and WhatsApp, is designated an extremist organization in Russia and its activities are banned there.

Install

Services

Manual install

cd nango && ./setup.sh && docker compose up -d

Brings up self-hosted Nango, generating secrets in nango/.env on first run.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Publishes content on behalf of the owner of connected VK, YouTube and Instagram accounts
  • Stores OAuth tokens in self-hosted Nango on the user's machine

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

What it does

The project solves the manual OAuth token problem for social posting: self-hosted Nango runs in Docker and stores and refreshes tokens itself, while a person connects an account through Nango's ordinary Connect UI login screen instead of a developer console. A thin MCP server exposes tools like youtube_upload, instagram_post and vk_post that call Nango Proxy and never see the tokens themselves. For platforms without OAuth, such as Dzen, separate browser-automation adapters run outside the Nango loop. Before any write action, the agent must show a preview and wait for confirm=true through a built-in confirmation guard. A separate self-extend mechanism lets the agent generate a missing tool from a template, but a new tool goes through a sandbox and human review before activation.

Who it is for. For people who want to publish to several social networks through an agent without setting up a developer app on each platform themselves, or for a non-technical friend.

Good fit when

  • You need to connect a VK, YouTube or Instagram account for an agent without a developer console
  • You need protection against accidental posting: a preview and confirmation before every write
  • You need a tool for a platform that does not exist yet, generated with review before activation

Not a fit when

  • You do not want to stand up a Docker Compose Nango stack just to post to a few networks
  • You need Dzen publishing without browser automation, the platform has no official API

Example request

Publish this video to VK and Instagram, show a preview first and wait for my confirmation

MCP

Transport
stdio
Authentication
OAuth

Environment variables

NANGO_SECRET_KEY required, secret
The self-hosted Nango secret key from its dashboard, for the MCP server's access to Nango Proxy.

Limitations

It needs self-hosted Nango in Docker, meaning your own server or machine to keep it running. The repository license is marked NOASSERTION, meaning it is not explicitly stated. The Dzen adapter runs via browser automation outside the Nango loop, which is more fragile to platform changes. The project is small, with no packaged releases.

How to disable. Run docker compose down in the nango folder and remove the broker-connectors server from your MCP client configuration.

FAQ

Does the MCP server see social media tokens?

No, per the README's architecture the server only calls Nango Proxy through tools like vk_post, and the tokens live solely in Nango.

Can the agent publish a post without human confirmation?

No, the confirmation guard requires a preview and an explicit confirm=true before any write action.

Discussion

No questions or reviews yet.

All VK tools
Russian stack

Remote MCP server for VK communities: 50 tools, posts, comments, dialogs, photos, video and products, with writing off by default

MCP serverBroad access
Russian stack

An MCP server for the VKontakte wall: reading and posting, messages, friends, communities and group stats in 8 tools

MCP serverBroad access1
Russian stack

MCP for VK on your own server: a VK API method catalog, reading walls and communities, community comparison and writes only after a human approves

MCP serverBroad access
Russian stack

MCP server for the VK API: profiles, walls, communities, photos, likes and stats, with confirmable post publishing

MCP serverBroad access17
Russian stack

An MCP server publishes one text at once to Telegram, VKontakte (group and personal wall) and TenChat with a single publish_all call

MCP serverBroad access

README in short

The Russian README describes the architecture with a diagram: a person connects an account via Connect UI, Nango stores and refreshes tokens, the MCP server calls Nango Proxy and never sees tokens, and adapters outside the Nango loop cover OAuth-less platforms like Dzen. It separately covers the confirmation guard with a preview before writes and the self-extend mechanism with a sandbox and review for new tools. A dedicated AGENTS.md file gives an operational playbook for AI-assistant-driven setup, including for a non-technical user.

README badge

Report a problem