optimize_publisher_revenue — audit MCP Prompt

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

by client

How to invoke optimize_publisher_revenue from your client

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

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