Debriefing
io.debriefingv2.0.0更新於 Oct 6, 2026
Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.
概覽
讓助理讀取與管理 Debriefing 競爭情報工作區:競品訊號、摘要、對戰卡以及公開簡報。
- 功能
- Debriefing 是為 B2B 團隊提供的託管式競爭情報服務。透過這個遠端 MCP 伺服器,助理不必登入就能搜尋公開簡報與指南;連接工作區後,可以列出追蹤的競品、搜尋附來源證據的訊號、讀取摘要與對戰卡,並調出某項結論背後的來源。寫入與消耗類工具可以新增或移除競品與監控頁面,置頂、收藏、加註與評價訊號和摘要,更新公司檔案與理想客戶輪廓,設定監控頻率與遞送管道,建立分享連結,邀請成員,並觸發研究、對戰卡產生與定位草稿。
- 適用情境
- 適合讓助理回答競品問題、回顧上次造訪以來的變化、為針對某個競品的業務通話做準備,或查核某項競爭情報結論的來源。適用於已在使用 Debriefing 工作區的團隊,也適用於只需要公開簡報與指南的人。
- 執行需求
- 遠端 streamable HTTP 端點,無需安裝或執行任何東西。公開工具與 tools/list 不需要憑證。工作區存取使用 OAuth 2.1 登入,作用域為 read、write 與 spend,或使用以 Authorization: Bearer 或 X-API-Key 傳送的 API 金鑰。部分工具僅限管理員或需要付費方案,Slack 遞送需要在應用程式內完成 Slack 連線。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Debriefing,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"debriefing": {
"type": "http",
"url": "https://debriefing.io/mcp"
}
}
}README
Debriefing MCP server
Debriefing is competitive intelligence for B2B teams. It watches your competitors, finds their moves (a price change, a launch, a new hire), and backs every signal with the source evidence. This MCP server lets Claude, ChatGPT, Cursor, and any other MCP client work on a Debriefing workspace.
This repository holds the public listing for the server: this README and server.json for the official MCP Registry. The server itself is hosted. There is nothing to install or run.
- Website: https://debriefing.io
- Docs: https://debriefing.io/developers?tab=mcp
- Server card: https://debriefing.io/.well-known/mcp/server-card.json
Endpoint
Auth
- OAuth 2.1 (Claude, ChatGPT, and other OAuth clients). The person signs in to Debriefing, approves the app, and picks the scopes:
read(always),write(changes that cost nothing), andspend(actions that use a plan allowance). PKCE S256, dynamic client registration, and Client ID Metadata Documents are supported. Metadata:https://debriefing.io/.well-known/oauth-authorization-serverandhttps://debriefing.io/.well-known/oauth-protected-resource. - API key (other clients). Create a key in the Debriefing app and send it as
Authorization: Bearer <key>orX-API-Key: <key>. A key acts as the admin who created it. - No credential.
tools/listand the four public tools work without one.
Each tool checks its scope, the person's role, and the plan. A refusal comes back as isError with the link that fixes it.
Connect
Claude (claude.ai, Desktop): Settings, Connectors, Add custom connector, URL https://debriefing.io/mcp.
Claude Code:
Cursor and other JSON-config clients:
ChatGPT: add https://debriefing.io/mcp as a connector in developer mode.
Tools
Public tools (no sign-in)
They read only the briefs and guides Debriefing publishes on debriefing.io.
Read tools (scope read)
Read the workspace. They change nothing.
Write tools (scope write)
Change the workspace. They cost nothing.
Spend tools (scope spend)
Use a plan allowance, such as the weekly research allowance or a daily cap.
Support
Questions and bugs: open an issue here, or write to the contact on https://debriefing.io.
License
The files in this repository are MIT licensed. The Debriefing service and its source code are proprietary.
來源:README.md,提交 14a8032
工具
0版本歷史
1- v2.0.0最新Oct 6, 2026

