MCP Server Settings

The MCP Server tab of Settings lets AI agents - Claude Code, Cursor, Codex, or any other client of the Model Context Protocol - query LogRaker directly: list your streams, read their live output, search scrollback, check connection health, and read LogRaker's own diagnostic log.

The server is off by default. When enabled, it listens on this Mac only (the loopback address 127.0.0.1) - nothing is exposed to your network - and every request must present the access token shown on this tab.

Enabling the server

Turn on Enable MCP server. The status line below shows Running on 127.0.0.1:<port> once the server is listening; it starts automatically with LogRaker from then on, and stops the moment you turn the switch off.

Port is where the server listens (1024-65535). If another program already uses the port, the status line says so - pick a different one and LogRaker restarts the server automatically.

The token

LogRaker generates a random access token the first time you use this tab. It is shown masked; Copy Token puts the real value on the clipboard. Regenerate… mints a fresh token - agents configured with the old one stop working until you reconnect them.

Connecting an agent

Pick your agent - Claude Code, Cursor, Codex, Gemini CLI, or GitHub Copilot - and the tab shows a ready-made registration snippet with your current port and token filled in. The snippet is masked on screen; the Copy button puts the real one on the clipboard.

Claude Code - Copy Command gives a claude mcp add command. Paste it into Terminal and run it once; it registers LogRaker for all your projects.
Cursor - Copy Snippet gives a JSON fragment. Merge it into ~/.cursor/mcp.json (create the file if it doesn't exist), or into a project's .cursor/mcp.json to scope it to that project. Cursor's own Settings ▸ MCP screen edits the same file.
Codex - Copy Snippet gives a TOML fragment. Add it to ~/.codex/config.toml.
Gemini CLI - Copy Command gives a gemini mcp add command. Paste it into Terminal and run it once; it registers LogRaker for all your projects.
GitHub Copilot - Copy Snippet gives a JSON fragment for VS Code. Merge it into your user-level MCP configuration (Command Palette ▸ MCP: Open User Configuration) or a project's .vscode/mcp.json. Copilot calls MCP tools in agent mode.

Agents read their configuration when a session starts, so LogRaker should be running before you start the agent - if it wasn't, launch LogRaker and reconnect (in Claude Code, type /mcp and choose reconnect) or restart the agent's session.

Other MCP-capable agents work too: any client that supports streamable HTTP can use the same URL with an Authorization: Bearer header carrying the token.

Once connected, an agent can call these tools:

list_streams - every configured stream with its id, source, file, live status, and buffered line count.
read_tail - the last lines of a stream's buffer, exactly what the detail pane shows (including connection marker lines).
search_logs - search a stream's scrollback by substring or regular expression, with line numbers.
get_stream_status - one stream's connection state in detail: status, activity, lines and bytes received, start time, host and file.
read_diagnostic_log - the tail of LogRaker's own internal log, for troubleshooting LogRaker itself.

All tools are read-only - an agent can observe your streams but cannot start, stop, or change anything. Several agents can be connected at the same time, each with its own session.

Privacy

Log lines can contain sensitive information, which is why the server is off by default, answers only on this Mac, and requires the token even locally. The token and port stay on this Mac - they are not included in saved configurations and do not sync via iCloud.