Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenüEinstellungen
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch

LogBrew

von LogBrewCoVersion 0.4.0i★ –iLäuft in der Cloud
Name in der Registryco.logbrew/mcp

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Marketing & Social Media

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 1 von 1 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Die Registry nennt keinen Schlüssel zum Eintragen.

Du brauchst

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://mcp.logbrew.co/mcp

Führe das in deinem Terminal aus

claude mcp add --transport http logbrew https://mcp.logbrew.co/mcp

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "logbrew": {
      "url": "https://mcp.logbrew.co/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "logbrew": {
      "type": "http",
      "url": "https://mcp.logbrew.co/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

ChatGPT verbindet sich nur mit Servern im Internet:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://mcp.logbrew.co/mcp

Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde über die Domain logbrew.co bestätigt (die Registry prüft, wem die Domain gehört)

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Endpunkt antwortet

    Noch nicht geprüft; wir prüfen die Endpunkte reihum

  • … Noch nicht geprüft

    Anmeldung mit OAuth

    Noch nicht geprüft; wir prüfen die Endpunkte reihum

  • … Noch nicht geprüft

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen

Im Vergleich mit anderen in Marketing & Social Mediai

  • Mehr Sterne als 0 % der anderen 2951 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 84 % der anderen 2951 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 2951 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist LogBrew sicher?

Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.4.0) kam vor 6 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Google Analytics MCP

von surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Läuft auf deinem Computer★ 244MITAktualisiert vor 9 Tagen
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

LogBrew MCP

The hosted LogBrew MCP server lets an AI agent read telemetry from your LogBrew projects and, if you allow it, triage issues and set up projects. You do not install it. Add its URL to your MCP client:

https://mcp.logbrew.co/mcp
  • Transport: Streamable HTTP. The server accepts MCP protocol versions 2026-07-28, 2025-11-25 and 2025-06-18.
  • Authorization: OAuth. Your client opens the LogBrew authorization page, you sign in, and you select the projects that the agent can read. The read scope lets the agent read. Operations that change data need the separate write scope, which you can decline when you approve the connection.
  • Changes: Without the write scope, the agent cannot change anything. With it, the agent can resolve, reopen, archive, prioritize and assign issues, and create projects and project keys, acting as you and within your permissions. Archiving an issue and revoking a key take a second, confirming call. The agent cannot change billing, members or account settings. A call on a project that you did not approve returns permission_denied.
  • Connection lifetime: An access token is valid for 1 hour, and the client refreshes it while you use the connection. A connection ends after 30 days without use, or 90 days after you approved it. Revoke a connection in the LogBrew dashboard under Settings > MCP connections, or with logbrew mcp revoke.

What an agent can do

The server has 2 tools. search is annotated read-only. execute is annotated as able to change data, because the catalog has write operations:

ToolWhat it does
searchFinds operations and returns the contract of one operation: its input and output schemas, permission, cost, safety and stability.
executeRuns one operation that search found and returns structured data, or an error with a stable code and a next action.

The operations read issues (investigation, lists, activity, owners and ownership rules), logs, traces, spans, metrics, product actions, releases, signal volume and product analytics. With the write scope, operations also resolve, reopen, archive, prioritize, assign and unassign issues, create projects, create and revoke project keys, send a test event, and load and remove sample data. The operation reference lists every operation in the shipped catalog and its limits.

Supported clients

Any MCP client that completes LogBrew authorization can connect. The client can publish a client ID metadata document or register dynamically.

Connect an AI agent with MCP shows the setup for many clients. For example, in Claude Code:

claude mcp add --transport http logbrew https://mcp.logbrew.co/mcp

claude mcp login logbrew

Operation reference

This reference describes the operation catalog shipped in catalog/operations.json, which the hosted server at https://mcp.logbrew.co/mcp loads. Most operations read. A connection with the write scope can also triage issues, create projects and project keys, send a test event, and load or remove sample data (see Changes). The catalog has no operations for billing, organization members, account settings, or deleting a project.

The server exposes two tools. search finds versioned operations and returns their input and output schemas. execute runs a selected operation. Every operation works only on the projects the signed-in user approved, and on projects created through the same connection. Discovery does not grant permission or establish that data is available for a particular account.

Each operation's info.permission names the delegated scope it needs: read, or write for an operation that changes data. A write operation also has safety: write, a title, and hints with the MCP tool annotation names readOnlyHint, destructiveHint, and idempotentHint. When the catalog holds a write operation, the execute tool declares readOnlyHint: false, and destructiveHint: true if any operation may delete or overwrite data. The authorization server checks the scope again on every call.

Use the returned schema for required fields, valid versions, filters, limits and pagination. Do not substitute CLI flags for JSON fields. Omit an optional field rather than sending null. Preserve the selected project and filters when following a cursor. Related evidence may be missing, unavailable or truncated; none of those states means zero events.

Investigations
OperationWhat it reads
issues.investigate.v16The issues.investigate.v15 result, where correlations.related_issues lists other issues from the same project, environment and release, one per issue, oldest first, up to 20. An issue is listed when it is unresolved and its first in-app frame has the same module, function and file, or when it occurred on the same trace within 5 minutes. Each item has basis (first_in_app_frame, same_trace), occurrence_count, first_seen_at and last_seen_at in that environment and release.
issues.investigate.v17The issues.investigate.v16 result plus two fields. source_locator.frame_links links each in-app frame whose captured path proves its repository file to that file and line at the deployed commit (frame_index, repository_relative_file, line, url). suspect_commits names the deploy where the issue first appeared or regressed (deployment_id, head_revision), the previous deploy of another release (base_revision), and up to 10 ranked commits in that range that changed a file in the issue's in-app frames (rank, sha, url, title, author_name, committed_at, files). The frame nearest the crash ranks first, then more matched files, then the newest commit. status and evidence.missing_fields say what is missing, such as repository contents access (suspect_commits.authorization) or a deploy without a commit SHA (suspect_commits.deployment.commit_sha). Suspect commits are read from GitHub.
issues.investigate.v15The issues.investigate.v14 result, with an archived issue reading archived instead of ignored in subject.status, the lifecycle's persisted and effective status, and each status change.
issues.investigate.v14One issue and its selected occurrence, reproduction, lifecycle, grouping and correction evidence. Each breadcrumb has data with method, url (no query or fragment) and status_code for an HTTP call, from and to for a route change, and logger for a log record; a field the breadcrumb does not have is null.
issues.investigate.v13The issues.investigate.v14 result without typed breadcrumb data.
logs.investigate.v1One log, its captured context and bounded related evidence.
traces.investigate.v3One trace, its failure evidence and cross-signal links.
spans.investigate.v1One exact span and its diagnostic evidence.
actions.investigate.v1One recorded product action and its related evidence. This does not perform the action.
metrics.investigate.v2A metric's meaning, captured description and linked evidence.
releases.investigate.v5One release, deployment comparisons and captured release markers.
Ownership and activity
OperationWhat it reads
issues.owners.v2The issues.owners.v1 result with teams: each owner has type user or team, and a team owner has team_id, slug and name. Ownership rules name a team as #slug; a CODEOWNERS @org/slug names the team with that slug.
issues.owners.v1Suggested owners of one issue, best first: matching ownership rules, then matching CODEOWNERS lines, then people who recently changed or were assigned the issue. Each owner names the rule, its line and what it matched. inputs counts the frame paths, modules, route template, tags and rules that were checked.
issues.activity.v1One issue's history, newest first: status, priority, assignee and severity rule changes, each with the account that made it, ending with when the issue was first seen. Follow next_cursor with cursor_time and cursor_id.
issues.activity.v2The issues.activity.v1 entries with team: the team of a team assignment, or null. An archive that ended by itself is a status entry with value unresolved and no account.
issues.activity.v3The issues.activity.v2 entries with archive on status entries: how an archive reopens (until is forever, escalating, time, events, or users, with reopen_at or count), and on an automatic reopen, the condition it met.
issues.ownership.v1A project's ownership rules and CODEOWNERS text, and the owners in them that name nobody with access to the project.

Owners and actors show a name and email only while that account can read the project. An account that lost access keeps only its ID in the activity and no longer appears as an owner. No owner means no rule matched the captured evidence; check inputs before you conclude that nobody owns the code.

An investigation may help locate a cause, but correlation alone does not prove one. Keep captured evidence separate from an inferred cause or a proposed fix. An absent description or source location remains absent. A later SDK upgrade does not backfill historical events.

Lists
OperationWhat it reads
projects.list.v2The projects this connection can read: each project's ID, name, creation time, setup status, last release and environment, and the signed-in user's access. It takes no input and returns every approved project in one response. Use it to find the project_id that other operations take.
projects.sample_data.v1Whether one project holds sample data, with the count of each sample signal: issue events, logs, trace spans and actions.
issues.list.v1Grouped issues through bounded cursor pages.
issues.list.v2Grouped issues with their priority (high, medium, low) and whether a user set it. Unless a user set it, the priority comes from how recent the issue is and how much it harms production. An issue someone archived reads as archived. Filter by status or priority.
issues.list.v3The issues.list.v2 fields plus each issue's assignee: user ID, name, and email, or null when nobody is assigned or the assignee can no longer read the project. Filter by assignee: me, none, or a user ID.
issues.list.v4The issues.list.v2 fields plus each issue's assignee: {type: user, user_id, name, email}, {type: team, team_id, slug, name}, or null. Filter by assignee: me, none, a user ID, team: , or my_teams.
issues.list.v5The issues.list.v4 fields plus archive on archived issues: until is forever, escalating, time, events, or users; reopen_at is the reopen time; count is the number of new events or users, or the events in 1 hour that count as escalating. Other issues have archive: null.
issues.list.v7The issues.list.v5 fields plus resolution on issues resolved in a release, user_impact and evidence on every issue. user_impact has status (complete, partial, not_captured, or unavailable), known_affected_users, count_method, coverage, and limitations, the same as impact.user_impact in issues.investigate.v17. evidence lists the fields of the latest occurrence that were captured, missing, redacted, or truncated, in the field names of the investigation's evidence. Each issue's next_action is investigate_issue; run issues.investigate.v17 for its ordered trace, logs, and breadcrumbs.
logs.list.v1Logs through bounded cursor pages.
traces.list.v1Traces with naming-quality coverage and cursor pagination.
actions.list.v1Recorded product actions through bounded cursor pages.

| `met

Nur der Anfang wird gezeigt; den Rest findest du im Repo

PopNx fragen