VibeBridgeIf you would rather have the agent do the publishing than upload files by hand, you connect your AI tool over MCP. MCP, the Model Context Protocol, is simply a standard way for an AI tool to use external tools. Connect your AI tool over MCP and it gains real publishing tools for your VibeBridge site: it can put pages live, update content and manage SEO directly from the conversation, instead of you exporting files and dragging them into the portal.
VibeBridge is the publishing and maintenance layer for your site, not a builder. You build the site with your AI tool; the MCP connection lets that same tool get it online and keep it current. There are two connection paths depending on the tool, and both point at the same server.
Two connection paths over MCP
- OAuth (one click): Claude on the web and ChatGPT connect by choosing "Sign in with VibeBridge". Their connector dialog has no field for a header, so they link your account through a sign-in instead of a key.
- API key: Claude Code, Cursor, Windsurf and other developer tools connect with an API key you create in the VibeBridge portal.
- Server URL: both paths use the same address, https://app.vibebridge.ai/api/mcp.
- Click-by-click path: the exact steps for each tool live at app.vibebridge.ai/connect.
Step 1: Create your VibeBridge account
Sign up at app.vibebridge.ai/signup. The trial runs 7 days, there is no setup fee, you can cancel monthly, and plans start at 9 € per month (excl. VAT); details are on the pricing page. Hosting is EU-based (data in Frankfurt) on a global CDN, with automatic SSL.
Step 2: Connect Claude on the web or ChatGPT with OAuth
Claude on the web and ChatGPT both connect the same way. Add VibeBridge as a connector using the server URL https://app.vibebridge.ai/api/mcp, then choose "Sign in with VibeBridge". That sign-in links the connector to your account, so you never paste a key into a field these tools do not have. Once it confirms, the connection is live for the rest of the conversation and the ones after it.
The setup guide at app.vibebridge.ai/connect shows where each tool keeps its connector settings, since the menus move between versions.
Step 3: Connect Claude Code, Cursor or Windsurf with an API key
Developer tools authenticate with a key instead. First create an API key in the VibeBridge portal. Then add the MCP server to your tool's configuration: the server URL is https://app.vibebridge.ai/api/mcp, authenticated with that key. In Claude Code you add it as an MCP server; in Cursor and Windsurf you add it to the MCP configuration. The same key works for any other dev tool that speaks MCP, and for your own scripts and CLIs that call the API.
Tip: Treat the API key like a password. Keep it out of your repo and out of any file you commit. If it ever leaks, revoke it in the portal and create a new one; the old key stops working immediately.
Step 4: Ask the agent to publish and maintain the site
Once connected, the agent has publishing tools, not just file access. Ask it to publish a page and the live URL comes back in the chat, on EU hosting with SSL handled for you. The connection stays useful long after launch. When you ask, the agent can publish pages, update content, manage SEO titles and descriptions, handle forms, media and redirects, all on the live site. It only acts when asked, so nothing changes on the site until you tell it to.
Every publish also generates sitemap.xml, robots.txt, canonical tags and llms.txt, and FAQ sections become structured data automatically. The technical SEO baseline is covered; content quality is still your job. If you get stuck, write to support@vibebridge.ai.
Frequently asked questions
What is MCP in one line?
MCP, the Model Context Protocol, is a standard way for an AI tool to use external tools. Connecting your AI tool over MCP gives it real VibeBridge actions, like publishing a page or editing SEO, rather than just reading or writing files on your machine.
Why do Claude on the web and ChatGPT use a sign-in instead of an API key?
Their connector dialog has no field for an authentication header, so a pasted key has nowhere to go. "Sign in with VibeBridge" links your account over OAuth instead. Developer tools like Claude Code, Cursor and Windsurf do have a place for a key, so they use one.
What can the connected agent actually do?
It can publish pages, update content, and manage SEO titles and descriptions, forms, media and redirects on the live site. It acts only when you ask, so the site does not change on its own.
Where do I find the click-by-click setup for my tool?
At app.vibebridge.ai/connect. It walks through each tool, the server URL https://app.vibebridge.ai/api/mcp, and whether that tool connects by sign-in or by API key.
How do I keep my API key safe?
Treat it like a password: keep it out of your repository and any committed file, and do not share it. If it leaks, revoke it in the portal and create a new one. The replaced key stops working straight away.
Do I have to use MCP, or can I still upload files?
You can do either. The browser upload in the portal takes HTML files and images together, and you can add the MCP connection later. Both routes work on the same site, so a manual upload and an agent connection sit side by side.