scenario — VibeCodePicks MCP Tool
scenario
(scenario) is one of 16 tools on the
VibeCodePicks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scenario from your client
- Claude Code VibeCodePicks scenario run in your project directory
- Claude Desktop VibeCodePicks scenario ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VibeCodePicks scenario ~/.cursor/mcp.json
- VS Code VibeCodePicks scenario .vscode/mcp.json
- Zed VibeCodePicks scenario ~/.config/zed/settings.json
- Windsurf VibeCodePicks scenario ~/.codeium/windsurf/mcp_config.json
- Cline VibeCodePicks scenario ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VibeCodePicks scenario ~/.gemini/settings.json
- Grok VibeCodePicks scenario .mcp.json (in your project root)
- ChatGPT VibeCodePicks scenario Settings → Connectors → Advanced → Developer mode
- Claude.ai VibeCodePicks scenario Settings → Connectors → Add custom connector
- LangChain VibeCodePicks scenario pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vibecodepicks https://vibecodepicks.com/api/mcp/Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.