Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
BugEzy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bugezy-mcp https://bugezy.dev/mcp
# 2 — ask your agent for something these tools do
# list_reports, get_report_overview, get_console_logs and 11 more
BugEzy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bugezy-mcp https://bugezy.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
列出某使用者的 Bug 報告(需提供 user_email + session_token 驗證身分)。List a user's bug reports — requires user_email and session_token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_email | string | no | 使用者 email;只回傳該 email 的報告。未提供則不回任何報告(安全預設)。 |
| session_token | string | no | BugEzy session token(如果 MCP URL 已帶 ?token= 則不需提供)。 |
| limit | number | no | — |
| url | string | no | — |
取得報告概覽(metadata + 各筆數 + AI Bug 導航摘要,不含原始資料)。Report overview with AI bug summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得 Console 記錄(warn/error)。Console logs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得 Network 錯誤(4xx/5xx)。Network errors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得開發者語音描述(中文轉錄)。Developer voice transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得頁面資訊(URL/標題/瀏覽器/解析度)。Page info.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
DOM 軌跡摘要(事件數/時長/類型分布,不回完整資料)。rrweb summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得完整 DOM 事件(⚠ 資料量大)。Full rrweb events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
取得某使用者當前頁面的即時 Console/Network 錯誤(需 user_email + session_token 驗證身分)。Live console/network errors — requires user_email and session_token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_email | string | yes | 你的 BugEzy email(只讀你自己的即時錯誤) |
| session_token | string | no | BugEzy session token(如果 MCP URL 已帶 ?token= 則不需提供)。 |
取得某使用者終端機的即時錯誤日誌(stderr/throw/crash,需 user_email + session_token 驗證;付費功能)。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_email | string | yes | 你的 BugEzy email(只讀你自己的終端機日誌) |
| session_token | string | no | BugEzy session token(如果 MCP URL 已帶 ?token= 則不需提供)。 |
取得當月的 MCP 使用量統計(呼叫次數、token 消耗、省了多少)。Monthly MCP usage stats.
No parameter schema on file.
查詢目前方案與本月剩餘用量(錄製 / 回溯 / MCP 讀取)。需 user_email + session_token 驗證身分。查詢不會消耗額度。Check your plan and remaining monthly quota — requires user_email and session_token. Checking does not consume quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_email | string | no | 使用者 email。未提供則無法查詢(安全預設)。 |
| session_token | string | no | BugEzy session token(MCP URL 已帶 ?token= 則不需提供)。 |
高畫質 AI 分析:取得報告截圖圖片(視覺 Bug 用)。⚠ 圖片消耗較高 Token(每張 ~3,000-8,000),建議只在需要看畫面時使用。Report screenshots.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | — |
| include_images | boolean | no | 開啟高畫質 AI 分析(預設 false,只回 metadata 省 Token) |
取得一份報告的完整時間軸(時序麵包屑)。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線,AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡(省去逐一呼叫 console/network/voice 各 tool)。Full report timeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | 報告 ID |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BugEzy or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish BugEzy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.