Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
在云端运行✓ 服务方 · relaticle.com
LogBrew
What it does
Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.
- Connects 在云端运行
- Account or key Sign in to the service when you connect (OAuth)
- Category 营销与社交媒体
安装
选择你使用的 AI 应用，然后复制设置。
通过 4/4 项检查 · 你的提问会经过开发者的服务器（logbrew.co） · ✓ 命令已检查 2026年11月13日
第一步：你用哪个 AI？
选择你用的应用，步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥，不用安装程序 · 在 claude.ai 或桌面应用设置一次，即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者（Owner）添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”，填写这 2 项
把这里的内容复制到 Claude 中同名的输入框，然后点击 Continue
Name · 名称LogBrewRemote MCP server URL · 地址https://logbrew.co/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择（Sign in now、Sign in when needed 或 No sign in），然后点击 Add
在聊天中开启
+ConnectorsLogBrew
试一试
用 LogBrew 告诉我你能帮我做什么，然后做一件给我看✓ 如果 Claude 说正在使用 LogBrew，或回答中出现 LogBrew 的工具名称，就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP：网页版 ChatGPT Business、Enterprise 或 Edu · Pro：以读取/获取权限连接，修改数据的工具可能用不了 · Plus：官方文档尚未确认，如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称，在 Connection 下粘贴地址，勾选风险提示，然后点击 Create as a plugin
Name · 名称LogBrewConnection · 地址https://logbrew.co/mcp在聊天中选择 LogBrew
开启新聊天，输入前先从插件列表中选择 LogBrew
试一试
用 LogBrew 告诉我你能帮我做什么，然后做一件给我看✓ 如果 ChatGPT 说正在使用 LogBrew，或回答中出现 LogBrew 的工具名称，就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥，不用安装程序
打开终端
Mac：按 Command+空格，输入 Terminal · Windows：打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user logbrew https://logbrew.co/mcp在 Claude Code 中输入 /mcp
应能看到 LogBrew 在列表中并显示已连接
试一试
用 LogBrew 告诉我你能帮我做什么，然后做一件给我看✓ 如果 Claude Code 说正在使用 LogBrew，或回答中出现 LogBrew 的工具名称，就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥，不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 LogBrew 告诉我你能帮我做什么，然后做一件给我看✓ 如果 Cursor 说正在使用 LogBrew，或回答中出现 LogBrew 的工具名称，就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥，不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 LogBrew 告诉我你能帮我做什么，然后做一件给我看✓ 如果 VS Code 说正在使用 LogBrew，或回答中出现 LogBrew 的工具名称，就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用（如 Windsurf、Zed、Gemini CLI）添加方式各不相同，请在应用列表中查看
通过网页连接的应用使用的地址
地址
https://logbrew.co/mcpJSON 设置在下方“开发者专用”中
开发者专用：终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user logbrew https://logbrew.co/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"logbrew": {
"url": "https://logbrew.co/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"logbrew": {
"type": "http",
"url": "https://logbrew.co/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。
通过互联网连接，适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
服务器要求先登录，才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月15日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 logbrew.co 验证（注册中心会核实域名所有权）
- ✓ 通过
仍在维护
代码最后更新于4天前
- – 不适用
有许可证
不适用：由 logbrew.co 的所有者自己运行的云端服务器，你不会运行仓库里的代码
- ✓ 通过
端点有响应
在 509 毫秒内响应（HTTP 401）
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表
作者：申请重新检查或报告信息错误
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 3957 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 3957 个服务器的 81% 更新
- 基础检查结果等于或优于此分类中其他 3957 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
LogBrew 安全吗？
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。
它还在维护吗？
GitHub 仓库最后更新于4天前，最新版本（0.5.0）于7天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，因此也能用于接受远程 MCP 的应用，例如网页版 ChatGPT（Business 及以上为完整 MCP；Pro 为只读）。
有什么可以替代它？
同一分类中有：Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面，再按星标排序。
如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
在云端运行✓ 服务方 · chatbotx.io
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
在云端运行✓ xquik.com
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
在云端运行✓ 服务方 · betterlytics.io
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
在云端运行✓ 服务方 · bibigpt.co
- Relaticle — 在云端运行，无需安装 · 不需要密钥
- ChatbotX — 在云端运行，无需安装 · 不需要密钥
- X (Twitter) MCP Server by Xquik — 在云端运行，无需安装 · 不需要密钥
- Betterlytics — 在云端运行，无需安装 · 需要密钥
- BibiGPT YouTube Video Summarizer — 在云端运行，无需安装 · 不需要密钥
作者的 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://logbrew.co/mcpThe earlier URL, https://mcp.logbrew.co/mcp, keeps working, so a client that already uses it needs no change. Each URL is its own protected resource: reconnect with the new URL to move a client to it.
- Transport: Streamable HTTP. The server accepts MCP protocol versions
2026-07-28,2025-11-25and2025-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
readscope lets the agent read. Operations that change data need the separatewritescope, which you can decline when you approve the connection. - Changes: Without the
writescope, 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 returnspermission_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://logbrew.co/mcpclaude mcp login logbrew
Operation reference
This reference describes the operation catalog shipped in catalog/operations.json, which the hosted server at https://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