Connect VibeHost as an MCP app in ChatGPT. Deploy Canvas artifacts to a permanent, shareable URL you control — no terminal, no code. Set up in under a minute.

You built something great in ChatGPT Canvas — a dashboard, a report, an interactive tool. Now someone asks: "can you send me a link?"

ChatGPT's built-in share creates a chatgpt.com conversation link. That shares the whole chat, not just the artifact — and you can't control who sees it after they have the URL. If you want a permanent URL you control, on your own subdomain, with privacy settings — connect VibeHost.

No terminal. No code. One-time setup in ChatGPT, then say "deploy this" in chat.

VibeHost is a hosting platform designed for AI workflows — deploy Canvas artifacts to a permanent URL with built-in privacy controls, team sharing, and custom domains. ChatGPT connects to VibeHost through the Model Context Protocol (MCP), giving you access to 46 deployment and management tools through natural language. ChatGPT is one of two officially supported chat clients alongside Claude Desktop.

Connect VibeHost to ChatGPT

ChatGPT connects to VibeHost through the MCP protocol. You'll register VibeHost as a custom app in ChatGPT's developer settings.

Requires a paid ChatGPT subscription (Plus, Pro, Team, or Enterprise). Free accounts do not have access to developer mode.

Step 1 — Open Settings

Open chatgpt.com in your browser. Click your profile icon in the bottom-left corner, then click Settings.

Step 2 — Enable developer mode

In Settings, go to Apps. Click Advanced settings and toggle on Developer mode.

This unlocks the ability to create custom MCP apps in ChatGPT.

Step 3 — Create a new app

Return to the Apps section. Click Create app.

Step 4 — Enter VibeHost details

Fill in the app creation form:

Name: VibeHost
URL: https://api.vibehost.com/mcp
Authentication: Select OAuth

Double-check that the URL is exactly https://api.vibehost.com/mcp — no trailing slash, no extra path.

Step 5 — Authorize

Click Create. ChatGPT opens a browser window for OAuth sign-in. Sign in with Google or email — the same account you use on vibehost.com.

Once authorized, VibeHost is registered as an app in your ChatGPT account. The connection persists across sessions — you only do this once.

Step 6 — Activate VibeHost in a chat

Start a new chat. In the message bar, click the + button, then click More. Find VibeHost in the list and select it.

ChatGPT now has access to VibeHost tools for this conversation. You need to activate VibeHost each time you start a new chat where you want to deploy.

Deploy an artifact

With VibeHost activated, just tell ChatGPT what you want:

Deploy this to VibeHost.

Or be more specific:

Deploy this dashboard to VibeHost as an app called "q2-metrics". Make it public.

ChatGPT calls create_app + create_deployment behind the scenes and returns a live URL like https://q2-metrics-yourworkspace.vibehost.space.

The artifact renders exactly as you see it in Canvas — interactive elements, charts, animations all work. Anything that needs a backend (API calls to localhost, database connections) won't work since VibeHost serves static files.

What you can do from chat

Once VibeHost is activated in a conversation, you can ask ChatGPT to:

Say this	What happens
"Deploy this to VibeHost"	Creates an app + deploys the current artifact
"Update the deploy"	Pushes a new version to the same URL
"Make it public" / "Make it private"	Changes visibility
"Roll back to the previous version"	Reverts to the last deployment
"Share this with sarah@acme.com"	Adds a viewer grant by email
"Give me a share link that expires in 7 days"	Creates a time-bound access link
"Delete the app"	Removes the app and all deployments

ChatGPT will ask for confirmation before destructive actions (delete, change visibility to public).

When to use this vs. the Chrome extension

	ChatGPT + MCP	Chrome extension
How	Talk to ChatGPT in chat	Click a button on the Canvas artifact
Best for	Iterating on deploys ("make it public, now roll back, now share with Sarah")	Quick one-off deploys from any AI canvas
Works with	ChatGPT only	Claude, ChatGPT, Gemini, AI Studio, v0
Access control	Full (grants, share links, passwords, visibility)	Basic (private by default, change via CLI/dashboard)

Both deploy to the same VibeHost backend. A deploy started from the extension can be updated from chat, and vice versa.

Troubleshooting

"Developer mode not available" — Developer mode requires a paid ChatGPT subscription (Plus, Pro, Team, or Enterprise). Free accounts cannot create custom MCP apps.

"Can't find VibeHost in the apps list" — Make sure Developer mode is enabled in Settings → Apps → Advanced settings. Try refreshing the page after enabling it.

"OAuth authorization fails" — Delete the app and create it again. Verify the URL is exactly https://api.vibehost.com/mcp with no trailing slash. If you're behind a corporate proxy or VPN, try from a different network.

"VibeHost tools not showing in chat" — You need to activate VibeHost in each new conversation. Click the + button in the message bar → More → toggle VibeHost on.

Artifact deploys but doesn't render correctly — VibeHost serves static files. If your artifact fetches from localhost or calls a backend API, those calls will fail once deployed. Keep artifacts self-contained.

FAQ

Does ChatGPT support VibeHost? Yes. ChatGPT is an officially supported VibeHost client. Connect via MCP in Settings → Apps — no terminal or coding required. All 46 VibeHost tools (deploy, rollback, custom domains, access control) are available through natural language in chat.

Do I need a paid ChatGPT subscription? Yes. Developer mode — required to add custom MCP apps like VibeHost — is available on ChatGPT Plus, Pro, Team, and Enterprise plans. Free accounts cannot create custom MCP apps.

Can I deploy from ChatGPT without a terminal? Yes. The entire workflow happens inside the ChatGPT chat interface. Say "deploy this to VibeHost" and ChatGPT handles the rest — creating the app, uploading files, and returning a live URL. No terminal, no CLI, no code.

Deploy from ChatGPT — Connect VibeHost via MCP