Marketing from Windsurf

See it work

From one prompt to reviewable drafts

stripe-analytics

Windsurf

VIBECOM

stripe-analytics

src

app

TSlayout.tsx

TSpage.tsx

TSloading.tsx

api

TSstripe/route.ts

TSwebhooks/route.ts

dashboard

TSpage.tsx

TSactions.ts

components

TSRevenueChart.tsx

TSPaywall.tsx

TSMetricCard.tsx

TSUpgradeBanner.tsx

growth

TSlaunch-materials.ts

TSapproval-flow.ts

TSschedule.ts

lib

TSstripe.ts

TSanalytics.ts

TSformat.ts

{}package.json

TStailwind.config.ts

MDREADME.md

•.env.local

MCP live

dashboard/page.tsx

RevenueChart.tsx

launch-materials.ts

page.tsx

1import { RevenueChart } from "@/components/RevenueChart"
2import { MetricCard } from "@/components/MetricCard"
3import { Paywall } from "@/components/Paywall"
4import { getMRR } from "@/lib/stripe"
5import { getActivation } from "@/lib/analytics"
6import { launchMaterials } from "@/growth/launch-materials"
7
8export default async function Dashboard() {
9  const mrr = await getMRR()
10  const activation = await getActivation()
11  const materials = launchMaterials(mrr)
12  const reviewWindow = "tomorrow 9:00 AM"
13
14  return (
15    <main className="grid gap-6">
16      <section className="grid grid-cols-3 gap-4">
17        <MetricCard label="MRR" value={mrr} />
18        <MetricCard label="Activation" value={activation} />
19        <MetricCard label="Review" value={reviewWindow} />
20      </section>
21      <RevenueChart value={mrr} />
22      <Paywall variant="business" materials={materials} />
23    </main>
24  )
25}
26
27// VibeCom reads this product context before drafting
28const launchSignal = {
29  shipped: true,
30  feature: "Stripe MRR dashboard",
31  audience: "growing SaaS teams",
32  channels: ["x", "linkedin", "blog"],
33  reviewAt: reviewWindow,
34}
35
36export const schedule = {
37  x: "tomorrow 9:00",
38  linkedin: "tomorrow 10:30",
39  blog: "ready to review",
40}

VibeCom MCP usage

Ask VibeCom to use this product context...

@ stripe-analytics

⌘K context

dev0 errors0 warningsAI marketing agents

Ln 20, Col 34TypeScript ReactPrettier5 drafts ready

Setup

Connect VibeCom to Windsurf

Windsurf's Cascade panel accepts custom MCP servers over Streamable HTTP with OAuth login. Add the VibeCom server URL, then authorize in the browser.

1
Open Windsurf Settings (Cmd/Ctrl+,) → Cascade → MCP servers → Add custom server.

2

Add the VibeCom server config:

{
  "mcpServers": {
    "vibecom": {
      "serverUrl": "https://www.vibecom.app/mcp"
    }
  }
}

3
Restart Windsurf. It opens a browser window for OAuth login — click Authorize.

Need another MCP client? See the full MCP setup guide for every supported client.

Why this matters

Marketing should start while product context is fresh

Windsurf is a fully AI-native code editor for builders who want deep product context and autonomous agent actions. VibeCom extends that same agentic workflow into distribution: product updates, features, and launches turn into platform-specific drafts without switching tools.

Best for builders and technical teams using Windsurf as their primary development environment who want a Windsurf MCP marketing workflow that fits naturally into how they already ship.

The product context is scattered

Most marketing tools ask you to start from a blank composer. The useful context is already in product updates, changelogs, launch notes, customer messages, and product decisions.

Every channel needs a different version

A good X post, LinkedIn post, and blog draft cannot be identical. VibeCom rewrites the same update into platform-native drafts while preserving the core message.

You still need control

AI marketing should not mean spam. The right workflow generates drafts, keeps them reviewable, and lets you approve, edit, skip, or publish.

Use cases

A specific workflow for builders who ship often

VibeCom is not a generic social scheduler. It is an AI marketing agent platform for people growing products online. These tool pages focus on one use case: keeping distribution close to the product workflows you already use.

Turn a shipped feature into launch posts

Check pending posts without opening a dashboard

Generate images for social content

Review and approve posts before publishing

Keep marketing in the same flow as building

Common questions

VibeCom is built for people who want help with distribution, but still want the final say before content goes live.

Does VibeCom work with Windsurf's MCP protocol?

Yes. VibeCom exposes its AI marketing agents as an MCP server that Windsurf can connect to. Once connected, you can generate posts, create images, approve drafts, and publish from Windsurf.

Is this a replacement for Buffer?

Not exactly. Buffer is mainly a scheduling dashboard. VibeCom is a growth agent that understands product context, generates channel-specific content, creates images, queues drafts, and can publish after approval.

Does it publish automatically?

It can publish approved posts to connected channels, but the core workflow is approval-first. You can approve, edit, reject, or publish manually depending on the channel and plan.

Why use this from a code editor?

Because the best marketing input often appears while shipping. If you have to open another dashboard later, the context gets weaker and the update often never becomes content.

From one prompt to reviewable drafts

One workflow, from product context to reviewed post

Share product context

Tell the agent

Review drafts

Publish

Connect VibeCom to Windsurf

Marketing should start while product context is fresh

The product context is scattered

Every channel needs a different version

You still need control

A specific workflow for builders who ship often

Use natural language, not a new dashboard habit

Common questions

Does VibeCom work with Windsurf's MCP protocol?

Is this a replacement for Buffer?

Does it publish automatically?

Why use this from a code editor?

Related guides

Marketing from Cursor

Marketing from Claude Code

MCP Marketing

Turn your next ship into distribution