play_tidelight — Tidelight MCP Prompt

play_tidelight is one of 1 prompt on the Tidelight MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke play_tidelight from your client

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

Tidelight also offers 2 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.