MonstarX Cursor plugin

Ship real full-stack apps from Cursor and Grok Bot — live preview, built-in backend, admin CMS, REST APIs, and one-click publish — via MonstarX's MCP endpoint.

What is MonstarX?

MonstarX is an AI app builder for shipping real web apps, not mockups. You describe an app in plain words; MonstarX plans it, writes the code, runs a live preview, tests it in real browsers, and publishes to *.monstarx.app or your own domain. The code is yours — export anytime or sync to GitHub.

Product UI is available in 16 languages (EN, JA, ZH-CN, PT-BR, AR, KO, TH, ID, VI, MS, HI, BN, TA, RU, SW, HA) — switch in account settings. Pricing is country-based.

Under the hood every project is a full-stack app on TanStack Start + React + TypeScript, with a database, sign-in, email, file storage, and AI from day one. Import from Lovable, GitHub, a zip, or push from coding agents (Cursor, Claude Code, Codex, and this plugin).

Same Lovable-class “describe it → see it running” feel — with the stack and ops surface to actually launch: Cloud backend, Admin back office, partner REST APIs, QA in real browsers, and publish.

• Product: monstarx.com
• Docs: What is MonstarX?
• Agents: Connect coding agents

Why MonstarX vs “prompt → UI only” builders

UI generators stop at screens. MonstarX ships the rest:

MonstarX Cloud

Every app gets a built-in backend — no servers to rent, no keys pasted into source. Explore it at mxcloud.monstarx.com and in docs under MonstarX Cloud.

• Database — bookings, orders, posts, sign-ups; browse and query from the Workbench Backend tab
• User accounts — sign-up, sign-in, password reset for your app’s users
• Email — confirmations and notices from the app’s own address
• File storage — photos and documents people upload
• AI — text, summaries, images, and more inside the app, with no API keys in code
• Maps — world and street maps without a separate key
• Secrets — encrypted keys for third-party services

Same backend in preview and production. Workbench Backend browses DB, users, files, emails, and AI usage; Admin covers day-to-day ops. Need Stripe, Twilio, or your own CRM? Connectors keep those accounts yours; custom/third-party APIs go through connectors + mx.api.call (keys held by MonstarX, not in the repo).

Admin panel / CMS + REST APIs

Admin ships on every project by default — not an add-on. Edit data as forms, manage users (ban, reset password, app admin), and use Activity + Undo. Optional Admin Studio adds saved views, forms, and dashboards (including AI-assisted pages). See The Admin panel.

Admin → APIs turns tables into REST endpoints (list / get / create / update / delete), publishes docs + OpenAPI, and issues project API keys — so partners and automations talk to your data without you writing a backend. See Your app’s REST API.

Grok Bot + MonstarX harmony

This plugin connects Cursor’s agent and Grok Bot to MonstarX (via Cursor Marketplace plugins) without hand-rolling mcp.json.

• Think → ship — Grok Bot scopes product, UX, and copy; Cursor implements; push to MonstarX for a live preview and shareable link.
• Round-trip builds — Iterate in the MonstarX workbench; pull latest into the agent, merge, push again.
• Ask MonstarX to build — “Add Stripe checkout” or auth via send_message; MonstarX builds in the workbench, then pull those changes.
• Publish and secrets from the agent — Publish when ready; set_secrets keeps keys out of chat.
• Mixed team — Non-dev teammates iterate in MonstarX while you stay in Cursor / Grok Bot; revision checks stop either side from overwriting the other.

Example prompts

Once connected, try:

• “Push this app to MonstarX and give me the link.”
• “Push my changes to MonstarX.”
• “Pull the latest version from MonstarX and merge it with my changes.”
• “Ask MonstarX to add Stripe checkout, then pull its changes.”
• “Publish it on MonstarX.”
• “Create a booking app on MonstarX with sign-in and confirmation emails.”
• “Import github.com/me/my-app into MonstarX.”
• “What is MonstarX doing on my project?”

MCP tools

Every tool acts only on projects you own. Publishing always asks first. Endpoint: https://monstarx.com/mcp.

Install

Cursor Marketplace

1. Install MonstarX from the Cursor Marketplace (once listed), or add this repo as a plugin source.
2. Open Settings → MCP, find monstarx, and use Sign in.
3. In the browser, sign in to MonstarX and press Allow.
4. Say: “Push this app to MonstarX and give me the link.”

Local plugin test

For maintainers / local testing before Marketplace listing:

mkdir -p ~/.cursor/plugins/local
git clone https://github.com/monstarx-tech/monstarx-cursor-plugin.git ~/.cursor/plugins/local/monstarx

Restart Cursor (or reload plugins), then Sign in under Settings → MCP as above.

Validate the package locally:

node scripts/validate-plugin.mjs

Manual OAuth setup (mcp.json)

If you are not using the marketplace package yet, add to ~/.cursor/mcp.json:

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

Then sign in from Settings → MCP (or agent mcp login monstarx in Cursor’s CLI agent).

This matches the official MonstarX Cursor snippet. For Cursor Marketplace installs this repo ships the same url-only shape in mcp.cursor.json (pinned from .cursor-plugin/plugin.json). Root mcp.json uses the Agent Plugins shape (type: streamable-http) for OpenAI ChatGPT/Codex — see OpenAI Plugins / Dots below. Do not put type: streamable-http in Cursor's own ~/.cursor/mcp.json; Cursor's CLI can drop the whole file when that type is present.

API key for CI / headless

Browser sign-in is preferred for interactive Cursor use. For CI, scripts, or agents that cannot open a browser:

1. Create a key in MonstarX Settings → API & MCP under API keys.
2. Configure MCP with a Bearer header (do not commit the key):

{
  "mcpServers": {
    "monstarx": {
      "url": "https://monstarx.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

API keys act as you on every project. Keep them out of chats and source control. Revoke unused keys in Settings. The marketplace install path stays OAuth-only so Cursor’s Sign in button works without an empty Bearer token.

Security

• .env files are not uploaded. The push command leaves them out; if one arrives anyway, MonstarX does not store it.
• Put secrets in Backend → Secrets, or ask your agent to use set_secrets.
• Never paste API keys into chat or commit them to the repo.

Support

• Docs: Connect coding agents
• Product: monstarx.com · Cloud: mxcloud.monstarx.com
• In product: Ask Luna
• Email: feedback@monstarx.com

OpenAI Plugins / Dots

This repo is also packaged as a portable Agent Plugins folder for ChatGPT and Codex. Dots reuse the same plugin packages. It's prepared for the OpenAI Plugins Directory but not submitted yet.

Validate and build the upload ZIP:

node scripts/validate-plugin.mjs            # Cursor + OpenAI checks (warns while the demo URL is empty)
node scripts/validate-plugin.mjs --release  # also requires review.demo_recording_url
node scripts/build-openai-zip.mjs           # → dist/monstarx-openai-plugin-<version>.zip

Still to do before Submit for review: record the demo and set review.demo_recording_url, add explicit destructiveHint values on the server's read-only tools, host the domain-challenge token, and set up a reviewer account with no MFA. See the checklist. Reviewer credentials go only in the portal, never in the ZIP.

Listing URLs: Privacy Policy · Terms of Service · Help and support (email: support@monstarx.com) · monstarx.com.

Marketplace submit (maintainers)

This plugin is prepared for the Cursor Marketplace but is not claimed as listed yet. When ready:

1. Confirm node scripts/validate-plugin.mjs passes.
2. Tag a release / note version in .cursor-plugin/plugin.json.
3. Submit the public repo at cursor.com/marketplace/publish.
4. Wait for Cursor’s manual review.

License

MIT © 2026 MonstarX / monstarx-tech