records_search — legal mcp server MCP Prompt

records_search is one of 1 prompt on the legal mcp server MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke records_search from your client

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

legal mcp server also offers 1 resource — 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.