Deploy a Claude Code project

Claude Code writes the app; what it can't conjure out of a terminal is somewhere for the app to live — a database, logins, file storage, a URL other people can open. Connect the TellWang MCP server and the same session that wrote the code gets all of that as tools. The agent provisions a Wok, creates the schema, publishes the frontend, and checks the live result. Everything below applies to Cursor and other MCP clients too.

1. Add the MCP server

In Claude Code:

claude mcp add --transport http tellwang https://tellwang.com/v1/mcp

Then run /mcp inside Claude Code to sign in — TellWang publishes standard OAuth metadata, so the browser handoff is automatic. In Cursor:

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

Non-interactive agents can skip OAuth and send an organization-scoped bearer token instead — details on the MCP server page.

2. Ask for the backend in the same session

You don't call the tools by hand; you ask for outcomes and the agent picks them up:

Provision a Wok for this project. Create tables for customers and
orders with row-level security so each signed-in user only sees
their own rows. Wire this frontend to it, deploy it, and verify
the live URL actually works.

Behind that one prompt the agent calls tools like provision_wok, exec_sql, and deploy_frontend, and it can finish with a real browser check of the deployed URL — console and network errors included, not just a 200.

3. What the wiring looks like

A Wok speaks the Supabase API, so the agent connects your frontend with @supabase/supabase-js pointed at the Wok's URL and anon key:

import { createClient } from "@supabase/supabase-js";
const db = createClient(WOK_URL, WOK_ANON_KEY);

The same client covers auth, storage, realtime, and functions — the quickstart has the full walk-through, and GET /v1/woks/{id}/connection returns every value the client needs.

4. Put it on your domain

The deployed frontend gets its own <wok-id>.tellwang.com URL immediately; attaching your own domain — DNS verification, TLS, routing — is one more ask in the same session. See Hosting & Domains.

If the agent wants to read for itself

TellWang publishes machine-readable references the agent can fetch mid-session: https://tellwang.com/llms.txt for the short version, https://tellwang.com/install.txt for setup, and https://tellwang.com/SOUL.md for build conventions. Pointing a stuck agent at llms.txt usually unsticks it.

Common questions