A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · tcgunel/mobius-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository tcgunel/mobius-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
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 1. On the site, as an administrator: **Users → Profile → Application Passwords**, add one named mcp, copy the password. 2. Make sure the theme licence is activated (**Sweipe → License**) and AI is on (**Sweipe → AI**). 3. Add the server to your client. Claude Code: Claude Desktop / Cursor (mcpServers entry): 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). Tools | Tool | What it does | Credits | | --- | --- | --- | | sweipe_status | Theme, plugin, licence, AI state, where the site plan stands | 0 | | sweipe_list_demos / sweipe_import_demo / sweipe_import_status | The demo packages and a waiting import | 0 | | sweipe_ai_ping | Service check + credit balance | 0 | | sweipe_ai_library | Templates a site can be planned from | 0 | | sweipe_ai_plan | Brief → plan (pages and sections) | 1 | | sweipe_ai_get_plan | The stored plan | 0 | | sweipe_ai_build | Plan → pages with copy and photos, imported | 4 | | sweipe_ai_review | Render, inspect, screenshot, judge; corrected plan | 5 (fix: 2, free when clean) | | sweipe_site_from_brief | Plan, build, review, rebuild, fix in one call | ~12 | | sweipe_brief_pages / sweipe_brief_generate / sweipe_brief_apply / sweipe_brief_undo | Rewrite the copy of existing pages, with backups | 1 per page | | sweipe_brief_pick | Which demos fit a brief | 0 |