Analytics
dealwize.co
Provides Dealwize sales intelligence by analyzing B2B sales opportunities to score deal health, identify risks, map stakeholders, and recommend next actions.
ENDPOINT 1
https://api.dealwize.co/api/v1/mcp
MCP server metadata
- Name
- dealwize-mcp
- Version
- 1.29.1
Known tools 14
analyze_dealAnalyse a raw B2B sales call transcript, meeting notes, sales conversation, or email thread and produce a Dealwize Deal Health Intelligence assessment.
Potential side effectsget_deal_healthAssess the health of a saved B2B sales opportunity using Dealwize Deal Health Intelligence and return a 0–100 health score with the reasons behind it.
Inferred read-onlyget_deal_risksIdentify the most important hidden and explicit risks that could prevent a saved B2B sales opportunity from closing.
Inferred read-onlyget_stakeholdersAnalyse the stakeholder landscape of a saved B2B sales opportunity, including champion strength, economic buyer access, decision makers, technical evaluators, procurement contacts, influencers, blockers, and missing stakeholders.
Inferred read-onlyget_next_best_actionDetermine the single highest-priority action the seller should take next to increase the probability of progressing or closing a saved B2B sales opportunity.
Inferred read-onlyget_dealRetrieve the complete Dealwize intelligence record for a specific saved B2B sales opportunity.
Inferred read-onlyget_dealsList the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks.
Inferred read-onlylist_dealsList the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks.
Inferred read-onlygenerate_mutual_action_planGenerate a structured buyer-facing Mutual Action Plan (MAP) for a B2B sales opportunity using the available deal evidence or transcript.
Inferred read-onlyget_mutual_action_planRetrieve the current living Mutual Action Plan for a saved B2B sales opportunity, including phases, milestones, action items, owners, checklist items, and deadlines.
Inferred read-onlyupdate_dealUpdate an existing saved B2B sales opportunity or ingest new sales evidence such as a call transcript, meeting notes, or conversation into the deal.
Potential side effectsshare_dealCreate a safe shareable link for approved Dealwize deal intelligence or buyer-facing deal content that can be viewed without requiring the recipient to authenticate.
Potential side effectsget_login_urlGenerate a secure Dealwize authentication URL when the user needs to sign in, create or access their Dealwize account, authorize access to private Dealwize resources, or continue from a temporary analysis into a persistent Dealwize workspace.
Potential side effectsconnect_accountStart the authorization flow for connecting the current AI client to the user's Dealwize account.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dealwize-mcp]
url = "https://api.dealwize.co/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dealwize-mcp": {
"type": "http",
"url": "https://api.dealwize.co/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dealwize-mcp
Remote MCP URL: https://api.dealwize.co/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dealwize-mcp": {
"url": "https://api.dealwize.co/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dealwize-mcp": {
"type": "http",
"url": "https://api.dealwize.co/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dealwize-mcp",
"transport": "streamable-http",
"url": "https://api.dealwize.co/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.