Vibiz Claude Plugin MCP Server

Generate ads, funnels, ICPs, social posts, and full Meta campaigns from inside Claude Code. Drafts a marketing post about every commit you make. The vibiz claude plugin mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• Generation — images, carousels, videos, UGC, funnels, ICPs, offers
• Social — list accounts, list posts, publish/schedule across IG / FB / TikTok / X / LinkedIn / Threads
• Inbox — list DMs, list commented posts, reply to comments, send DMs
• Analytics — top posts, daily metrics, best posting times

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vibiz Claude Plugin's toolset — Generation, Social, Inbox and 1 more — is a fair guide to whether it matches your workflow. It is maintained by vibiz-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vibiz Claude Plugin's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vibiz claude plugin mcp server does with a few real requests.