find_performer_schedule — SofiaStage Events MCP Prompt

find_performer_schedule is one of 3 prompts on the SofiaStage Events MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke find_performer_schedule from your client

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

Other prompts on this server

• discover_upcoming_events
• explore_event_details

SofiaStage Events 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.