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…
debriefing-mcp is an MCP project maintained in the 0xrome/debriefing-mcp repository. The maintainer describes its purpose as “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…”. Read the project documentation for the complete scope.
The maintainer’s configuration uses https://debriefing.io/mcp. Check the project’s account and authentication instructions when adding the endpoint to your client.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| search_public_briefs | Searches the competitive briefs Debriefing publishes on debriefing.io about named companies, newest first. Each brief is dated and every finding cites a public |
| get_public_brief | Gets one competitive brief that Debriefing published on debriefing.io: the summary, each finding with its category and date, and the numbered public sources… |
| search_guides | Searches the public competitive intelligence library on debriefing.io: how-to guides, glossary terms, tool comparisons, alternatives pages, company profiles… |
| get_free_brief_link | Gets the debriefing.io links where a person requests a free competitive brief about their own company and competitors, signs up for a workspace, or compares… |
| get_workspace | Gets the Debriefing workspace this connection works on: its name and website, who you are in it and your role, the scopes this connection holds, and the… |
| get_plan_and_limits | Gets the workspace plan and every limit an agent runs into: competitor slots, the weekly research allowance, the daily caps on battlecards, ICP refreshes and… |
| list_competitors | Lists the competitors this Debriefing workspace tracks, with the id, name, website, and category of each. Call it first to get the competitor_id that other… |
| get_competitor | Gets the dossier for one tracked competitor: company facts, the risk and opportunity it poses to this workspace, and the stored reads on positioning… |
| search_signals | Searches open signals, newest first. A signal is a competitor move that Debriefing found, such as a price change or a launch, with the source evidence.… |
| list_digests | Lists the digests Debriefing wrote for this workspace, newest first. A digest is a brief that sums up competitor moves over a period. Filter by type, such as… |
| get_digest | Gets one digest by id or slug, or the newest digest when no id is given. Pass type daily_digest for the newest daily digest. Use it when the user asks for… |
| list_battlecards | Lists the battlecards Debriefing wrote for this workspace, one for each competitor that has one. A battlecard holds talk tracks for sales calls against that… |
| get_battlecard | Gets one battlecard by competitor_id or battlecard_id. Use it when the user prepares a sales call against a competitor. |
| get_evidence | Gets the evidence behind one signal: each source excerpt with its URL and date. Use it when the user asks where a claim comes from. |
| get_company_profile | Gets the workspace's own company profile: description, category, target customer, positioning lists, and the ideal customer profile. Debriefing reads every… |
| get_delivery_settings | Gets how often Debriefing runs a monitoring cycle for the workspace, the cadences the plan allows, and whether a finished cycle goes out by email and to Slack. |
| list_members | Lists the people in the workspace with their roles. An admin also sees pending invitations. |
| what_changed | Lists everything new in the workspace since a time: signals Debriefing found, digests it wrote, and battlecards it wrote or rewrote. Use it to catch up, such… |
| add_competitor | Adds a competitor to the workspace's core watchlist from its website. Debriefing then monitors it. Admin only. The plan sets how many core competitors fit… |
| rename_competitor | Changes the display name of one tracked competitor. Admin only. |
| remove_competitor | Takes one core competitor off the watchlist. Debriefing stops monitoring it and keeps its history. Admin only, on a paid plan. |
| add_monitored_page | Asks Debriefing to watch one more page of a core competitor, such as its pricing page. Changes on it then show up as signals. Up to 10 pages per competitor.… |
| remove_monitored_page | Stops watching a page that someone added on a core competitor. Name it by page_id or url. Admin only, on a paid plan. |
| pin_signal | Pins a signal for the whole team, or removes the pin with pinned false. |
| save_signal | Saves a signal to your own saved list, or removes it with saved false. Only you see your saved signals. |
| add_signal_note | Adds a talking point to a signal. The team sees it in the workspace. It never appears on a public link unless the link includes notes. |
| rate_signal | Tells Debriefing whether a signal was useful to you. For not useful, add reasons and a comment. A new rating replaces your old one. |
| pin_digest | Pins a digest for the whole team, or removes the pin with pinned false. |
| add_digest_note | Adds a talking point to a digest. The team sees it in the workspace. |
| rate_digest | Scores a digest from 1 to 5, says what is missing from it, or both. A new rating replaces your old one. |
| add_battlecard_note | Adds what the team knows about a core competitor that no page says. The next rewrite of its battlecard reads the note as framing, never as a verified fact. |
| update_company_profile | Changes fields of the workspace's company profile. Only the fields you send change. The lists replace the old lists. Admin only. Locked while the first brief… |
| set_monitoring_cadence | Sets how often Debriefing runs a monitoring cycle. The plan decides which cadences are allowed; get_delivery_settings lists them. Admin only, on a paid plan. |
| set_delivery_channels | Turns delivery of a finished cycle by email and to Slack on or off. Only the channels you send change. Slack needs a paid plan and a Slack connection made in… |
| create_share_link | Makes a public link to one signal that anyone with the address can open. A new link replaces the old one, which stops working. The plan sets how long a link… |
| invite_member | Sends an email invitation to join the workspace as a member. The invitation lasts 7 days. Inviting the same address again sends a fresh email. Admin only, on a |
| research_competitor | Starts the first research on one core competitor that has none yet: Debriefing reads its site and outside sources. It uses one update from the weekly… |
| refresh_watchlist | Refreshes the research on the core watchlist now, instead of at the next cycle. It uses one update from the weekly research allowance. Admin only. |
| generate_battlecard | Writes or rewrites the battlecard for one core competitor now, instead of at the next cycle. It takes about a minute; read it afterwards with get_battlecard.… |
| update_icp | Sets the ideal customer profile, then re-reads how much each tracked competitor overlaps it. Only the dimensions you send change; an empty list clears one.… |
| draft_positioning | Reads the company's own website and drafts the empty positioning fields: value propositions, differentiators, and exclusions. Filled fields stay as they are.… |
{
"mcpServers": {
"debriefing": {
"url": "https://debriefing.io/mcp"
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.