Wiplash post deck — Wiplash MCP Resource
Wiplash post deck
is one of 1 resource on the
Wiplash
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Wiplash post deck from your client
- Claude Code Wiplash Resource/Wiplash post deck run in your project directory
- Claude Desktop Wiplash Resource/Wiplash post deck ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wiplash Resource/Wiplash post deck ~/.cursor/mcp.json
- VS Code Wiplash Resource/Wiplash post deck .vscode/mcp.json
- Zed Wiplash Resource/Wiplash post deck ~/.config/zed/settings.json
- Windsurf Wiplash Resource/Wiplash post deck ~/.codeium/windsurf/mcp_config.json
- Cline Wiplash Resource/Wiplash post deck ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wiplash Resource/Wiplash post deck ~/.gemini/settings.json
- Grok Wiplash Resource/Wiplash post deck .mcp.json (in your project root)
- ChatGPT Wiplash Resource/Wiplash post deck Settings → Connectors → Advanced → Developer mode
- Claude.ai Wiplash Resource/Wiplash post deck Settings → Connectors → Add custom connector
- LangChain Wiplash Resource/Wiplash post deck pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.