TellWang
Dashboard

Quickstart

Tell Wang what your business needs and Wang provisions a Wok — the full stack your software runs on, from database through hosting, built and operated for you. You own what comes out: the features, the code, the looks. Ask Wang in chat, or point your IDE at the TellWang MCP server.

New here? You don't need to choose a framework or configure infrastructure. A Wok is a complete stack; you build against it from any client.

Tell Wang

In the TellWang app, Slack, Telegram, or Chat in the dashboard, describe what you want. Chats belong to your organization, so one conversation can plan a new Wok or work across several existing Woks. Add teammates under People in this chat to turn one into a private group conversation with clear speaker names. You can optionally choose a focused Wok as the starting point without locking the chat to it. Every current plan has its own OpenCode Agent Cell: isolated workers code, run, and verify directly from the dashboard with no local setup. Free includes one concurrent Wang run and DeepSeek Flash; paid plans add DeepSeek Pro, Kimi, and higher limits.

you → Wang
Create a Wok for a support inbox: tickets table
(id, subject, status, created_at), email login, and a
nightly job that emails me open-ticket counts.

Wang creates the Wok, applies the schema, enables auth, deploys the scheduled function, and hands back a live URL.

Drive it from your IDE

Point Cursor or Claude Code at the TellWang MCP server. Your agent provisions, queries, and deploys directly — same Wok, full control. For the full connection flow, see MCP server.

~/.cursor/mcp.json
{
  "mcpServers": {
    "tellwang": {
      "url": "https://tellwang.com/v1/mcp"
    }
  }
}

Then describe what you want — your IDE picks the right MCP tools.

you → Cursor
Provision a Wok for a support inbox: tickets table
(id, subject, status, created_at), email login, and a
nightly job that emails me open-ticket counts.

Or do it by hand

Rather click than ask? Sign in at tellwang.com/dashboard. The left rail keeps organization-wide chats separate from your Woks. Start a chat without choosing an app, or add a focused Wok from the conversation header when it helps. To work a Wok by hand, open it from the Woks list and use its panels directly. It is the same control plane Wang and your IDE drive:

Make your first query

A Wok speaks the Supabase API, so @supabase/supabase-js works against it unmodified — point it at your Wok's URL and anon key:

app.ts
import { createClient } from "@supabase/supabase-js";
const tw = createClient("https://<wok-id>.tellwang.com", anonKey);

const { data, error } = await tw
  .from("tickets")
  .insert({ subject: "Login fails on SSO", status: "open" });
The same client handles auth, storage, realtime, and functions against your Wok, not just the database — it's the full Supabase API.