Put your AI-built website online from the chat.

What you need

• A VibingView account with a verified email address.
• At least one VibingView server that is running. Servers are set up in your VibingView dashboard, not in the chat; the assistant never buys anything.
• Your project: a GitHub repository, a ZIP of the project folder, or (for a small static site) the files themselves.

Connect

1. ChatGPT: add VibingView from the ChatGPT app directory (once it is listed), or as a custom connector with the server URL https://vibingview.com/api/mcp.
2. Claude: add VibingView from the Claude connector directory (once it is listed), or under Settings → Connectors → Add custom connector with https://vibingview.com/api/mcp.
3. Claude Code: claude mcp add --transport http vibingview https://vibingview.com/api/mcp, then run /mcp to sign in.
4. You sign in on VibingView and choose what the assistant may do. Without “publish, update and roll back”, each deployment waits for your approval on VibingView.

Manage or disconnect at any time under Dashboard → Connected apps.

Supported projects

• Static website (HTML, CSS, JavaScript)
• Vite single-page app (built to static files)
• Next.js static export
• Next.js app with a server
• Node.js web server

Projects with their own Dockerfile, Python and PHP apps can be deployed from the VibingView dashboard; the assistant explains this instead of guessing. Uploads: one ZIP up to 100 MB (500 MB unpacked). Files sent from the chat: up to 60 files and 1.5 MB.

What the assistant can do

• Get connected VibingView account – reads only
• List servers for websites – reads only
• List websites – reads only
• Get website details – reads only
• Create a secure upload link – makes a change
• Import project files or a GitHub repository – makes a change
• Inspect an imported project – reads only
• Prepare a deployment for review – reads only
• Deploy a reviewed plan – makes a change
• Check deployment progress – reads only
• Read deployment logs – reads only
• List website releases – reads only
• Roll back a website – makes a change

Data and privacy

• VibingView receives only what a tool sends: project files you import, and IDs and settings in tool calls. It does not receive or store your conversation.
• Imported project files are kept for 7 days unless deployed; deployed versions follow your website's release history. Unused upload links expire after 30 minutes.
• Connection records (which app, when, permissions) are kept until you disconnect plus 90 days; access tokens expire after one hour.
• For reliability we record tool names, outcomes and durations, never arguments, file contents, logs or messages (kept 90 days).
• Logs shown to the assistant are redacted for common secrets. Read the full privacy policy and terms.

Support

Email support@vibingview.com or open a ticket in the dashboard.

Questions

Does the assistant buy anything?

No. The connection only works with servers your VibingView account already has. It cannot buy servers, domains or credit, top up your wallet or change billing. Deploying a website onto an existing server does not charge your wallet.

Do I need to paste passwords or API keys into the chat?

No, and you should not. You approve the connection on the VibingView website. Secret settings (API keys, database passwords) are set on the website's settings page in VibingView; the assistant only ever sees their names.

Can the assistant read the files on my computer?

Only if your chat app gives it those files. Otherwise it gives you a private upload link: you upload a ZIP of your project in the browser while signed in to VibingView.

What happens if a deployment fails?

Your current version stays online. The assistant shows what the build log confirmed and the next step, for example a missing start script or a setting you still need to add.

Does a rollback restore my database?

No. A rollback switches the website's code back to an earlier saved build. Database contents, uploaded files and environment variables stay as they are now.