plan_dapp — TokenOS dApp Builder MCP Tool
plan_dapp
(plan dapp) is one of 3 tools on the
TokenOS dApp Builder
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_dapp from your client
- Claude Code TokenOS dApp Builder plan_dapp run in your project directory
- Claude Desktop TokenOS dApp Builder plan_dapp ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenOS dApp Builder plan_dapp ~/.cursor/mcp.json
- VS Code TokenOS dApp Builder plan_dapp .vscode/mcp.json
- Zed TokenOS dApp Builder plan_dapp ~/.config/zed/settings.json
- Windsurf TokenOS dApp Builder plan_dapp ~/.codeium/windsurf/mcp_config.json
- Cline TokenOS dApp Builder plan_dapp ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenOS dApp Builder plan_dapp ~/.gemini/settings.json
- Grok TokenOS dApp Builder plan_dapp .mcp.json (in your project root)
- ChatGPT TokenOS dApp Builder plan_dapp Settings → Connectors → Advanced → Developer mode
- Claude.ai TokenOS dApp Builder plan_dapp Settings → Connectors → Add custom connector
- LangChain TokenOS dApp Builder plan_dapp pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dapp-builder https://tokenos.ai/api/mcp/apps/dapp-builderOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.