starter_2 — TokenOS Token Launch Planner MCP Prompt
starter_2
is one of 4 prompts on the
TokenOS Token Launch Planner
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 Token Launch Planner Prompt/starter_2 run in your project directory
- Claude Desktop TokenOS Token Launch Planner Prompt/starter_2 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenOS Token Launch Planner Prompt/starter_2 ~/.cursor/mcp.json
- VS Code TokenOS Token Launch Planner Prompt/starter_2 .vscode/mcp.json
- Zed TokenOS Token Launch Planner Prompt/starter_2 ~/.config/zed/settings.json
- Windsurf TokenOS Token Launch Planner Prompt/starter_2 ~/.codeium/windsurf/mcp_config.json
- Cline TokenOS Token Launch Planner Prompt/starter_2 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenOS Token Launch Planner Prompt/starter_2 ~/.gemini/settings.json
- Grok TokenOS Token Launch Planner Prompt/starter_2 .mcp.json (in your project root)
- ChatGPT TokenOS Token Launch Planner Prompt/starter_2 Settings → Connectors → Advanced → Developer mode
- Claude.ai TokenOS Token Launch Planner Prompt/starter_2 Settings → Connectors → Add custom connector
- LangChain TokenOS Token Launch Planner 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.