Schema | Vibe.co MCP Server

Vibe.co MCP Server

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

Features and capabilities supported by this server

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.

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

Contextual data attached and managed by the client

Name	Description
`advertisers`	List all advertisers available to your Vibe API key

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jacob-hartmann/vibeco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server