write_submission — ClusterHack MCP Prompt

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

by client

How to invoke write_submission from your client

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

Other prompts on this server

• set_up_event
• find_a_team

ClusterHack also offers 1 resource — 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.