gigs_tonight — electron.dance MCP Prompt

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

by client

How to invoke gigs_tonight from your client

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

electron.dance 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.