Debriefing
io.debriefingv2.0.0Updated Oct 6, 2026
Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.
Overview
Lets an assistant read and manage a Debriefing competitive-intelligence workspace: competitor signals, digests, battlecards, and public briefs.
- What it does
- Debriefing is a hosted competitive-intelligence service for B2B teams. Through this remote MCP server, an assistant can search public briefs and guides without signing in, and, with a workspace connection, list tracked competitors, search evidence-backed signals, read digests and battlecards, and pull the sources behind a claim. Write and spend tools add or remove competitors and monitored pages, pin, save, note and rate signals and digests, update the company profile and ICP, set monitoring cadence and delivery channels, create share links, invite members, and trigger research, battlecard generation and positioning drafts.
- When to use it
- Use it when an assistant should answer questions about competitors, catch up on what changed since a last visit, prepare a sales call against a named competitor, or check where a competitive claim comes from. It fits teams already using a Debriefing workspace, or anyone who only needs the public briefs and guides.
- Requirements
- A remote streamable HTTP endpoint; nothing to install or run. Public tools and tools/list need no credential. Workspace access uses OAuth 2.1 sign-in with scopes read, write and spend, or an API key sent as Authorization: Bearer or X-API-Key. Some tools are admin-only or need a paid plan, and Slack delivery needs a Slack connection made in the app.
Installation
In SourceWeft
- Open Debriefing in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"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.
Source: README.md at commit 14a8032
Tools
0Version history
1- v2.0.0LatestOct 6, 2026