Guided Onboarding
Follow the Growth Autopilot path from MCP connection to first reviewed posts.
Growth Autopilot should never leave you guessing what to do next. The intended onboarding path is product setup -> research -> channels -> first materials -> first posts -> daily review.
Who Can Start
Every VibeCom account can connect MCP: Free, Pro, and Growth. The OAuth connection is not plan-gated.
Plan gates apply when a tool performs paid work:
- Free: Can connect MCP and authorize an editor. Paid Growth Autopilot actions return an upgrade prompt.
- Pro: Can use Growth Autopilot to create products, research, generate content, review posts, and auto-publish to X and LinkedIn, with Pro limits.
- Growth: Gets the full workflow, including Growth-only features such as competitor radar, SEO keywords, image generation, and custom skills.
The Recommended Path
- Connect MCP β Install the VibeCom MCP server in Cursor, Claude Code, Codex, VS Code, or another MCP-compatible editor.
- Authorize VibeCom β The editor opens OAuth. Log in and click Authorize.
- Create the product β Paste the onboarding prompt in your IDE. The agent reads your landing page, README, and package metadata and calls
create_product. Research kicks off automatically in the background β no separate call needed. - Wait for research β Research usually takes 2-3 minutes. Status stays at
onboardingwhile product research and default setup run, then flips toactivewhen product context is ready (orresearch_failedif something goes wrong). Materials and first drafts may continue in the background after setup. - Adjust channels β Research creates default X and blog channels. Add or edit channels for LinkedIn, blog, or other destinations. Each channel stores platform, tone, language, and schedule.
- Generate the first batch β Ask the IDE agent to generate content from your current product context.
- Review in the dashboard β Open
/console/growth, approve, edit, schedule, or skip posts.
IDE Onboarding Prompt
Paste this into your editor after MCP is connected:
After research completes (you'll see the product status flip to active in the dashboard), continue with:
What The Agent Should Do
When there are no products, the agent should ask for or infer product name, URL, and description, then create the product.
When a product exists but has no channels, the agent should suggest practical channels based on the product type and create the ones you approve.
When channels exist but no materials exist, the agent should collect or ask for launch notes, feature updates, customer quotes, metrics, or founder lessons before generating posts.
When posts exist, the next action is review: approve, edit, schedule, publish, or reject.
Web Dashboard Fallback
You can complete the same flow from the dashboard:
- Open
/console/growth. - Create a product from your URL.
- Wait for onboarding research.
- Add channels.
- Review generated posts from the Posts page.