Debriefing vs Lexicon
A side-by-side look at the Debriefing and Lexicon MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Debriefing for research work over a hosted endpoint; choose Lexicon for research over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Debriefing when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_public_briefs, get_public_brief, search_guides.
Choose Lexicon when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
LEXICON_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 55/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | LEXICON_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
Debriefing tools 41
search_public_briefsSearches the competitive briefs Debriefing publishes on debriefing.io about named companies, newest first. Each brief is dated and every finding cites a public source. Filter by words in the brief and by company name, slug, or domain. With no arguments, lists the newest briefs. Needs no Debriefing…get_public_briefGets one competitive brief that Debriefing published on debriefing.io: the summary, each finding with its category and date, and the numbered public sources with their URLs. Name the brief by its URL, or by company_slug and slug from search_public_briefs. With company_slug only, gets the newest bri…search_guidesSearches the public competitive intelligence library on debriefing.io: how-to guides, glossary terms, tool comparisons, alternatives pages, company profiles, and market intel posts. Returns the title, a short excerpt, and the page URL of each match, best match first. Needs no Debriefing account.get_free_brief_linkGets 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 plans. It only returns links. It sends nothing and creates nothing.get_workspaceGets 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 plan. Call it first when you are not sure what you may do.get_plan_and_limitsGets the workspace plan and every limit an agent runs into: competitor slots, the weekly research allowance, the daily caps on battlecards, ICP refreshes and positioning drafts, share link lifetimes, monitoring cadences, and which features need a paid plan. Includes the pricing link.list_competitorsLists 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 tools take.get_competitorGets the dossier for one tracked competitor: company facts, the risk and opportunity it poses to this workspace, and the stored reads on positioning, product, pricing, funding, traffic, and more. Use it when the user asks about one competitor in depth.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Debriefing
{
"mcpServers": {
"debriefing": {
"url": "https://debriefing.io/mcp"
}
}
}
Lexicon
{
"mcpServers": {
"lexicon": {
"url": "https://dbssearch.today/mcp/v1"
}
}
}
Frequently asked questions
Debriefing is categorized under Research and uses a remote HTTP/SSE transport. Lexicon belongs to Research and uses a remote HTTP/SSE transport. Pick Debriefing for research work and Lexicon for research.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Debriefing has no declared pricing — check the project's own site. Lexicon has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add debriefing and lexicon as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Debriefing has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Lexicon has 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.