starter_2 — TokenOS dApp Builder MCP Prompt
starter_2
is one of 4 prompts on the
TokenOS dApp Builder
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke starter_2 from your client
- Claude Code TokenOS dApp Builder Prompt/starter_2 run in your project directory
- Claude Desktop TokenOS dApp Builder Prompt/starter_2 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenOS dApp Builder Prompt/starter_2 ~/.cursor/mcp.json
- VS Code TokenOS dApp Builder Prompt/starter_2 .vscode/mcp.json
- Zed TokenOS dApp Builder Prompt/starter_2 ~/.config/zed/settings.json
- Windsurf TokenOS dApp Builder Prompt/starter_2 ~/.codeium/windsurf/mcp_config.json
- Cline TokenOS dApp Builder Prompt/starter_2 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenOS dApp Builder Prompt/starter_2 ~/.gemini/settings.json
- Grok TokenOS dApp Builder Prompt/starter_2 .mcp.json (in your project root)
- ChatGPT TokenOS dApp Builder Prompt/starter_2 Settings → Connectors → Advanced → Developer mode
- Claude.ai TokenOS dApp Builder Prompt/starter_2 Settings → Connectors → Add custom connector
- LangChain TokenOS dApp Builder Prompt/starter_2 pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.