Log inSubmit server
Swebsy MCP logo

Swebsy MCP

by swebsy

Drive Swebsy Studio from MCP-compatible coding agents to build, edit, screenshot, and export real websites.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Swebsy MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "swebsy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@swebsy/mcp"
      ],
      "env": {
        "SWEBSY_AGENT_PORT": "YOUR_VALUE_HERE",
        "SWEBSY_AGENT_DIR": "YOUR_VALUE_HERE",
        "SWEBSY_APP_URL": "YOUR_VALUE_HERE",
        "SWEBSY_NO_OPEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 45 tools correctly (10d ago).

Overview

swebsy/MCP MCP server connects coding agents to an open Swebsy Studio tab, allowing agents to create and edit websites through MCP tools. It runs locally through a 127.0.0.1 WebSocket relay, with pairing handled through the browser and no proxying through Swebsy servers. Agents can manage sites, pages, sections, content, settings, screenshots, and exports. Reach for it when you want to use an existing coding-agent subscription to control a visual website builder and retain portable site output.

Use cases

  • Build landing pages from Swebsy templates
  • Edit page sections and content through a coding agent
  • Configure SEO, fonts, analytics, and deployment settings
  • Capture responsive screenshots for review
  • Export portable website files

Key features

  • Local WebSocket relay to Swebsy Studio
  • Template, site, page, and section management
  • Reusable symbol and block editing
  • Site settings for SEO, fonts, analytics, and robots.txt
  • Viewport screenshot capture and project export
  • Multi-agent access through a shared broker

Tools45

What Swebsy MCP lets your agent do. Expand a tool for its parameters.

Verified live~17.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 44d

What it can do

From the 45 tools this server returned when we ran it; 45 declare their own safety hints.

Can delete or modify data · 9Handles credentials · 2Makes network requests · 3Read-only tools · 36
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age108 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @swebsy/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.9kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed45Callable tools this server registers over MCP.

How Swebsy MCP works

What swebsy/MCP MCP server does

swebsy/MCP exposes Swebsy Studio as a set of tools for MCP-compatible coding agents. An agent can discover templates, create or open sites, rename projects, inspect the page tree, edit sections and content, switch between pages, and export a completed project. It can also configure site-level options such as SEO, favicons, fonts, analytics, robots.txt, and deployment targets.

The server is intended for building real websites in Swebsy rather than generating text-only plans. Swebsy exports HTML, CSS, and JavaScript files, so the resulting project can be hosted outside Swebsy.

How it works

The package runs as a local stdio MCP server and starts a relay on the local machine. The relay communicates with an open Swebsy Studio browser tab over 127.0.0.1. On the first tool request, the server can open a pairing flow and connect Studio; subsequent sessions reuse a saved session file. The Studio tab must remain available while tools are being used. A sleeping browser tab can cause tab_unresponsive results until it is activated.

After creating or opening a site, an agent should poll swebsy_status until the expected site ID is present and the editor reports that it is ready. Multiple coding agents can use one paired tab when they share the same relay port. Commands are serialized so the editor processes one operation at a time, while results, screenshots, and exports are routed to the requesting agent. Pairing another Studio tab replaces the previous pairing.

Studio removes secrets such as API keys, deployment tokens, and chat history before data crosses the bridge. Non-secret content is still handled by the coding agent and its applicable service and privacy policies.

Setup and configuration

The package can register itself with supported agents using:

Terminal
npx -y @swebsy/mcp setup

Manual registration is also available through each client's MCP configuration. The package supports setup examples for Claude Code, Codex, Cursor, Windsurf, VS Code with GitHub Copilot, and Cline. A local source build can be used by pointing an agent at dist/server.js instead of invoking the npm package.

The main configuration variables are:

  • SWEBSY_AGENT_PORT: local relay port; defaults to 37373.
  • SWEBSY_AGENT_DIR: directory for screenshots and exports; defaults to .swebsy-agent in the workspace.
  • SWEBSY_APP_URL: Studio origin used in pairing links; useful for a local or self-hosted Studio deployment.
  • SWEBSY_NO_OPEN: set this variable to prevent automatic browser opening during pairing.

To pair manually, run swebsy_start_pairing and open the returned link in the browser containing Studio. The raw code and relay port are also returned for fallback pairing.

Tools and capabilities

The available swebsy_* tools cover site and editor operations, including:

  • Listing installed templates and saved-site metadata.
  • Creating blank sites or importing templates.
  • Opening sites by ID and renaming their internal Swebsy names.
  • Reading page structure, adding sections, editing content, and creating or linking pages.
  • Inserting blocks and managing reusable symbols, including per-instance content with shared styling.
  • Applying site settings for SEO, favicons, fonts, analytics, robots.txt, and deployment targets.
  • Capturing screenshots at selected viewport sizes.
  • Exporting the finished project.
  • Checking connection and editor readiness with swebsy_status.

Site listings return metadata only; they do not include page content, thumbnails, assets, revisions, or settings.

Limitations and notes

The browser tab must stay open and responsive. One Studio tab can be paired with one broker at a time, although several agents can share that paired tab. Site IDs are authoritative, and duplicate internal site names are allowed. The package is designed for coding agents running on the user’s machine; ChatGPT and the Claude app use a separate hosted connector flow rather than this package.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Swebsy MCP

swebsy/MCP is an MCP server that connects coding agents to an open Swebsy Studio tab through a local relay. Its main tools create and open sites, edit pages and sections, manage settings and reusable symbols, capture screenshots, check editor status, and export finished website projects.

Run `npx -y @swebsy/mcp setup` to register it with supported agents. The setup command handles Claude Code, Codex, Cursor, Windsurf, VS Code, and Cline configurations without replacing existing `swebsy` entries.

Yes, swebsy/MCP works with Cursor through its MCP configuration. Add an `swebsy` server entry that runs `npx -y @swebsy/mcp`, then restart Cursor and pair the server with an open Swebsy Studio tab.

Ask the agent to run `swebsy_start_pairing`; the server opens a pairing link and returns the link, code, and relay port. Open the link in the browser containing Studio, then keep that tab open while the agent uses the `swebsy_*` tools.

Yes, multiple agents can share one paired Studio tab when their servers use the same `SWEBSY_AGENT_PORT`. The local broker serializes editor commands and routes each result, screenshot, or export to the agent that requested it.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSwebsy MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/swebsy-mcp?style=directory)](https://allmcps.com/mcp/swebsy-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/swebsy-mcp"><img src="https://allmcps.com/api/badge/swebsy-mcp?style=directory" alt="Swebsy MCP on AllMCPs" /></a>