swebsy/MCP

**Build and edit real websites with the coding agent you already pay for — no per-token AI fees.**
@swebsy/mcp is an MCP server that lets
Claude Code, Codex, Cursor, Windsurf, Cline, GitHub Copilot — or any agent that
speaks the Model Context Protocol — drive an open Swebsy
Studio tab. Your agent discovers templates, creates and opens sites, renames projects,
adds sections, edits content, switches pages, sets every site setting (SEO,
favicon, fonts, analytics, robots.txt, deploy target), captures screenshots, and
exports the finished site, all over a local 127.0.0.1 WebSocket relay. Nothing is proxied through our servers, and Studio redacts
secrets (API keys, deploy tokens, chat history) before anything crosses the
bridge. Your coding agent's own service and privacy policy still apply to the
non-secret content it receives.
> **Using ChatGPT or Claude (the apps)?** You don't need this package. Add
> https://mcp.swebsy.com/mcp as a custom app in ChatGPT or a custom connector
> in Claude, sign in to Swebsy and click Allow —
> setup steps. This
> package is for coding agents that run on your machine.
What is Swebsy?
Swebsy is a **visual website builder** with a real ownership model: you build
visually, export real files (HTML/CSS/JS), and publish wherever you want — no
lock-in, no proprietary hosting requirement. The free plan runs fully local;
no account required.
Why use an MCP instead of a built-in AI panel?
Most "AI website builders" bolt on a chat panel and **bill you per token** on
top of the model you're already subscribed to. Swebsy takes the opposite
approach — it exposes the editor as a tool your **own** agent can drive:
- **No per-token API billing.** Swebsy isn't in the loop on model costs. You use
the Claude, Cursor, Codex, or Copilot plan you already pay for.
- **Runs on your machine.** The agent talks to your open Studio tab over a local
127.0.0.1 bridge — prompts and content aren't shipped off to be metered.
- **Bring your own agent.** Your model, your custom instructions, your workflow
— not a locked-down wrapper. Any MCP-capable agent works.
- **You own the output.** Everything the agent builds exports as real, portable
files you can host anywhere.
Setup
One command registers Swebsy with every supported agent it finds (Claude Code,
Codex, Cursor, Windsurf, VS Code, Cline):
It never changes an existing swebsy entry and never rewrites a config file it
can't parse; it reports each agent's result. Or register it by hand:
**Claude Code**
**Codex**
**Cursor** — add to ~/.cursor/mcp.json (or a project's .cursor/mcp.json):
**GitHub Copilot (VS Code)**
**Windsurf** — add the same JSON block to ~/.codeium/windsurf/mcp_config.json.
**Cline** — add the same JSON block to cline_mcp_settings.json, or use the
extension's MCP Servers → Configure button, which opens it:
- macOS ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Linux ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Windows %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
**Cline CLI** (npm i -g cline) is a separate install from the extension, with
its own config at ~/.cline/data/settings/cline_mcp_settings.json and a nested
transport block:
Or let its own CLI write it: cline mcp add swebsy --yes -- npx -y @swebsy/mcp.
Pairing
1. Run npx -y @swebsy/mcp setup
2. Restart your agent.
3. Ask it: "Build me a landing page with Swebsy." The first request opens Studio and connects it.