Quickstart

There are two ways to authenticate: a one-click OAuth flow, which is recommended, or a manual API key.

1. Add Vibiz to your client

Point your MCP client at the Vibiz server URL. That is all the information any client needs.

https://mcp.vibiz.ai/mcp

• In Claude, use Settings → Connectors → Add custom connector.
• In Cursor, add it under Settings → MCP.
• In Claude Code, run npx @vibiz/vibiz. It installs the official plugin, with slash commands, a subagent and a post-commit nudge, and the MCP connection in one step. See the Claude Code page.

2. Sign in to Vibiz

Your client opens a browser tab to vibiz.ai. Sign in with the same account you use for the app. Approve the connection and the browser hands the session back to your client.

3. Verify the connection

The Vibiz tools should now appear in your client's tool picker. Try a prompt like "generate an ad image for our hero product" to confirm.

Manual: API key

Prefer a static credential? Mint a token from your workspace's Developer page: sign in to vibiz.ai, then open Developer → API keys, and add it as a Bearer header. Use this for headless agents, CI, or clients that do not support OAuth.

{
  "mcpServers": {
    "vibiz": {
      "url": "https://mcp.vibiz.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_VIBIZ_API_KEY"
      }
    }
  }
}

Test it directly with curl:

curl https://mcp.vibiz.ai/mcp \
  -H "Authorization: Bearer YOUR_VIBIZ_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Toolsets

A new connection loads the core toolset: ad creatives, the growth report, brand setup, billing and the main reads. Add more by appending ?toolsets= to the server URL, or with the X-Vibiz-Toolsets header in clients that support headers:

https://mcp.vibiz.ai/mcp?toolsets=ads,social
https://mcp.vibiz.ai/mcp?toolsets=all

Toolsets: core, ads, creatives, social, comms, crm, research, workspace, autonomy, sites. core already launches or boosts ads, adds ads to an existing ad set and sets its budget; the other tools that spend on ads (turning ads back on, new ad sets, bulk launches, campaign copies) are in ads. Every one of them asks for your approval before it spends. Add readonly=1 for a connector that can only read. Not sure which one you need? Ask the assistant: the vibiz_find_capability tool finds any tool and names the toolset that enables it.

Approvals

Anything that spends on ads, publishes, sends, pauses or deletes needs your OK first. Claude and ChatGPT ask you in their own permission prompt. Other clients show an approval card or, when they cannot show one, give you a link: open it in Vibiz, check the budget, the Vibiz fee and what reaches the ad platform, and click Approve. The assistant then retries and the action runs once, exactly as you approved it. Links expire after 30 minutes.

To let agents act without asking up to a limit, open MCP → API keys in Vibiz and set the auto-approve limit: a maximum daily budget in USD (Vibiz fee included) for Meta launches and budget changes, and whether pausing ads needs your OK. Posts, messages, emails and deletes always ask. Only a workspace owner or admin can change it.

Next steps