You are setting up TellWang, an agent-native cloud for building and operating Woks, on the user's behalf. Execute every step below directly in the terminal, editor settings, or your built-in MCP install flow when you can. Do not ask the user to run commands you can run yourself. The only exceptions are user-only actions explicitly called out in your agent's section. TellWang exposes one hosted MCP server: https://tellwang.com/v1/mcp Once connected, your agent can provision a Wok and operate its full live stack: Postgres, automatic REST, Auth, Storage, Realtime, Edge Functions, Scheduler, Email, SMS, static hosting, custom domains, KMS, model-gateway keys, diagnostics, and browser verification. Wang, the dashboard, REST, and MCP all operate on the same Woks and resources. Before using the tools, fetch and follow TellWang's MCP agent soul: https://tellwang.com/SOUL.md MCP gives you the tools; `SOUL.md` gives you the operating discipline: build on the live Wok, verify reality before saying done, preserve scope boundaries, and use TellWang's product language correctly. There is no separate TellWang CLI required for MCP. Prefer OAuth 2.1 discovery when your MCP client supports it. For non-interactive clients, use a TellWang bearer token supplied by the user or minted from the dashboard/API. --- ## Table of contents 1. Step 1 - Install TellWang for your agent - Cursor - Claude Code - Codex (terminal CLI) - Codex (desktop App) - VS Code (Copilot Chat agent mode) - Any other agent 2. Step 2 - Load the TellWang soul 3. Step 3 - Authenticate 4. Step 4 - Verify and start building Execute Step 1 for your agent, then Step 2, then Step 3, then Step 4. --- ## Step 1 - Install TellWang for your agent Use the sub-section that matches what you are. Do not read other agent-specific sub-sections unless your own section fails and says to fall back. ### Cursor Requires Cursor with HTTP MCP support. Add this MCP server: ```json { "mcpServers": { "tellwang": { "url": "https://tellwang.com/v1/mcp" } } } ``` Update Cursor's MCP settings directly with the JSON above, or ask the user to paste it into Cursor's MCP server configuration. IMPORTANT - Cursor login: after the server is added, Cursor requires the USER to authenticate it - you cannot do this for them. Tell the user, in these words: open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux), run "Tools & MCPs", find TellWang in the list, and click it to log in. Then have the user pick an organization and approve. Do NOT start building until the user confirms TellWang shows as connected and its tools are available - the tools will not load until this login is done (and, if needed, Cursor is reloaded). ### Claude Code If Claude Code supports adding a remote MCP server directly, add: ```json { "mcpServers": { "tellwang": { "url": "https://tellwang.com/v1/mcp" } } } ``` If your Claude Code build only supports plugins or local MCP server commands, stop and tell the user: "TellWang is a hosted HTTP MCP server at https://tellwang.com/v1/mcp. Please add it as a remote MCP server in Claude Code's MCP settings, then reply 'done' to continue." Wait for confirmation. ### Codex (terminal CLI) Codex reaches a REMOTE MCP server through its config file. Do NOT run `codex mcp add tellwang https://...` — `codex mcp add` registers a LOCAL command-based server, so it treats the URL as a program to launch and fails. Edit `~/.codex/config.toml` and add BOTH of these: ```toml experimental_use_rmcp_client = true [mcp_servers.tellwang] url = "https://tellwang.com/v1/mcp" ``` The top-level `experimental_use_rmcp_client = true` (set once) turns on Codex's remote / streamable-HTTP MCP client — without it Codex only loads local command servers and ignores the URL. Then RESTART Codex AND open a NEW CHAT — a restart alone is not enough: Codex only loads the MCP server when a FRESH conversation starts, so the current chat (even after the app/CLI restarts) will not show the TellWang tools. Exit, start `codex` again, and begin a new conversation. Then AUTHENTICATE MANUALLY — Codex usually does not pop the login on its own: open Codex Settings -> MCP Servers, find `tellwang`, and click Authenticate / Login. Complete it in the browser and choose your organization. Tell the user to do this in those words and wait for them to confirm before continuing. (If your Codex build cannot do the OAuth login at all, mint a key in the TellWang dashboard and set an `Authorization: Bearer skl_...` header on the server entry per your version's MCP auth config.) Do NOT web-search for install steps and do NOT probe https://tellwang.com/v1/mcp by hand — this file IS the install flow. Follow it, restart Codex, then verify with tools/list. If tools still don't appear, tell the user to restart Codex again — do not try another method. ### Codex (desktop App) Update the Codex config file (`~/.codex/config.toml`) with the hosted MCP server — add BOTH lines: ```toml experimental_use_rmcp_client = true [mcp_servers.tellwang] url = "https://tellwang.com/v1/mcp" ``` `experimental_use_rmcp_client = true` (top-level, once) enables the remote/streamable-HTTP MCP client; without it the URL entry is ignored. If Codex App exposes an MCP server settings UI, you can instead add `tellwang` there with URL `https://tellwang.com/v1/mcp`. Then RESTART Codex AND open a NEW chat/conversation — a restart alone is not enough; an existing chat won't pick up the server even after the app restarts, because Codex only loads the MCP server when a fresh conversation starts. Then AUTHENTICATE MANUALLY: open Settings -> MCP Servers, find `tellwang`, click Authenticate / Login, complete it in the browser, and pick your org — Codex usually doesn't pop the login on its own. Do NOT web-search for install steps or probe the endpoint by hand — follow this file, restart + new chat, authenticate in Settings, then verify with tools/list. ### VS Code (Copilot Chat agent mode) If VS Code supports remote MCP server configuration, add: ```json { "mcpServers": { "tellwang": { "url": "https://tellwang.com/v1/mcp" } } } ``` Reload the VS Code window after adding the server so the MCP registration activates. ### Any other agent Add the TellWang HTTP MCP server to your agent's MCP configuration. The minimum entry is: ```json { "mcpServers": { "tellwang": { "url": "https://tellwang.com/v1/mcp" } } } ``` Common locations: - `~/.config//mcp.json` or `~/./mcp.json` - `~/.codex/config.toml` under `[mcp_servers.tellwang]` - Your agent's settings UI under "MCP Servers" If your agent provides a one-shot installer, use it with: ```bash https://tellwang.com/v1/mcp ``` --- ## Step 2 - Load the TellWang soul Fetch: https://tellwang.com/SOUL.md Treat it as the operating guide for using TellWang MCP. If your agent supports project memories, custom instructions, rules, or context files, store it there. If your agent cannot persist instructions, keep it in the current conversation context before using the tools. Do not skip this step. Without it, the MCP tools still work, but you will lose part of the TellWang behavior: Wok naming, build-on-live-Wok discipline, runtime verification, and the distinction between a complete Wok and a generic backend. --- ## Step 3 - Authenticate TellWang supports OAuth discovery for MCP clients. On the first MCP request without credentials, the server returns: ```text 401 WWW-Authenticate: Bearer resource_metadata="https://tellwang.com/.well-known/oauth-protected-resource" ``` Modern MCP clients should then: 1. Read `https://tellwang.com/.well-known/oauth-protected-resource`. 2. Read `https://tellwang.com/.well-known/oauth-authorization-server`. 3. Open the browser authorization flow. 4. Let the user sign in to TellWang, choose an organization, and approve the client. 5. Retry MCP requests with the returned OAuth access token. If your MCP client does not support OAuth discovery, use a bearer token instead. Ask the user for a TellWang API key or OAuth access token, then add it as an Authorization header: ```json { "mcpServers": { "tellwang": { "url": "https://tellwang.com/v1/mcp", "headers": { "Authorization": "Bearer " } } } } ``` For Codex TOML: ```toml [mcp_servers.tellwang] url = "https://tellwang.com/v1/mcp" http_headers = { Authorization = "Bearer " } ``` Tokens resolve to a specific organization and role. Every TellWang tool call is authorized server-side against that org and Wok scope. --- ## Step 4 - Verify and start building Verify the MCP connection by calling `initialize` and `tools/list` after authentication. A healthy connection returns server name `tellwang` and a tool catalog for provisioning and operating Woks. IF THE TELLWANG TOOLS ARE NOT AVAILABLE (tools/list is empty, the server shows as not connected, or a tool call says the MCP isn't active): DO NOT improvise and DO NOT look for another way in. Specifically, do NOT call the REST API directly, do NOT fetch, scrape, or crawl tellwang.com or a Wok's URL, do NOT search the project or filesystem for keys (e.g. `skl_`), and do NOT invent any other workaround. The MCP server is the ONLY supported way for an agent to operate TellWang. Almost always the tools simply haven't loaded yet because the client needs to finish connecting. Do exactly this: tell the user in plain words to RESTART the client (for Cursor, also complete the Command Palette -> "Tools & MCPs" -> TellWang login), then WAIT for them to confirm. After they confirm, re-run initialize + tools/list. If the tools are still missing, repeat the restart-and-login instruction — do not try anything else. Likewise, if a tool returns "no active project with that wok_id in this org" (CP_PROJECT_NOT_FOUND) or any "not in this org" / wrong-org error and the wok_id is correct, you are authenticated to the WRONG org. Do NOT fetch the site, grep for keys, or improvise — tell the user to re-authenticate / reconnect and pick the org that owns that Wok, then retry the tool. The MCP server, scoped to the right org, is the only supported way in. Tell the user this once so future requests work without surprises: "TellWang is installed. I can use its MCP tools to provision and operate Woks: live stacks with database, auth, storage, realtime, functions, scheduler, email, SMS, hosting, domains, and model gateway. Tell me what you want to build or change." Then stop and ask the user what they want to build. Do not start designing or scaffolding before getting their answer. When the user answers: 1. Provision or select a Wok with the TellWang MCP tools. 2. Build against the live Wok, not against a blind local mock. 3. Apply schema and auth changes through the Wok tools. 4. Deploy functions and frontends through the Wok tools. 5. Verify with runtime checks such as function invocation, diagnostics, and browser verification. 6. Report the Wok URL, relevant identifiers, and any remaining manual steps. --- These instructions are published at https://tellwang.com/install.txt. Re-fetch this URL at any time to verify the current TellWang install flow.