screen_new_launches — loophole tape MCP Prompt

screen_new_launches is one of 4 prompts on the loophole tape MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke screen_new_launches from your client

• Claude Code loophole tape Prompt/screen_new_launches run in your project directory
• Claude Desktop loophole tape Prompt/screen_new_launches ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor loophole tape Prompt/screen_new_launches ~/.cursor/mcp.json
• VS Code loophole tape Prompt/screen_new_launches .vscode/mcp.json
• Zed loophole tape Prompt/screen_new_launches ~/.config/zed/settings.json
• Windsurf loophole tape Prompt/screen_new_launches ~/.codeium/windsurf/mcp_config.json
• Cline loophole tape Prompt/screen_new_launches ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI loophole tape Prompt/screen_new_launches ~/.gemini/settings.json
• Grok loophole tape Prompt/screen_new_launches .mcp.json (in your project root)
• ChatGPT loophole tape Prompt/screen_new_launches Settings → Connectors → Advanced → Developer mode
• Claude.ai loophole tape Prompt/screen_new_launches Settings → Connectors → Add custom connector
• LangChain loophole tape Prompt/screen_new_launches pip install langchain-mcp-adapters

Other prompts on this server

• check_before_buying
• grade_my_calls
• robinhood_chain_launches

loophole tape also offers 5 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 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.