Field noteOct 21, 20261 min read1 source

Slack | v0 Docs

In one minute

v0 has documented a Slack bot that lets teams request code changes by mentioning `@v0` in a Slack channel.

What changed: v0 now offers a Slack beta that can turn channel prompts into code changes and pull requests; no prior document reports this integration.

The feature is currently marked beta. The bot reads the conversation thread for context, makes code changes, creates a branch, and opens a pull request.

Users can attach images and files, continue work by mentioning the bot again in the same thread, and configure a default GitHub repository and branch for a channel. Vercel generates a preview deployment for commits pushed to the resulting branch. The documentation says a user may also specify a repository, branch, Vercel project name, deployment URL, or project ID in a request.

Installation may require Slack admin permissions or workspace-level approval. Each Slack user links a Vercel account independently, needs access to the target GitHub repositories, and needs a v0 Premium, Plus, or Enterprise plan. v0 says the bot can see only channels the user's account can access.

The source does not give a launch date or plan prices. Although the supplied announcement calls this “Slack MCP,” the public documentation describes a Slack app and bot; it does not establish the implementation as an MCP connection.

Evidence / sources

  1. 1v0.app/docs/slack
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicMcpExplore the mcp topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract