Skip to content
VI Engine
Waitlist
Beta 2 / coming soon · Q4 2026 target

MCP for AI agents

Give your AI agent a social growth engine

Turn brand knowledge into campaigns, publish reliably, measure performance, and carry what works into the next campaign.

MCP access is planned for Beta 2. It is not available yet, and Q4 2026 is a target, not a guaranteed launch date. No assistant directory listings are live.

Join the beta waitlistSee what is live today

Live today and coming

The engine is live today. MCP brings it to your agents.

Live todayPrivate beta

The VI Engine app

VI Engine is a social content lifecycle OS. It runs your entire content presence, so you can stay where leverage is created.

  • Read available trend snapshots to inform planning. The expanded cited trends and SEO intelligence layer is coming soon for Beta 2 (Q4 2026 target).
  • Build campaigns from your brand voice and campaign memory, so each round starts with context instead of a blank page.
  • Brief the Autonomous Agent with an objective or launch milestone. It recalls your brand voice, plans multi-platform drafts, streams its activity and prepares scheduling actions for your confirmation. Available on Pro and Team.
  • Adapt every draft for each platform and generate companion images, with a live preview per channel.
  • Publish across Facebook Pages, Instagram professional accounts and LinkedIn personal profiles, with next-best actions that balance your schedule.
  • Review available analytics and recall campaign learnings to inform the next decision. Missing signals are not proof of performance.

Access is opening in controlled waves through the beta waitlist.

Coming with MCPPlanned

The same engine, for your own AI agents

An MCP server will bring this same engine to the AI agents you already use: brand memory, trend research, campaign planning, publishing and learning. Your agents will work from the same memory, research and results your team uses.

  • Agents will work in the same workspace as your team.
  • Agents will run under scopes and limits you set.
  • Every agent action will leave a receipt.
  • Ads tools are planned too, and will need a person’s approval.

Planned. Not available yet.

Assistant directories

Coming soon: planned ways to find VI Engine

After Beta 2 access is ready, we plan to submit VI Engine to these directories. Each listing will require its own review; none is available today.

  • Official MCP RegistryComing soon
  • SmitheryComing soon
  • CursorComing soon
  • Claude Connectors DirectoryComing soon
  • ChatGPT / CodexComing soon

Planned submissions only. VI Engine is not listed in these directories today.

What agents will be able to do

Planned: a growth loop your agent can run in VI.

Everything in this section is planned. None of it is available yet.

Planned

Start with context

In a new session, an agent will be able to read your brand context and history, so it starts from what VI already knows instead of a blank page.

Planned

From one brief to drafts

One brief will become platform-specific drafts and images, planned with VI’s trend research and your brand context.

Planned

Publish reliably

Agents will be able to schedule and publish. The work will survive the agent disconnecting, and retries are designed so the same post is not published twice.

Planned

See what happened

Agents will be able to see dated performance for each post.

Planned

Carry learnings forward

What worked will carry into the next campaign, so the next round starts from results instead of from scratch.

Planned

One shared workspace

Humans and agents will work on the same workspace items.

Control and safety

Planned: you stay in control of what an agent can do.

Agents will act on real social accounts. These are the controls we plan to give you.

Planned

Scoped access

You will grant tool scopes for a workspace connection. Workspace and brand checks will limit what tools can access.

Planned

Posting limits

Publishing will remain subject to workspace plan limits and approval checks.

Planned

Pause or revoke

You will be able to pause or revoke an agent’s access at any time.

Planned

A receipt for every action

Every action an agent takes will leave a receipt you can review.

Works with your stack

Planned: connect VI Engine over MCP.

After Beta 2 access is ready, supported AI assistants will be able to connect to VI Engine over MCP.

Planned

Directly over MCP

Connect a supported AI assistant to VI Engine over MCP, after access opens.

MCP access is planned for Beta 2. The connection is not available yet.

The assistant directory submissions listed above are planned and are not live.

Start with the engine that is live today.

VI Engine is opening through a private beta, in controlled waves. Join the waitlist for access to the app.

Join the beta waitlistRead the docs

This page describes planned work. Scope and timing may change.