Jiayang Cloud

Cursor

Deploy what Cursor builds, privately

Updated

Install the jiayang CLI, run jiayang mcp install cursor in your project, and ask Cursor to deploy it. The app goes live at its own address that only the people you share it with can open, and everything Cursor did is in the audit log under your name. Our plugin isn't in the Cursor Marketplace yet, so you add the server with that one command.

Set it up

First install the CLI and sign in. Then, in the project's folder:

jiayang login
jiayang mcp install cursor

This writes the project's .cursor/mcp.json, naming jiayang by its full path. Cursor opened from the Dock or the Start menu doesn't see the PATH your terminal has, so a config that names plain jiayang can fail with the server shown as not available.

Run it from a jiayang you've installed, not through npx. npx keeps it in a cache it clears, so the command refuses.

Then open the project in Cursor, or run Developer: Reload Window if it's open, and turn on jiayang-cloud under Customize, MCP if it isn't on. Pasting the config into the chat doesn't add the server. It has to be in the file.

The file holds a path on your computer, with your username in it, so think about that before you commit it.

For a whole team

On Cursor's Teams or Enterprise plan, an admin can add our plugin for everyone: Dashboard, Plugins & MCPs, Add Marketplace, Import from Repo, with https://github.com/ss2d22/jiayang. The plugin adds skills that tell Cursor how to deploy, share, import an app and more. Each person still needs the CLI installed and signed in.

Ask Cursor to ship it

For example: "Deploy this directory to Jiayang Cloud as acme/hello and tell me the URL." Then "Share it with sam@example.com as a viewer." Cursor works as you, with your permissions and no credential of its own. It can't open an app to the internet, add people to your workspace, sign in, pay or read a secret's value. See the agent guide for every tool.

If Cursor says the server isn't available

Cursor can't start jiayang mcp. In order:

  1. In a terminal, jiayang whoami shows the CLI is installed and signed in. If it isn't installed, install it.
  2. Run jiayang mcp install cursor in the project again, so the config has the full path.
  3. Quit Cursor and open it again, so it reads the config afresh.
  4. Check the server is turned on under Customize, MCP. Its log is in the Output panel under MCP Logs.

More in Troubleshooting.

Who can open it

Only the people you share it with: any email address, everyone at your company's domain, or a group. Viewers sign in with a code sent to their address, or with Google or Microsoft, and don't need an account first. Remove someone and they lose access within 60 seconds. Your app gets a signed token saying who is calling, which our SDKs check in one call.

Connect Cursor to an MCP server you deployed

An MCP server deployed here sits behind the same sign-in. Once AI clients are turned on for it, add its address to .cursor/mcp.json:

{
  "mcpServers": {
    "tools": { "url": "https://tools--acme.jiayang-apps.cloud/mcp" }
  }
}

Cursor opens a browser to sign in and approve it, and then reaches that one app as you. It signs in through an address on your own computer, so a Cursor version that offers only its cursor:// address can't connect: update Cursor. See MCP servers behind sign-in.

Questions

Is it free?

Free covers three apps and three people, with no card, for JavaScript, TypeScript and static apps. A Python server, or any other app that runs as a container, needs Team or above. See pricing.

I keep my session in another config directory. Does Cursor find it?

Yes, if you set it before you run the command. With JIAYANG_CONFIG_DIR, XDG_CONFIG_HOME or --config-dir set, jiayang mcp install cursor writes that directory into the file too, and says which of them it came from.

Next