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