LogBrew

Name: LogBrew
Author: LogBrewCo

de LogBrewCoversión 0.4.0i★ –iSe ejecuta en la nube

Nombre en el registroco.logbrew/mcp

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en la nube
Transporte: Streamable HTTP
Categoría: Marketing y redes sociales

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
El registro no indica ninguna clave que completar.

Necesitas

Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Funciona en Claude para web, escritorio y móvil:

Abre Settings → Connectors
Presiona Add custom connector
Pega la dirección de abajo y presiona Add
Si te pide iniciar sesión, inicia sesión en el servicio del creador

https://mcp.logbrew.co/mcp

Ejecuta esto en tu terminal

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

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

ChatGPT solo se conecta a servidores en internet:

Abre ChatGPT en la web → Settings → Connectors (Apps)
Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
Pega la dirección de abajo, ponle un nombre y guarda
Si te pide iniciar sesión, inicia sesión en el servicio del creador

https://mcp.logbrew.co/mcp

Los nombres de los menús pueden variar un poco según el plan y con el tiempo.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio logbrew.co (el registro comprueba quién es dueño del dominio)
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
El endpoint responde
Aún sin revisar; revisamos los endpoints por turnos
… Aún sin revisar
Inicio de sesión con OAuth
Aún sin revisar; revisamos los endpoints por turnos
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint

Comparado con otros en Marketing y redes socialesi

Más estrellas que el 0% de los otros 2956 servidores de esta categoría
Publicado en el registro más recientemente que el 83% de los otros 2956 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 2956 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro LogBrew?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.4.0) llegó al registro hace 6 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

MCP YouTube Transcript

de jkawamoto

An MCP server retrieving transcripts of YouTube videos

Se ejecuta en tu computadora★ 495MITActualizado hace 9 días

Instalar

Google Analytics MCP

de surendranb

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

Se ejecuta en tu computadora★ 244MITActualizado hace 9 días

Instalar

BibiGPT YouTube Video Summarizer

de JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Se ejecuta en la nube★ 137MITActualizado hace 9 días

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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:

Tool	What it does
`search`	Finds operations and returns the contract of one operation: its input and output schemas, permission, cost, safety and stability.
`execute`	Runs 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

Operation	What it reads
`issues.investigate.v16`	The `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.v17`	The `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.v15`	The `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.v14`	One 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.v13`	The `issues.investigate.v14` result without typed breadcrumb `data`.
`logs.investigate.v1`	One log, its captured context and bounded related evidence.
`traces.investigate.v3`	One trace, its failure evidence and cross-signal links.
`spans.investigate.v1`	One exact span and its diagnostic evidence.
`actions.investigate.v1`	One recorded product action and its related evidence. This does not perform the action.
`metrics.investigate.v2`	A metric's meaning, captured description and linked evidence.
`releases.investigate.v5`	One release, deployment comparisons and captured release markers.

Ownership and activity

Operation	What it reads
`issues.owners.v2`	The `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.v1`	Suggested 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.v1`	One 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.v2`	The `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.v3`	The `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.v1`	A 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

Operation	What it reads
`projects.list.v2`	The 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.v1`	Whether one project holds sample data, with the count of each sample signal: issue events, logs, trace spans and actions.
`issues.list.v1`	Grouped issues through bounded cursor pages.
`issues.list.v2`	Grouped 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.v3`	The `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.v4`	The `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.v5`	The `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.v7`	The `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.v1`	Logs through bounded cursor pages.
`traces.list.v1`	Traces with naming-quality coverage and cursor pagination.
`actions.list.v1`	Recorded product actions through bounded cursor pages.

| `met

Solo se muestra el principio; lee el resto en el repo

LogBrew

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Marketing y redes socialesi

Preguntas frecuentes

Alternativas

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README del creador

LogBrew MCP

What an agent can do

Supported clients

Operation reference

Investigations

Ownership and activity

Lists