publish_log — docbin MCP Prompt
publish_log
is one of 4 prompts on the
docbin
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke publish_log from your client
- Claude Code docbin Prompt/publish_log run in your project directory
- Claude Desktop docbin Prompt/publish_log ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor docbin Prompt/publish_log ~/.cursor/mcp.json
- VS Code docbin Prompt/publish_log .vscode/mcp.json
- Zed docbin Prompt/publish_log ~/.config/zed/settings.json
- Windsurf docbin Prompt/publish_log ~/.codeium/windsurf/mcp_config.json
- Cline docbin Prompt/publish_log ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI docbin Prompt/publish_log ~/.gemini/settings.json
- Grok docbin Prompt/publish_log .mcp.json (in your project root)
- ChatGPT docbin Prompt/publish_log Settings → Connectors → Advanced → Developer mode
- Claude.ai docbin Prompt/publish_log Settings → Connectors → Add custom connector
- LangChain docbin Prompt/publish_log pip install langchain-mcp-adapters
Other prompts on this server
docbin 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.