Swebsy MCP

Name: Swebsy MCP
Author: swebsy

by swebsyversion 0.16.1i★ –iComputer or cloud

Registry nameio.github.swebsy/mcp

Install

Overview

Description from the maker (original English)

Build and edit real websites in Swebsy Studio from your coding agent — no per-token AI fees.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: SWEBSY_AGENT_PORT, SWEBSY_AGENT_DIR, SWEBSY_APP_URL, SWEBSY_NO_OPEN

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.swebsy.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "swebsy": {
      "command": "npx",
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "env": {
        "SWEBSY_AGENT_PORT": "your-value",
        "SWEBSY_AGENT_DIR": "your-value",
        "SWEBSY_APP_URL": "your-value",
        "SWEBSY_NO_OPEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http swebsy https://mcp.swebsy.com/mcp

Or run it on your computer

claude mcp add swebsy --env SWEBSY_AGENT_PORT=your-value --env SWEBSY_AGENT_DIR=your-value --env SWEBSY_APP_URL=your-value --env SWEBSY_NO_OPEN=your-value -- npx -y @swebsy/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "swebsy": {
      "url": "https://mcp.swebsy.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "swebsy": {
      "command": "npx",
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "env": {
        "SWEBSY_AGENT_PORT": "your-value",
        "SWEBSY_AGENT_DIR": "your-value",
        "SWEBSY_APP_URL": "your-value",
        "SWEBSY_NO_OPEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "swebsy": {
      "type": "http",
      "url": "https://mcp.swebsy.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "swebsy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "env": {
        "SWEBSY_AGENT_PORT": "your-value",
        "SWEBSY_AGENT_DIR": "your-value",
        "SWEBSY_APP_URL": "your-value",
        "SWEBSY_NO_OPEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.swebsy.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SWEBSY_AGENT_PORT env
Port the local relay listens on (default 37373)
SWEBSY_AGENT_DIR env
Where screenshots and exports land (default: .swebsy-agent in the workspace)
SWEBSY_APP_URL env
Studio origin used for the pairing link (default https://studio.swebsy.com; set this for local or self-hosted Studio)
SWEBSY_NO_OPEN env
Set to skip auto-opening the pairing link in the browser

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account swebsy, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 426 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 4906 servers in this category
Published to the registry more recently than 84% of the other 4906 servers in this category
Basic checks equal to or better than 100% of the other 4906 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Swebsy MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.16.1) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@swebsy/mcp — connect your coding agent to Swebsy

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):

npx -y @swebsy/mcp setup

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

claude mcp add swebsy -- npx -y @swebsy/mcp

Codex

codex mcp add swebsy -- npx -y @swebsy/mcp

Cursor — add to ~/.cursor/mcp.json (or a project's .cursor/mcp.json):

"mcpServers": { "swebsy": { "command": "npx", "args": ["-y", "@swebsy/mcp"] } } }

GitHub Copilot (VS Code)

code --add-mcp '{"name":"swebsy","command":"npx","args":["-y","@swebsy/mcp"]}'

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:

"mcpServers": { "swebsy": { "transport": { "type": "stdio", "command": "npx", "args": ["-y", "@swebsy/mcp"] } } } }

Or let its own CLI write it: cline mcp add swebsy --yes -- npx -y @swebsy/mcp.

Pairing

Run npx -y @swebsy/mcp setup
Restart your agent.
Ask it: "Build me a landing page with Swebsy." The first request opens Studio and connects it.

You connect once per browser. Whenever no Studio tab is connected, the next tool call opens Studio and reconnects it by itself (it waits up to 20 seconds). The session is saved in ~/.swebsy/agent- .session, so it survives the bridge restarting.

Claude Code also lists a /swebsy:swebsy (MCP) prompt that walks the agent through connecting and opening a site. Other agents show MCP prompts their own way, if at all.

To pair by hand (the browser didn't open, Swebsy runs in a different browser, or SWEBSY_NO_OPEN=1 is set):

Ask your agent to run the swebsy_start_pairing tool. It opens the pairing link in your default browser automatically, and also returns the link, raw code, and relay port.
Swebsy connects automatically and strips the code from the address bar after it is used. (Set SWEBSY_NO_OPEN=1 to skip the auto-open and just get the link back.)
If the browser didn't open — or Swebsy is running in a different browser — open the returned link there yourself, or use the fallback fields under Global settings → Coding agents → Didn't connect? Pair by hand: paste the raw code, leave the port at 37373 unless you changed SWEBSY_AGENT_PORT, and click Connect.
Prompt your agent as usual — it drives the tab through the swebsy_* tools.

Keep the Studio tab open. If the browser puts it to sleep, tools return tab_unresponsive until you click the tab. Pinning it may help, or add Studio under Chrome's Settings → Performance → "Always keep these sites active".

Full guide: https://docs.swebsy.com/settings/ai-coding-agent/

Multiple agents

Several coding agents can share one paired Studio tab. Register @swebsy/mcp in each agent and use the same SWEBSY_AGENT_PORT (default 37373) for every server. The first MCP process starts the local broker; later processes join it automatically, so Studio only needs to be paired once.

Studio shows the connected-agent roster and activity. The broker serializes commands across agents so the editor handles one command at a time, and routes each result, screenshot, and export back to the agent that requested it. One Studio tab can be paired to a broker at a time; pairing another tab revokes the previous tab.

What your agent can do

Once paired, your agent can work from Home or Studio. It can refresh and list installed templates, create the standard blank site or import a template unchanged, list saved-site metadata, open sites by ID, and rename their internal Swebsy names. Duplicate names are allowed; IDs are authoritative.

After swebsy_create_site or swebsy_open_site, poll swebsy_status until the expected siteId appears and editorReady is true. The agent can then read the page tree, add and edit sections, create and link pages, insert blocks, manage reusable symbols — including repeating one with different content per instance while its styling stays in sync — capture screenshots at any viewport, and export the project.

swebsy_list_sites returns metadata only — never page content, thumbnails, assets, revisions, or settings. Agent-driven create/rename analytics contain only source/template/site IDs, never internal names or site content.

Configuration

Env var	Default	Purpose
`SWEBSY_AGENT_PORT`	`37373`	Port the local relay listens on
`SWEBSY_AGENT_DIR`	workspace `.swebsy-agent`	Where screenshots/exports land
`SWEBSY_APP_URL`	`https://studio.swebsy.com`	Studio origin for the `swebsy_start_pairing` link (set for local/self-host)
`SWEBSY_NO_OPEN`	_(unset)_	Set to skip auto-opening the pairing link in the browser

Build from source

The published package is all you need to use this; the source is here to read, audit, or hack on.

git clone https://github.com/swebsy/MCP.git

cd MCP npm install npm test npm run build # -> dist/server.js

Point an agent at your local build instead of npm:

claude mcp add swebsy -- node /absolute/path/to/MCP/dist/server.js

This repo is a generated mirror, snapshotted from the mcp/ directory of

Swebsy's main repository on every release. Every file here is overwritten on

the next sync, so a pull request against it would be erased rather than

merged — please open an issue instead and we'll apply the change upstream.

License

MIT

Swebsy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

@swebsy/mcp — connect your coding agent to Swebsy

What is Swebsy?

Why use an MCP instead of a built-in AI panel?

Setup

Pairing

Multiple agents

What your agent can do

Configuration

Build from source

Links

License