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, and a model gateway.

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.

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:

https://tellwang.com/.well-known/oauth-protected-resource
https://tellwang.com/.well-known/oauth-authorization-server

If a client sends a request without credentials, TellWang returns a 401 with a WWW-Authenticate challenge pointing at the protected-resource metadata. After OAuth, the access token resolves to the selected organization and enforces the same server-side permissions as REST and the dashboard.

What agents can do

Provision a new Wok and get its URL and keys.
Build tables, policies, edge functions, scheduled jobs, and hosted frontends.
Operate domains, email, SMS, credits, model-gateway keys, and KMS resources.
Verify by invoking functions, checking the browser surface, reading diagnostics, and searching org knowledge.

Machine-readable discovery

Agents can also read:

https://tellwang.com/install.txt
https://tellwang.com/SOUL.md
https://tellwang.com/llms.txt
https://tellwang.com/.well-known/mcp.json
https://tellwang.com/sitemap.xml
https://tellwang.com/robots.txt