PromptUI — Build. Verify. Launch. Grow. Operate.

Build and grow from the coding agent you already use

PromptUI connects to Codex, Claude Code, and Cursor through a shared tool standard (Model Context Protocol, or MCP). Your agent can ask PromptUI to build and publish an app, then use the same product context to draft marketing work, review the queue, publish an approved post, and read results. You stay in control: anything that spends credits or publishes outside your account requires explicit confirmation.

The MCP server exposes Builder, Launch and Growth tools. Operate runs in the PromptUI web app, not through this connector. Paid-ad creation, activation and spend are separate and are not exposed here either.

What your agent can do

Build and publish

  • build_app — start a PromptUI build
  • get_build_status — check progress and open the preview
  • list_builds — find your recent projects
  • deploy_app — publish a completed app after confirmation

Create and grow

  • gtm_generate_content — create and save a draft
  • gtm_list_content — review saved, approved, or scheduled work
  • gtm_publish_content — publish one approved item after confirmation
  • gtm_get_analytics — read current channel results

Growth tools follow the same access rules as the Growth Agent workspace. Drafting and listing your queue work on every plan. Images and reels use credits. Reading results and publishing an approved item to a connected channel need Grow or Growth Pro. Publishing always asks for confirmation first.

1. Get your API key

Sign in and copy your pui_ key from Dashboard → Settings. The key acts as your account: anything an agent builds or deploys with it uses your credits and shows up in your dashboard.

2. Connect your client

Claude Code

export PROMPTUI_API_KEY="pui_YOUR_KEY"
claude mcp add --transport http promptui https://www.promptui.co/api/mcp \
  --header "Authorization: Bearer ${PROMPTUI_API_KEY}"

Codex CLI

Set the key in your shell, then add this native remote-server entry to ~/.codex/config.toml:

export PROMPTUI_API_KEY="pui_YOUR_KEY"

[mcp_servers.promptui]
url = "https://www.promptui.co/api/mcp"
bearer_token_env_var = "PROMPTUI_API_KEY"

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "promptui": {
      "type": "http",
      "url": "https://www.promptui.co/api/mcp",
      "headers": { "Authorization": "Bearer pui_YOUR_KEY" }
    }
  }
}

What works today: the local Codex, Claude Code, and Cursor clients above. A one-click hosted connector inside ChatGPT or claude.ai is coming, and is not available yet.

3. Use it

"Build me a booking page for a yoga studio, then deploy it."

→ build_app { prompt: "a booking page for a yoga studio" }
→ confirm the credit-spending build action
→ get_build_status { buildId } … status: completed, previewUrl
→ confirm the public publishing action
→ deploy_app { buildId } → live URL

If the planner needs a clarification, get_build_status returns a link to answer it in the browser — the build resumes where it paused. Repos you export from PromptUI include this setup pre-wired: an AGENTS.md and .mcp.json so your agent can keep iterating on the app.

Pricing & limits

Your Codex or Claude subscription pays for the work done by that coding agent, subject to its own limits. PromptUI actions still follow your PromptUI plan and credit balance. A default build is 50 credits. A first publish is 25 credits, and updates to the same published app are free. Social-platform charges and advertising spend are separate and remain in the connected business's account. See pricing before you run a metered action.