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