mcpField

About VibeVO

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"io-vibevo-vibevo": {
"command": "npx",
"args": [
"-y",
"@vibevo/mcp"
],
"env": {
"VIBEVO_API_KEY": "<VIBEVO_API_KEY>",
"VIBEVO_API_BASE_URL": "<VIBEVO_API_BASE_URL>",
"VIBEVO_ACTIVE_ACCOUNT_ID": "<VIBEVO_ACTIVE_ACCOUNT_ID>"
}
}
}
}
Run commandnpx -y @vibevo/mcp
Environment variables to set
VIBEVO_API_KEYSecretVibeVO Public API key (vibevo_live_...). Optional for anonymous public creator catalog/page reads; required for other tools.
VIBEVO_API_BASE_URLBase URL of the VibeVO API. Optional; defaults to https://api.vibevo.io.
VIBEVO_ACTIVE_ACCOUNT_IDOptional positive account ID for authenticated placement participant requests, including private deliverable downloads. Omit to use the API-key owner's account; it is not sent to anonymous reads, creator profile/channel operations, or signed upload PUTs.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@vibevo/mcp0.7.0

Tools

100

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.