simulate_failures — Mockbird MCP Prompt

simulate_failures is one of 5 prompts on the Mockbird MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke simulate_failures from your client

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

Other prompts on this server

• mock_an_api
• mock_from_spec
• monitor_uptime
• is_it_down

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