TellWang
Dashboard
Develop / MCP server

TellWang MCP server

Connect Cursor, Claude Code, or another MCP-native agent to TellWang at https://tellwang.com/v1/mcp. The agent can provision Woks, run SQL, deploy functions, publish frontends, connect domains, inspect inboxes, search org knowledge, and verify work through the same control plane Wang uses.

✦
A Wok is the resource your agent works on: one live stack with Postgres, REST, auth, storage, realtime, edge functions, scheduler, email, SMS, hosting, domains, a model gateway, and KMS.

Endpoint

MCP endpoint
https://tellwang.com/v1/mcp

The server speaks JSON-RPC over Streamable HTTP. It advertises tools through tools/list and executes them through tools/call. The mint_llm_key tool advertises the exact model ids technical builders can use: private, deepseek-v4-flash, deepseek-v4-pro, and paid-plan kimi-k2.7-code.

Cursor config

Use OAuth when your client supports MCP authorization. For non-interactive agents, use an organization-scoped TellWang bearer token.

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

Authentication discovery

MCP clients discover TellWang authorization from the standard metadata endpoints:

If a client sends a request without credentials, TellWang returns a 401 with a WWW-Authenticate challenge pointing at the protected-resource metadata. Ordinary MCP clients select one organization and receive an organization-bound access token. lollipop login can authorize every current membership in one consent; it stores one independently scoped token pair per organization and switches locally with lollipop org <slug>. Every request enforces the same server-side permissions as REST and the dashboard.

The dashboard's Connected clients panel lists the coding clients authorized by the current user. Disabling one revokes that user's access and refresh tokens for the client in the current organization; the client must complete sign-in again before it can reconnect.

What agents can do

The dashboard keeps the original task entry points for Create app, Edit app, GEO, Domain, Email, Marketing email, MCP server, and Generate image. It also provides focused prompts for enterprise RAG, edge functions, automations, and read-only diagnosis. Each selection changes the example and the generated instructions so the coding agent receives constraints that fit the work.

Build your own MCP server

Open Build with an agent in the dashboard and choose MCP server. Select the Wok, describe the tools and access policy, then paste the generated prompt into a connected Claude Code, Codex, Cursor, or other MCP client. The agent builds a customer-owned Streamable HTTP endpoint and tests the complete client handshake before returning its URL and connection snippet.

The default server uses scoped bearer API keys whose raw values are shown only at creation. Public read-only tools and an existing OAuth provider are supported when the requested data and identity setup fit those models. Authorization stays inside every tool handler, Wok secrets remain server-side, and Wang does not put live credentials in chat.

Machine-readable discovery

Agents can also read: