LogBrew

Name: LogBrew
Author: LogBrewCo

제작자: LogBrewCo버전 0.4.0i★ –i클라우드에서 실행

레지스트리 이름co.logbrew/mcp

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 클라우드에서 실행
전송 방식: Streamable HTTP
카테고리: 마케팅 및 소셜 미디어

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
제작자의 서버에서 실행돼요. 내가 요청한 내용은 제작자의 서버를 거쳐요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:

Settings → Connectors 열기
Add custom connector 누르기
아래 주소를 붙여 넣고 Add 누르기
로그인하라고 하면 제작자의 서비스에 로그인하기

https://mcp.logbrew.co/mcp

터미널에서 이 명령어를 실행하세요

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

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:

웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
로그인하라고 하면 제작자의 서비스에 로그인하기

https://mcp.logbrew.co/mcp

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 도메인 logbrew.co 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
엔드포인트 응답
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
… 아직 점검 안 함
OAuth로 로그인
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 2952개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 2952개 중 84%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 2952개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

LogBrew, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.4.0)은 6일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

MCP YouTube Transcript

제작자: jkawamoto

An MCP server retrieving transcripts of YouTube videos

내 컴퓨터에서 실행★ 495MIT9일 전 업데이트

설치

Google Analytics MCP

제작자: surendranb

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

내 컴퓨터에서 실행★ 244MIT9일 전 업데이트

설치

BibiGPT YouTube Video Summarizer

제작자: JimmyLv

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

클라우드에서 실행★ 137MIT9일 전 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

LogBrew

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

제작자의 README

LogBrew MCP

What an agent can do

Supported clients

Operation reference

Investigations

Ownership and activity

Lists