PM Lab Platform

Build and deploy prototypes from Cursor IDE — no engineering support needed.

PM Lab lets Product Managers go from idea to live web app by talking to Cursor's AI. It handles all the infrastructure: GitHub repos, Vercel deployments, databases, and authentication.

For PMs: Get started

If your engineering team has already set up PM Lab, you just need Cursor and a URL.

Getting Started Guide for PMs — everything you need to create your first prototype.

Connect the MCP server

Claude Code:

claude mcp add pm-lab --transport http https://pm-mcp-server.vercel.app/api/mcp

Cursor: Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pm-lab": {
      "url": "https://pm-mcp-server.vercel.app/api/mcp"
    }
  }
}

Then restart your client, open the AI chat, and say: "Create a new prototype called my-idea"

What you can ask Cursor

What you want	What to say
Create a prototype	"Create a new prototype called feedback-board"
Add a new page	"Add a /settings page with a form to update the app name and description"
Add a feature	"Add the ability to filter items by status using a dropdown"
Change the design	"Make the header dark blue with white text and add a logo placeholder"
See your prototypes	"List my prototypes"
Deploy changes	"Commit and push my changes"

Every prototype comes with user authentication, a database, and a live URL out of the box.

For Engineers: Set up PM Lab

Admin Setup Guide — provision Supabase, Vercel, and GitHub, deploy the remote MCP server, then share the URL with your team.

How it works

PM opens Cursor → says "create a new prototype called X"
  → Remote MCP server creates GitHub repo from template
  → MCP server creates Vercel project with env vars
  → MCP server creates a Postgres schema for the project
  → MCP server triggers first deployment via Vercel API
  → MCP server returns the clone URL
  → PM clones the repo and builds features with Cursor's AI
  → PM pushes to main → Vercel auto-deploys

The MCP server runs as a Next.js app deployed on Vercel. PMs connect to it over Streamable HTTP — no local server process, no secrets on their machines. Authentication is handled via Sign In with Vercel (OAuth).

Repository structure

pm-lab-platform/
├── apps/
│   ├── mcp-server/             # Remote MCP server (Next.js, deployed to Vercel)
│   └── template/               # Standalone Next.js prototype template
├── packages/
│   ├── typescript-config/
│   └── eslint-config/
├── scripts/
│   └── push-template.sh
└── docs/

Quick commands

pnpm install          # Install dependencies
pnpm build            # Build everything
pnpm type-check       # Type-check everything
pnpm lint             # Lint everything
pnpm build:mcp        # Build the MCP server
pnpm build:template   # Build the template app

Documentation

Doc	Audience	What it covers
Getting Started	PMs	Connecting to the MCP server, creating prototypes, building features
Admin Setup	Engineers	Infrastructure setup, deploying the remote MCP server, PM onboarding
MCP Server	Engineers	Server architecture, tools, OAuth, configuration, extending
Template App	Engineers	App structure, auth, database, Cursor rules
Development	Engineers	Monorepo workflow, building, testing, adding packages