find_server — r4ck MCP Prompt
find_server
is one of 1 prompt on the
r4ck
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find_server from your client
- Claude Code r4ck Prompt/find_server run in your project directory
- Claude Desktop r4ck Prompt/find_server ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor r4ck Prompt/find_server ~/.cursor/mcp.json
- VS Code r4ck Prompt/find_server .vscode/mcp.json
- Zed r4ck Prompt/find_server ~/.config/zed/settings.json
- Windsurf r4ck Prompt/find_server ~/.codeium/windsurf/mcp_config.json
- Cline r4ck Prompt/find_server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI r4ck Prompt/find_server ~/.gemini/settings.json
- Grok r4ck Prompt/find_server .mcp.json (in your project root)
- ChatGPT r4ck Prompt/find_server Settings → Connectors → Advanced → Developer mode
- Claude.ai r4ck Prompt/find_server Settings → Connectors → Add custom connector
- LangChain r4ck Prompt/find_server pip install langchain-mcp-adapters
r4ck 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 11 November 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.