Vibe.co MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBE_API_KEY | Yes | Vibe API key | |
| MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| MCP_SERVER_HOST | No | Host to bind the HTTP server to | 127.0.0.1 |
| MCP_SERVER_PORT | No | Port for the HTTP server | 3000 |
| VIBE_API_BASE_URL | No | API base URL (override for testing) | https://clear-platform.vibe.co/rest/reporting/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibe.pingA | Check that the Vibe MCP server is running and that API credentials are configured. Does not make any API calls to Vibe. |
| vibe.advertisers.listA | List all advertiser IDs available to your Vibe API key. |
| vibe.apps.listA | List all app IDs for a specific advertiser. |
| vibe.campaigns.listA | List campaign details for a specific advertiser. |
| vibe.reports.createA | 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. |
| vibe.reports.statusA | Check the status of an async report. Returns status and download URL when complete. |
| vibe.purchases.listA | List purchase IDs for a specific advertiser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| campaign-report | Guided workflow for creating a campaign performance report |
| setup-api-key | Instructions for configuring the Vibe API key |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| advertisers | List all advertisers available to your Vibe API key |
TDQS
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.