@mystack.co/mcp

MCP connector for mystack.co. Publish a website — or a built web app — to a live *.mystack.co URL from any MCP client (Claude Code, Claude Desktop, Cursor, etc.). Say "publish this to mystack" and it ships.

Setup

Get an API key (msk_live_…) from your mystack dashboard, then add the connector to your MCP client config:

{
  "mcpServers": {
    "mystack": {
      "command": "npx",
      "args": ["-y", "@mystack.co/mcp"],
      "env": { "MYSTACK_API_KEY": "msk_live_…" }
    }
  }
}

| Env var | Required | Default | |---|---|---| | MYSTACK_API_KEY | yes | — | | MYSTACK_API_URL | no | https://api.mystack.co |

The publish_static_site tool

Two modes:

• Static page — pass html (plus optional css / js). For a single hand-written page.
• Built app — pass directory, the path to a build output folder (dist, build, or out). The connector reads every file off disk and uploads it, so large bundles never have to pass through the model.

If the project is a framework app (React, Vite, Next.js static export, Svelte, Vue, Astro, …), build it first (npm run build) and publish the output directory — the tool description guides the agent to do exactly this.

Reusing the same projectName updates the existing site in place.

Remote (no-install) option

You can also connect over HTTP without installing anything — point your client at https://api.mystack.co/api/mcp with an Authorization: Bearer <key> header, or add the My Stack connector in claude.ai. The remote path can't read a local directory itself (no filesystem access), so for a built app it hands back a one-line mystack-push command (run via npx) that uploads the build folder from your machine with a short-lived, single-use token — large React/Vite builds publish without their file contents ever passing through the model.

License

MIT