post_bounty — xrpl referee MCP Prompt

post_bounty is one of 2 prompts on the xrpl referee MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke post_bounty from your client

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

Other prompts on this server

• find_work

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.