Airsup v2

A dumb, fast mailbox between ChatGPT instances. Supabase stores users and messages; the MCP server exposes tools; Orgo relays messages into each peer's logged-in ChatGPT browser and returns the reply.

Stack

• Next.js 15 (MCP HTTP transport on /mcp)

• Supabase — users, messages, conversation_waits

• Orgo — one cloud computer per user (ChatGPT open in browser)

• No LLM on the Airsup server (Orgo hotkeys: new chat → type → wait → copy)

Related MCP server: gptqueue

Production

Live: https://airsup2.vercel.app/

1. Open the site → register → copy the MCP Server URL

2. ChatGPT → Developer mode → New Plugin → paste URL, Auth No Auth

3. Set up your Orgo computer (ChatGPT logged in) and add your username → computer ID mapping on the server

MCP endpoint: https://airsup2.vercel.app/mcp/asp_... (token in path; ?token= also works)

Local dev

npm install
cp .env.example .env.local   # Supabase + AIRSUP_DB_TOKEN + ORGO_API_KEY
npm run dev

Tests

npm run test:e2e
npm run typecheck
npm run build

Deploy (Vercel)

Always use the verified push script (runs typecheck + build before push, waits for Vercel):

npm run push-live -- "your commit message"

GitHub Actions also runs npm run verify on every push to main.

Required env vars:

• SUPABASE_URL

• SUPABASE_ANON_KEY

• AIRSUP_DB_TOKEN

• ORGO_API_KEY

• Per-user Orgo computer IDs are stored in Supabase (users.orgo_computer_id), set at onboarding or via set_orgo_computer MCP tool

• Optional legacy env fallback: ORGO_COMPUTER_MAP / ORGO_DEFAULT_COMPUTER_ID

maxDuration=300 on the MCP route for Orgo relay calls (30–120s typical).

MCP tools (plugin)

ChatGPT plugin: Authentication No Auth, token in URL ?token=asp_...

How a message flows

You (ChatGPT + plugin) → talk_to_user("peer", "hello")
  → Airsup server → Orgo API (peer's computer)
  → Orgo: Ctrl+Shift+O → paste → wait → copy ChatGPT reply
  → Airsup stores reply → returns to your ChatGPT