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