submit_feedback — VoteShip MCP Prompt

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

by client

How to invoke submit_feedback from your client

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

VoteShip 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.