get_playbook — Buzz Dealer AI MCP Tool Read-only
get_playbook
(get playbook) is one of 31 tools on the
Buzz Dealer AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_playbook from your client
- Claude Code Buzz Dealer AI get_playbook run in your project directory
- Claude Desktop Buzz Dealer AI get_playbook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Buzz Dealer AI get_playbook ~/.cursor/mcp.json
- VS Code Buzz Dealer AI get_playbook .vscode/mcp.json
- Zed Buzz Dealer AI get_playbook ~/.config/zed/settings.json
- Windsurf Buzz Dealer AI get_playbook ~/.codeium/windsurf/mcp_config.json
- Cline Buzz Dealer AI get_playbook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Buzz Dealer AI get_playbook ~/.gemini/settings.json
- Grok Buzz Dealer AI get_playbook .mcp.json (in your project root)
- ChatGPT Buzz Dealer AI get_playbook Settings → Connectors → Advanced → Developer mode
- Claude.ai Buzz Dealer AI get_playbook Settings → Connectors → Add custom connector
- LangChain Buzz Dealer AI get_playbook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.buzzdealer.ai/mcpOther tools on this server
- find_publications
- get_publication
- plan_campaign
- get_ai_visibility_score
- check_company_presence
- check_originality_and_fit
- quote_order
- place_order
- get_order_status
- cancel_order
- respond_to_replacement
- get_report
- order_audit
- get_account_status
- get_linked_account
- contact_support
- start_radar
- get_radar_status
- get_questions
- answer_question
- set_preferences
- get_gaps
- start_fix
- mark_fix_done
- get_progress
- what_changed
- check_request
- rate_fix
- get_reputation_profile
- update_reputation_profile
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.