Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Vibe.co MCP Server list my advertisers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for the Vibe CTV/streaming advertising platform.
This server allows AI assistants (like Claude) to interact with your Vibe advertising data securely via the Vibe Streaming API.
Node.js v22 or higher
A Vibe account with API access
A Vibe API key (see Step 1)
Log in to your Vibe account
Navigate to Developer Tool > API Keys
Create or copy your API key
Choose the setup that matches your MCP client:
Add to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"vibe": {
"command": "npx",
"args": ["-y", "vibeco-mcp"],
"env": {
"VIBE_API_KEY": "your-api-key"
}
}
}
}Add to your Claude Code MCP settings (~/.claude/mcp.json or project-level):
{
"mcpServers": {
"vibe": {
"command": "npx",
"args": ["-y", "vibeco-mcp"],
"env": {
"VIBE_API_KEY": "your-api-key"
}
}
}
}In Cursor settings, add an MCP server:
{
"mcpServers": {
"vibe": {
"command": "npx",
"args": ["-y", "vibeco-mcp"],
"env": {
"VIBE_API_KEY": "your-api-key"
}
}
}
}Related MCP server: AdButler MCP Server
Variable | Required | Default | Description |
| Yes | - | Vibe API key |
| No |
| API base URL (override for testing) |
| No |
| Transport mode: |
| No |
| Host to bind the HTTP server to |
| No |
| Port for the HTTP server |
The server provides 8 tools for full Vibe API coverage:
Tool | Description |
| Check server status and API key configuration |
Tool | Description |
| List all advertiser IDs |
Tool | Description |
| List app IDs for an advertiser |
Tool | Description |
| List campaign details for an advertiser |
Tool | Description |
| Create an async report (rate limited: 15/hr) |
| Check report status and get download URL |
Tool | Description |
| List purchase IDs for an advertiser |
The server exposes data as MCP resources:
Resource URI | Description |
| List all advertiser IDs |
Resource URI | Description |
| App IDs for a specific advertiser |
| Campaign details for a specific advertiser |
The server provides guided prompts for common workflows:
Prompt | Description |
| Guided workflow for creating a campaign performance report |
| Instructions for configuring the Vibe API key |
# Clone the repo
git clone https://github.com/jacob-hartmann/vibeco-mcp.git
cd vibeco-mcp
# Use the Node.js version from .nvmrc
# (macOS/Linux nvm): nvm install && nvm use
# (Windows nvm-windows): nvm install 22 && nvm use 22
nvm install
nvm use
# Install dependencies
pnpm install
# Copy .env.example and configure
cp .env.example .env
# Edit .env with your API key# Development mode (auto-reload)
pnpm dev
# Production build
pnpm build
# Production run
pnpm startYou can use the MCP Inspector to debug the server:
# Run from source
pnpm inspect
# Run from built output
pnpm inspect:distpnpm inspect loads .env automatically via dotenv (see .env.example).
Contributions are welcome! Please see CONTRIBUTING.md for guidelines on how to contribute to this project.
See SECURITY.md for security policy and reporting vulnerabilities.
This is a community project provided "as is" with no guaranteed support. See SUPPORT.md for details.
MIT © Jacob Hartmann
List all advertiser IDs available to your Vibe API key.
Inputs: no named parameters. Returns: object
List all app IDs for a specific advertiser.
Inputs: advertiser_id (required). Returns: object
List campaign details for a specific advertiser.
Inputs: advertiser_id (required). Returns: object
Check that the Vibe MCP server is running and that API credentials are configured. Does not make any API calls to Vibe.
Inputs: no named parameters.
List purchase IDs for a specific advertiser.
Inputs: advertiser_id (required), start_date, end_date. Returns: object
Create an async report for a Vibe advertiser. Returns a report_id to check status with vibe.reports.status. Rate limited to 15 requests per hour.
Inputs: advertiser_id (required), start_date (required), end_date (required), metrics (required), +7 more. Returns: object
Check the status of an async report. Returns status and download URL when complete.
Inputs: report_id (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool targets a distinct resource (advertisers, apps, campaigns, etc.) with clear actions, even the two report tools are well-separated by create vs status. No overlap or ambiguity.
All tools follow the same 'vibe.<resource>.<action>' pattern (e.g., vibe.advertisers.list, vibe.reports.create). The only exception is vibe.ping, which is a standalone health check, but it's still consistent in style.
With 7 tools, the set is scoped well for a media platform server covering listing, reporting, and health checks. It is neither too few nor too many, filling a useful niche.
The server covers listing of key resources and async report creation/status, which aligns with its apparent purpose. However, it lacks CRUD for advertisers, campaigns, and purchases, which could be considered minor gaps for a more complete management interface.
Amazon Ads and Seller Central for your AI assistant: reports, campaign management and seller data.
Manage your Vidalytics videos and analytics from your AI assistant.
Real-time Meta, Google, LinkedIn and TikTok ad library access for AI assistants. No API keys.
Run Google Ads and Meta Ads from ChatGPT or Claude: audit wasted spend, create and manage campaigns.
