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