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