mobius-studio-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mobius-studio-mcp Build a site from this brief: a bakery in Berlin."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mobius-mcp
The Mobius Studio MCP server for Sweipe and FlatMobile sites. On npm as mobius-studio-mcp.
An MCP server that lets an AI agent (Claude Code, Claude Desktop, Cursor, any MCP client) set up a WordPress site running the Sweipe or FlatMobile theme: import a demo, plan and build a site from a one-paragraph brief, rewrite the copy of existing pages, review the result, change core settings.
It talks to the theme plugin's sweipe/v1/agent REST surface (Companion 1.2.1+) with a
WordPress Application Password. The AI itself runs on the theme's service and is paid
for by the site's licence in monthly credits; no API key is needed anywhere.
Setup
On the site, as an administrator: Users → Profile → Application Passwords, add one named
mcp, copy the password.Make sure the theme licence is activated (Sweipe → License) and AI is on (Sweipe → AI).
Add the server to your client.
Claude Code:
claude mcp add sweipe -e SWEIPE_SITE_URL=https://example.com -e SWEIPE_USER=admin -e SWEIPE_APP_PASSWORD="xxxx xxxx xxxx xxxx xxxx xxxx" -- npx -y mobius-studio-mcpClaude Desktop / Cursor (mcpServers entry):
{
"sweipe": {
"command": "npx",
"args": ["-y", "mobius-studio-mcp"],
"env": {
"SWEIPE_SITE_URL": "https://example.com",
"SWEIPE_USER": "admin",
"SWEIPE_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}Application Passwords need HTTPS; on a local http:// site add
add_filter( 'wp_is_application_passwords_available', '__return_true' ); to a
must-use plugin.
Works for FlatMobile sites too: the server reads the site's REST index and picks
sweipe/v1 or flatmobile/v1 on its own (SWEIPE_NAMESPACE overrides).
Optional: SWEIPE_IMPORT_BUDGET (seconds the server spends per import step, default
25, max 55; lower it if your host kills long requests).
Related MCP server: WordPress MCP Server
Tools
Tool | What it does | Credits |
| Theme, plugin, licence, AI state, where the site plan stands | 0 |
| The demo packages and a waiting import | 0 |
| Service check + credit balance | 0 |
| Templates a site can be planned from | 0 |
| Brief → plan (pages and sections) | 1 |
| The stored plan | 0 |
| Plan → pages with copy and photos, imported | 4 |
| Render, inspect, screenshot, judge; corrected plan | 5 (fix: 2, free when clean) |
| Plan, build, review, rebuild, fix in one call | ~12 |
| Rewrite the copy of existing pages, with backups | 1 per page |
| Which demos fit a brief | 0 |
| AI features on/off | 0 |
| Core title, tagline, timezone, language, front page | 0 |
SKILL.md is a plain-English skill file for agents: when to use which tool, what to
check first, what to ask the owner before spending credits.
The REST surface behind it
Everything the server does is a call to https://example.com/wp-json/sweipe/v1/agent/…
with Basic auth; the routes are listed at the top of the plugin's
plugin/Services/Ai/AgentApi.php. Any script can use them directly:
curl -u 'admin:xxxx xxxx xxxx xxxx xxxx xxxx' https://example.com/wp-json/sweipe/v1/agent/status
curl -u '…' -H 'Content-Type: application/json' -d '{"brief":"…","language":"English"}' https://example.com/wp-json/sweipe/v1/agent/ai/planDevelopment
npm install
npm run build
SWEIPE_SITE_URL=http://localhost:8081 SWEIPE_USER=admin SWEIPE_APP_PASSWORD=… node dist/index.jsMIT © Mobius Studio
Available Tools
20 toolssweipe_ai_buildBuild the planned siteA
Assemble the plan into pages with copy written from the brief and stock photos, then import it into the site and wait for the import to finish. Costs 4 credits. Pass plan to build an edited plan; omit it to build the stored one.
Inputs: plan, import.
sweipe_ai_get_planCurrent site planB
The stored site plan (pages and their sections), the brief it came from, and when it was built and reviewed.
Inputs: include_sections.
sweipe_ai_librarySite templatesA
The templates a site can be planned from (slug, name, what the design looks like, required plugins). Pass a slug as base to sweipe_ai_plan, or let the planner pick.
Inputs: no named parameters.
sweipe_ai_pingAI service checkA
Round trip to the Sweipe AI service: confirms the licence is accepted and returns the credit balance (included monthly credits, used, left, reset date).
Inputs: no named parameters.
sweipe_ai_planPlan a site from a briefA
Turn a one-paragraph business brief into a site plan: pages, and for each page an ordered list of sections chosen from the template library. Costs 1 credit. Review the plan (edit page titles, slugs, add or drop sections) before sweipe_ai_build.
Inputs: brief (required), base, language.
sweipe_ai_reviewReview the built siteA
Render every built page, inspect it (empty sections, broken images, missing pages), take phone and desktop screenshots, and have the service judge the result against the brief. Returns a score out of 10, a summary, the changes made to the plan and whether the plan changed. If changed is true, call sweipe_ai_build again, then review with mode "fix". Full review costs 5 credits, fix 2 (free when nothing is broken).
Inputs: mode.
sweipe_ai_set_enabledTurn AI features on or offA
Switch the AI features of the plugin on or off for this site (Sweipe → AI).
Inputs: enabled (required).
sweipe_brief_applyApply drafted copyA
Write the stored drafts into the pages, keeping a backup for sweipe_brief_undo. Pass items to apply an edited or partial set of rows per page instead of the whole draft.
Inputs: post_ids (required), items.
sweipe_brief_generateDraft copy for a pageA
Rewrite every text on one page (or the site identity, post_id 0) for the business in the brief, keeping the layout. Returns the draft rows (id, widget, old, new) and stores them; nothing changes on the site until sweipe_brief_apply. 1 credit per page.
Inputs: brief (required), post_id (required), language.
sweipe_brief_pagesPages with editable copyA
Every page, post and the site identity block (id 0: title, tagline, menus) with how many text items each holds, whether a draft is waiting, and whether AI copy has already been applied. Use the ids with sweipe_brief_generate / apply / undo.
Inputs: no named parameters.
sweipe_brief_pickWhich demos fit a briefB
Ask the service which demo packages fit the business brief, with a reason each. Free. Also stores the brief for later copy generation.
Inputs: brief (required), language.
sweipe_brief_undoUndo applied copyA
Restore the pre-apply backup of the given pages (all backed-up pages when post_ids is empty).
Inputs: post_ids.
sweipe_import_demoImport a demoA
Import one of the demo packages into the site and wait for it to finish (pages, menus, images, settings; products when WooCommerce is active). Existing user pages are never overwritten. Takes one to a few minutes.
Inputs: slug (required).
sweipe_import_statusImport progressA
Progress of a running or finished import by its import_id.
Inputs: import_id (required).
sweipe_list_demosList demo packagesA
The ready-made demo sites this licence can import (slug, name, description, category, required plugins). Use sweipe_import_demo with a slug.
Inputs: refresh.
sweipe_site_from_briefSite from brief (plan, build, review, rebuild)A
The whole loop in one call: plan from the brief, build and import, full review, and if the review changed the plan, rebuild and run a fix review. About 12 credits and 3–8 minutes. Use the individual tools when the plan should be edited by hand first.
Inputs: brief (required), base, review, language.
sweipe_statusSite statusA
What this WordPress install is (theme, plugin, Elementor, WooCommerce), whether the licence is active, whether AI is enabled and configured, and where the AI site plan stands (planned, built, reviewed). Call this first.
Inputs: no named parameters.
wp_get_settingsSite settingsA
Core WordPress settings (site title, tagline, timezone, language, front page) via wp/v2/settings.
Inputs: no named parameters.
wp_list_pagesList pagesA
Published and draft pages with id, title, slug, link and status, for picking front pages and checking an import.
Inputs: search, per_page.
wp_update_settingsUpdate site settingsA
Change core WordPress settings: title, description (tagline), timezone (e.g. "Europe/Istanbul"), language (e.g. "tr_TR"), show_on_front ("page"|"posts"), page_on_front, page_for_posts.
Inputs: title, language, timezone, date_format, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 20 tools
Most tools target distinct actions or resources: status checks, demo import, AI planning, and brief copy are clearly separated. A few boundaries could still trip an agent, such as sweipe_status vs sweipe_import_status or sweipe_list_demos vs sweipe_ai_library, but the descriptions provide enough to disambiguate.
The names consistently use snake_case and a sweipe_ prefix, with wp_ used for the WordPress core tools. There are minor structural deviations like sweipe_site_from_brief and sweipe_brief_pages where the noun/phrase form replaces the usual verb_noun pattern, but the overall scheme is predictable.
Twenty tools is on the heavy side for a single server, and the 16-25 range makes it feel sprawling. That said, the functions are grouped into distinct workflows (demos, AI site building, brief copy), so the count is defensible even if it could be consolidated.
The server covers the full Sweipe lifecycle: licensing/status, demo import, AI plan/build/review, one-shot brief-to-site, and the copy brief workflow with undo. Minor gaps exist, such as no direct arbitrary page editing or delete/cancel operations, but the core workflows are complete and have no dead ends.
Maintenance
Related MCP Connectors
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Let your AI agent build, preview and update web apps, download source and publish when you allow it.
Generate GEO/AEO-optimized articles and publish them to WordPress from your AI agent.
AI agent website builder. Create and publish link-in-bio sites via MCP or REST API.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage WordPress sites with 190+ tools for content management, theme/plugin customization, file system operations, WooCommerce, and complete site control through natural language.10028 npm55MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI models like Claude to manage WordPress sites through the WordPress REST API, supporting operations like post creation, taxonomy management, and site configuration. It features secure authentication via Application Passwords and provides tools for comprehensive content administration.1MIT
- AlicenseNot gradedqualityDmaintenanceConnects WordPress sites to AI agents, enabling content management through natural language commands via the WordPress REST API.21 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-