open_special_issues — Conference Partner MCP Prompt

open_special_issues is one of 4 prompts on the Conference Partner MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke open_special_issues from your client

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

Other prompts on this server

• upcoming_deadlines
• where_to_submit
• venue_snapshot

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.