VibeVO

io.vibevoPublished by vibevo.iov0.7.0Updated Oct 24, 2026

Use VibeVO API tools for campaigns, placements, analytics, creators, wallets, and factories.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant call the VibeVO API for campaigns, placements, analytics, creators, wallets, and factories.

What you can do
This local MCP server exposes VibeVO API operations as assistant tools, covering campaigns, placements, analytics, creators, wallets, and factories. It runs as a local process over stdio and can perform anonymous public creator catalog and page reads without credentials. Other tools require a VibeVO Public API key, and authenticated placement participant requests can optionally target a specific account.
When to use it
Worth adding when you work with VibeVO and want an assistant to look up or act on campaigns, placements, analytics, creators, wallets, or factories through the API. Anonymous public creator catalog and page reads work without a key, so it can also be used for read-only browsing of public data.
Requirements
Runs locally over stdio, installed from the npm package @vibevo/mcp, so Node.js is needed. Desktop only. Set VIBEVO_API_KEY (a VibeVO Public API key) for tools beyond anonymous public reads. Optional: VIBEVO_API_BASE_URL (defaults to the VibeVO API) and VIBEVO_ACTIVE_ACCOUNT_ID for authenticated placement participant requests, including private deliverable downloads. Network access to the VibeVO API is required.
Before you install
The server handles an API key, VIBEVO_API_KEY, which grants access to non-anonymous tools; keep it out of shared logs and configuration. VIBEVO_ACTIVE_ACCOUNT_ID selects which account authenticated placement participant requests act on, including private deliverable downloads, so confirm the intended account before use. The tool list is not published in the manifest, so review which operations write, send, or change data before granting access.

Installation

In SourceWeft

  1. Open VibeVO in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.7.0LatestOct 9, 2026
  2. v0.1.2Sep 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.