Skip to content
Agentmart
Submit a tool

swebsy/mcp

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

Connector by swebsy · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)Remote (HTTP)
Write a review

Chalk Labs

Need help deploying swebsy/mcp?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/swebsy-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://mcp.swebsy.com/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
15 read · 18 write · 6 delete · 9 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 48

Read from the source code; the running server may list different tools.

Read 15 · Look things up without changing anything.

  • clarify_scope
  • get_skill
  • lookup_classes
  • read_page
  • swebsy_capture
  • swebsy_get_builder_guide
  • swebsy_list_assets
  • swebsy_list_blocks
  • swebsy_list_pages
  • swebsy_list_sites
  • swebsy_list_skills
  • swebsy_list_symbols
Show 3 more tools
  • swebsy_list_templates
  • swebsy_read_selection
  • swebsy_status

Write 18 · Create, change, send or run things.

  • add_section
  • animate_page
  • commit_design_direction
  • create_page
  • edit_section
  • insert_block
  • move_section
  • replace_page_content
  • swebsy_add_symbol_instance
  • swebsy_create_site
  • swebsy_detach_symbol
  • swebsy_rename_site
Show 6 more tools
  • swebsy_rename_symbol
  • swebsy_select_page
  • swebsy_start_pairing
  • swebsy_upload_asset
  • update_page
  • update_settings

Delete 6 · Delete, drop, revoke or wipe things.

  • delete_page
  • delete_section
  • swebsy_delete_asset
  • swebsy_delete_symbol
  • swebsy_mark_block
  • swebsy_undo

Not yet classified 9 · We could not tell from the name and description.

  • duplicate_page
  • duplicate_section
  • link_page
  • swebsy_export
  • swebsy_export_template
  • swebsy_open_site
  • swebsy_promote_to_symbol
  • swebsy_redo
  • wrap_section

Secrets and settings it asks for

Other settings (environment variables or headers).

  • SWEBSY_AGENT_DIR
  • SWEBSY_AGENT_PORT
  • SWEBSY_APP_URL
  • SWEBSY_NO_OPEN

Network hosts it talks to 1

  • mcp.swebsy.com · found in remote endpoint, install command

Files it touches

  • Any path the agent passes to its tools

Tools (48)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • add_section

    Insert a new section into the current page. Use for adding discrete sections (hero, features, pricing, CTA) to an existing page. Appends to the end by default; to place it somewhere specific, pass `position` plus the `targetPath` of the component to place it next to.

  • animate_page

    Apply Swebsy's built-in scroll-reveal animation in one step — a smart, per-section staggered entrance on headings, text, images, buttons, and cards (navbars/footers skipped). Prefer this over hand-placing animate-* classes whenever the user asks to animate the page or site, or wants a consistent reveal.

  • clarify_scope

    Ask the user to choose between an element-scoped change and a theme-wide change before acting. ALWAYS call this first when the scope is ambiguous.

  • commit_design_direction

    Commit this site to a specific visual direction, and apply it (fonts, type roles, palette swatches). Call this ONCE, BEFORE generating a new site's first page — a site with no committed direction has nothing for later edits to stay consistent with, and the result drifts to generic. Prefer a `directionId` from the sampled menu; supply the `custom` fields only when the user's brief clearly calls for something the menu doesn't cover. Not needed when editing a site that already has a direction.

  • create_page

    Create a NEW blank page in the project and (by default) select it. Returns the new page's id and fileName. The page starts nearly empty — fill it with `replace_page_content` or `add_section`, and point a navbar/link at it with `link_page`. Use THIS to add an additional page; use `replace_page_content` (NOT this) to overwrite the current page's content.

  • delete_page

    Delete a page. The home page (index) and a site's last page can't be deleted. Links to the deleted page are left in place — repoint them with `link_page` or delete them.

  • delete_section

    Remove a component from the current page entirely. Use this instead of emptying a section's contents — an emptied section leaves a stray blank div on the page. Deletes the selected component by default; pass `targetPath` (from `read_page`) to delete a component you did not select.

  • duplicate_page

    Copy a page (content, classes and styles) into a new page and select the copy. Returns the new page's id and fileName. Use it to start a page from an existing layout instead of rebuilding it.

  • duplicate_section

    Copy a component (with its classes and styles) and insert the copy right after it. Paths after it shift by one — call `read_page` before the next path-based edit.

  • edit_section

    Modify an existing component. By default this edits the selected component. To edit a component identified by `read_page`, provide its `targetPath`; an explicit path overrides the canvas selection. Preferred: provide `component` — the full replacement component tree (compact DSL OK), best for structural changes. Alternative: provide `html` — the complete modified HTML string. Fallback: provide `patch` — JSON Patch (RFC 6902) for tiny single-property tweaks. Supply exactly one. Preserve existing IDs: an id kept in the edit keeps the styles attached to it; an id you drop loses them.

  • get_skill

    Load deep, on-demand guidance for a specific area before acting on it (e.g. before adding animations, composing a new page, writing copy, building forms, editing the nav, or reusing components with symbols). Returns the full instructions for that skill.

  • insert_block

    Insert a pre-built block from the catalog and optionally customize its content. STRONGLY preferred over generating from scratch when a matching block exists. The block re-themes on insert — its colour and font classes resolve against THIS site's theme, so the result is meant to differ from the catalog thumbnail (a screenshot of the block in the template it came from).

  • link_page

    Point an existing link at a project page — the same wiring the UI's 'Link to' picker does. Pass the link's `targetPath` (from `read_page`) and the target `page` (id or name). For a navbar link this sets its page target so the href and active state stay in sync; for a plain link or button it sets href to the page's ./slug.html. Use after `create_page` to wire a navbar to the new page.

  • lookup_classes

    Retrieve the full list of preset component classes for a given family (e.g., 'btn', 'card', 'navbar', 'semantic', 'animation'). Use when you need to choose among specific variants.

  • move_section

    Move a component to just before or after another component on the current page — reorder sections, swap columns, lift a CTA above the footer. The component keeps its id, classes and id-styles. ALWAYS use this to reorder; delete + re-add loses the component's styles.

Show 33 more tools
  • read_page

    Read the current page structure and addressable component target paths. Call this BEFORE editing a named or relative page component that is not the current selection. The default `sections` read lists every top-level section with its target path — enough to pick the one to edit. When copying content between components, use `detail: full` WITH the `targetPath` of the one section you're copying, not a whole-page read. Also call it AFTER applying edits to verify the result.

  • replace_page_content

    Replace ALL top-level sections of the CURRENTLY SELECTED page with a generated list of components. This OVERWRITES the page — it does NOT create a new page (use `create_page`) and does NOT append a single section (use `add_section`). Use when the user asks to build/replace/redesign an entire page. Each top-level component should be wrapped in a container.

  • swebsy_add_symbol_instance

    Add a linked INSTANCE of an existing symbol (see list_symbols) to the CURRENT page. The instance stays in sync with the symbol main and every other instance — the way to reuse one navbar/footer/CTA across pages. Select the target page with select_page first.

  • swebsy_capture

    Capture a styled screenshot of the current page at a fixed viewport, written under .swebsy-agent/screenshots/. Returns the file path. Scope it with `targetPath` when verifying ONE section — a whole-page PNG downscales so far that component detail is unreadable.

  • swebsy_create_site

    Create a site and open it in Studio. Pass name to set its internal Studio/Home name (default "My Website"). Omit templateId for Swebsy's standard blank site; provide an installed template ID to import that template unchanged. Then poll swebsy_status until editorReady is true and siteId matches before editing.

  • swebsy_delete_asset

    Delete one managed asset from the open site's asset gallery. By default this refuses assets referenced by any page, shared symbol, style, or site setting; call swebsy_list_assets first. force:true also clears live component references and should be used only when that is explicitly intended.

  • swebsy_delete_symbol

    Delete a symbol. Every instance is DETACHED first and stays on its page as a plain component — nothing disappears from the site. To also remove the copies, delete_section them.

  • swebsy_detach_symbol

    Turn ONE symbol instance on the current page back into a plain component, so it can be edited on its own. The symbol and its other instances stay linked. Use it when one page needs a variant of the shared navbar/footer.

  • swebsy_export

    Export the site to .swebsy-agent/exports/. Static files via the site exporter and/or the project JSON (with assets). Returns `outDir`, the exported page paths, and per-kind file counts — verify a build by grepping those HTML files.

  • swebsy_export_template

    DEV-ONLY template authoring: export the open site as a template into the local content catalog. This installs the template (meta, project.json, static preview, thumbnail), harvests every component marked via swebsy_mark_block into the block catalog (light+dark thumbnails included), and rebuilds both catalogs. Requires the local content server (pnpm -F @swebsy/content run dev). Passing an existing `id` replaces that template; omitting `id` re-exports to the template this site was last exported as (or derives an id from `name`). Returns { id, blocksHarvested }.

  • swebsy_get_builder_guide

    Load the static Swebsy builder guidance (component system, theme classes, conventions) that the in-app AI Builder is primed with.

  • swebsy_list_assets

    List managed assets in the open site with whole-project usage counts. References are checked across every page, shared symbols, styles, and site settings. Use imagesOnly:true and unusedOnly:true before deleting unused gallery images.

  • swebsy_list_blocks

    List the pre-built block catalog (ids + labels) available to insert_block.

  • swebsy_list_pages

    List the project's pages (id, name, fileName, section count, which one is selected). Call this instead of guessing a page name for select_page or link_page.

  • swebsy_list_sites

    List saved sites newest-first as metadata only: IDs, internal names, status, timestamps, template ID, page count, and whether each site is open.

  • swebsy_list_skills

    List the available deep-guidance skills (animation, page-composition, copywriting, forms, nav) with one-line summaries.

  • swebsy_list_symbols

    List the project's SYMBOLS (reusable components that stay in sync across every page). Returns each symbol's id, name, component type, instance count, and how many pages use it, plus a `health` report of BROKEN linkage: `orphans` (copies whose main was deleted — editing them changes nothing elsewhere), `unregistered` (instances the main doesn't list back, so edits propagate one way only) and `ghosts`. Repair any of it by calling promote_to_symbol on one affected section. Use before add_symbol_instance to find the symbol id.

  • swebsy_list_templates

    Refresh and list installed site templates with names, descriptions, tags, fonts, preview URLs, and thumbnail URLs. Works from Home or Studio.

  • swebsy_mark_block

    DEV-ONLY template authoring: mark the component at `targetPath` (from read_page) as a harvestable block, or update/remove its annotation. Marked sections become catalog blocks when the template is exported (see swebsy_export_template). Selection rule: mark the smallest meaningful designed composition, not an atomic content element. Never mark a lone image, video, heading, paragraph, divider, spacer, or a wrapper whose only meaningful child is one of those. A valid block combines at least two complementary content/layout elements (for example image + copy, heading + CTA, or label + stats), or i…

  • swebsy_open_site

    Open a saved site by ID in the paired tab and return its metadata. Idempotent if it is already open. Poll swebsy_status for the expected siteId and editorReady before editing.

  • swebsy_promote_to_symbol

    Promote an existing component into a reusable SYMBOL so it can be shared, in sync, across pages. Pass its `targetPath` from read_page (e.g. the navbar or the CTA band). Also REPAIRS broken linkage (see list_symbols → health): re-promoting an orphaned copy rebuilds its main and re-links every other copy of it, and re-promoting a symbol registers instances it had lost. Returns the symbol id (for add_symbol_instance) and a `repaired` count; copies whose structure has diverged too far are reported as `detached` — delete_section + add_symbol_instance those instead.

  • swebsy_read_selection

    Read the currently selected component (type, classes, attributes, text). Secrets are never surfaced.

  • swebsy_redo

    Re-apply tool calls reverted by swebsy_undo, oldest-undone last. Cleared by any new edit.

  • swebsy_rename_site

    Rename a saved site's internal Studio/Home name. This does not change its SEO or public title settings.

  • swebsy_rename_symbol

    Rename a symbol (the name shown in the Symbols panel).

  • swebsy_select_page

    Select a page in the connected Studio project.

  • swebsy_start_pairing

    Start a pairing session. Returns a single-use `pairUrl` — give it to the user to click; opening it connects their Studio tab automatically. (Also returns the raw `code`/`port` for manual entry.)

  • swebsy_status

    Report bridge status, siteName, selected page, and editorReady, plus a short theme summary (fonts, default color mode, brand colors). After creating or opening a site, wait until editorReady is true and siteId matches the expected site before editing.

  • swebsy_undo

    Revert your own last editing tool call(s) this session (add/edit/delete/move/duplicate_section, insert_block, update_settings, page tools…), newest first. Does NOT undo symbol or asset tools. Refuses (returns `blocked`) when a page, CSS or settings it would restore has been edited since, so hand edits are never overwritten. Paths may shift — call read_page afterwards.

  • swebsy_upload_asset

    Upload a local image, font, video, audio or PDF file into the open site and return its `assetId`, `src` and a `usage` snippet. Images go in the asset library for `image` components, video for `video` components (`attributes.src`), audio for `audio`, PDFs as a link `href`; fonts are stored for `update_settings` fonts.custom. This is the ONLY way to get your own imagery (screenshots, logos, textures, mockups) into a site — an `image` with an empty src gets a random stock photo instead. Reads the file from the agent's own filesystem, so pass a path you can see (for example a screenshot you just c…

  • update_page

    Rename a page and/or change its URL slug — the Pages panel's rename. Links that pointed at the old `./slug.html` on every page follow the new slug. The home page's `index` slug is locked (its display name can still change).

  • update_settings

    Update site settings — SEO title/description, site URL, structured data (JSON-LD), per-page SEO overrides, language/direction, theme tokens (light + dark), type scale, animation defaults, Google and uploaded fonts, dark mode toggle, site-wide custom CSS for component-level restyling (globalTheme.customTailwindConfig), favicon, robots.txt/sitemap/service worker/security headers/image optimization (performance), analytics ids, custom head/body code (advanced), the "Made with Swebsy" badge (branding) and the deploy target (deploy). Provide ONLY the fields that change. `general`/`seo` are SITE-WID…

  • wrap_section

    Wrap a run of sibling components in one new element, optionally with a semantic tag — e.g. put everything between the navbar and footer in `<main>`, or a footer symbol in `<footer>`. The wrapped components keep their ids, id-styles and symbol links. ALWAYS use this to add a wrapper; re-sending the components through `edit_section`/`replace_page_content` loses their styles. Paths shift — call `read_page` before the next path-based edit.

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Oct 24, 2026 (6 days ago)
Last release
Oct 19, 2026 (11 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.swebsy/mcp
Version
0.12.1
Auth
Auth not stated
Packages
npm @swebsy/mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get swebsy/mcp running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying swebsy/mcp?

CallGet help
Cite this page

swebsy/mcp. Agent Mart. https://agentmart.dev/connectors/swebsy-mcp (last updated 2026-10-24)