Loggerhead

com.getloggerheadPublished by getloggerhead.comv1.12.0Updated Oct 27, 2026

Read the logs, metrics, and traces of the app you are editing, from the Loggerhead Mac app.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Bridges a coding agent to the Loggerhead Mac app so it can read your app's local OpenTelemetry logs, metrics and traces, and adjust telemetry lint rules.

What you can do
  • Search and read telemetry: query log records by text, severity and time, read time-series metrics, find traces and read every span of one trace.
  • Inspect setup: list workspaces and environments with receiver ports, report effective OTLP ports and send addresses, and read total counts of logs, metrics and spans.
  • Review telemetry lint: list findings such as noisy logs, unbounded labels, secrets and lost trace context, list lint rules with their state and thresholds, and read the last AI analysis findings.
  • Change lint configuration: enable or disable rules, set or reset thresholds, add or remove exceptions, ignore or unignore findings, and mark a finding fixed after a code change, each with a…
When to use it
Useful when you are editing an app on a Mac that already sends OpenTelemetry data to Loggerhead and you want the agent to ground debugging in real logs, metrics and traces, or to tune the telemetry lint rules that flag noisy or leaky instrumentation.
Requirements
The Loggerhead Mac app must be installed and running; the bridge exits when the app is not running. Runs as a local stdio process, installed via the .mcpb extension in Claude Desktop or by pointing a stdio client at the app's bundled binary. No port or API key is configured; the bridge finds the app on local loopback ports. Desktop only.
Before you install
Eight tools change state: seven alter a workspace's lint rules and one marks a finding fixed, each with a reason the user sees and can undo in the app. Telemetry read from the app is handed to the connected MCP client, so review what that client does with it. Data stays in a DuckDB file on your disk under the app's retention setting.

Installation

In SourceWeft

  1. Open Loggerhead in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Loggerhead MCP server

[M8ven Score]

Your coding agent reads your app's logs, metrics, and traces.

Loggerhead is a native Mac app that receives OpenTelemetry logs, metrics, and traces from the software you run on your own Mac, and stores them in a DuckDB file on your disk. The MCP server runs inside the app. This repository holds loggerhead-mcp, the small bridge that connects Claude, Cursor, Codex, Windsurf, or any other MCP client to it.

The tools read the telemetry. Seven tools change the lint rules of a workspace, each with a reason that the user sees and can undo in the app. One tool marks a finding fixed after a code change. The endpoint listens on loopback only. Nothing leaves the Mac.

The Loggerhead app must be installed and running. Download it first. The bridge exits when the app is not running. The free tier includes the MCP server.

Install

Claude Desktop

Download loggerhead-mcp.mcpb from the latest release and open it. Claude Desktop installs the extension.

Claude Code

bash
claude mcp add loggerhead -- "/Applications/Loggerhead.app/Contents/Resources/loggerhead-mcp"

Cursor, Codex, Windsurf, and other stdio clients

Every stdio client takes the same two values. The .mcp.json in this repository is the file to copy:

json
{  "mcpServers": {    "loggerhead": {      "command": "/Applications/Loggerhead.app/Contents/Resources/loggerhead-mcp"    }  }}

The app itself writes this entry for you: open Settings › AI and click Add beside your tool.

The bridge finds the app by itself on a fixed ladder of local ports. You set no port, and it needs no permission to read the app's files. Full instructions: Set up the MCP server.

Tools

ToolPurpose
query_logsSearch log records by text, severity, and time.
query_metricsRead time-series metrics by name and time range.
query_tracesFind traces by service, operation, duration, and time.
get_traceRead every span of one trace.
list_environmentsList every workspace and environment on this Mac, with the receiver ports.
get_receiver_infoReport the effective OTLP ports and the addresses to send telemetry to.
query_improvementsList the telemetry-lint findings: noisy logs, unbounded labels, secrets, lost trace context.
list_lint_rulesList the lint rules of a workspace with their state, thresholds, exceptions, ignored findings, and recent changes.
query_ai_findingsList the findings of the last AI analysis run. It does not start a run.
set_lint_rule_enabledSwitch a lint rule on or off for a workspace, with a reason.
set_lint_thresholdSet one threshold of a lint rule for a workspace, with a reason.
reset_lint_thresholdPut one threshold of a lint rule back to its default, with a reason.
add_lint_exceptionHide the findings of one lint rule for a service, metric, attribute key, operation, or log message, with a reason.
remove_lint_exceptionRemove one lint rule exception, with a reason.
ignore_findingIgnore one lint finding by its id, with a reason.
unignore_findingStop the ignore of one lint finding, with a reason.
mark_finding_fixedMark one lint finding fixed after a code change, so the app judges it by the telemetry after the fix.

One resource, loggerhead://stats, reports the total counts of logs, metrics, and spans. Every parameter is in the tools reference.

Privacy Policy

The bridge and the server read telemetry from the Loggerhead app on the same Mac and hand it to the MCP client you connected. They collect nothing about you, they store nothing of their own, they share nothing with a third party, and they open no network connection except to 127.0.0.1. Data retention is the app's: the telemetry lives in a DuckDB file on your disk for as long as the app's retention setting keeps it, and you can delete the file. The full policy of the publisher, Rubics Code, is at https://getloggerhead.com/privacy. Contact: [email protected].

Registry

The registry name of this server is com.getloggerhead/loggerhead.

  • MCP Registry name: mcp-name: com.getloggerhead/loggerhead

Licence

The loggerhead-mcp bridge and the files in this repository are under the MIT licence.

The bridge contains open-source Swift packages. The .mcpb bundle has Acknowledgements.txt with the licence text and the notice text of each package.

The bridge connects to Loggerhead, a proprietary Mac app by Rubics Code (ABN 40 440 756 434), Australia. The app has a free tier, and the source of the app is not public. The Loggerhead terms of service apply to the app.

Source: README.md at commit ec4cfeb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

10
  1. v1.12.0LatestOct 13, 2026
  2. v1.11.0Oct 6, 2026
  3. v1.9.0Oct 2, 2026
  4. v1.8.0Oct 1, 2026
  5. v1.7.0Sep 25, 2026
  6. v1.5.0Sep 25, 2026
  7. v1.4.0Sep 24, 2026
  8. v1.3.0Sep 24, 2026
  9. v1.2.1Sep 22, 2026
  10. v1.2.0Sep 22, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts