# Dealwize Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Dealwize

Analyze B2B sales deals to uncover risks, stakeholders, and winning next steps.

- Record: https://musedirectory.ai/connector/dealwize
- Category: Productivity
- Developer: Dealwize (https://dealwize.co/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 897ms, checked 2026-09-28T09:46:09Z
- Endpoint: https://api.dealwize.co/api/v1/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T09:35:58Z)
- Source: Found in the official MCP Registry (co.dealwize/dealwize) https://registry.modelcontextprotocol.io/v0/servers?search=co.dealwize%2Fdealwize

Dealwize analyzes sales transcripts, meeting notes, and emails to assess deal health, identify risks, map stakeholders, and recommend actions. It generates mutual action plans and tracks pipeline opportunities with health scores and buyer commitment signals.

Example request: "Analyze my sales call transcript to see if this deal is really progressing or at risk of slipping."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Dealwize to help me. It is a free service with an MCP server at https://api.dealwize.co/api/v1/mcp. It needs an API key from Dealwize; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- analyze_deal: Analyse a raw B2B sales call transcript, meeting notes, sales conversation, or email thread and produce a Dealwize Deal Health Intelligence assessment. Use this when the user wants to know whether a sales opportunity is genuinely progressing, likely to close, at risk of slipping,
- get_deal_health: Assess 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. Use this when the user asks whether a deal is healthy, genuinely progressing, likely to close, likely to slip, at risk, forecasta
- get_deal_risks: Identify the most important hidden and explicit risks that could prevent a saved B2B sales opportunity from closing. Categorize risks across commercial, stakeholder, timing, procurement, technical, competitive, qualification, and buyer-commitment factors. Use this when the user a
- get_stakeholders: Analyse 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. Use this when the user asks who matters in the dea
- get_next_best_action: Determine the single highest-priority action the seller should take next to increase the probability of progressing or closing a saved B2B sales opportunity. Base the recommendation on deal health, buyer commitment, stakeholder gaps, risks, timeline, qualification gaps, procureme
- get_deal: Retrieve the complete Dealwize intelligence record for a specific saved B2B sales opportunity. Includes deal reality, health, brutal truth, North Star goals, top risks, stakeholder intelligence, buyer commitment, qualification gaps, timeline context, and next best action. Use thi
- get_deals: List the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks. Use this when the user wants an overview of their pipeline, asks which deals need attention, wants to compare opportunities
- list_deals: List the user's saved B2B sales opportunities in Dealwize with their current health scores, statuses, buyer commitment, North Star goals, and primary risks. Use this when the user wants an overview of their pipeline, asks which deals need attention, wants to compare opportunities
- generate_mutual_action_plan: Generate a structured buyer-facing Mutual Action Plan (MAP) for a B2B sales opportunity using the available deal evidence or transcript. Create logical phases, milestones, action items, owners, dependencies, and target deadlines that help the buyer and seller progress toward a su
- get_mutual_action_plan: Retrieve the current living Mutual Action Plan for a saved B2B sales opportunity, including phases, milestones, action items, owners, checklist items, and deadlines. Use this when the user asks to review the deal plan, check MAP progress, see outstanding actions, identify overdue
- update_deal: Update an existing saved B2B sales opportunity or ingest new sales evidence such as a call transcript, meeting notes, or conversation into the deal. New evidence should trigger the existing Dealwize intelligence process so health, risks, stakeholders, buyer commitment, qualificat
- share_deal: Create a safe shareable link for approved Dealwize deal intelligence or buyer-facing deal content that can be viewed without requiring the recipient to authenticate. Use this when the user asks to share a deal diagnosis, deal intelligence one-pager, deal board, or buyer-facing de
- get_login_url: Generate 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.
- connect_account: Start the authorization flow for connecting the current AI client to the user's Dealwize account. Use this when the user wants the AI client to access saved private deals, persistent Dealwize intelligence, living Mutual Action Plans, or other authenticated Dealwize resources.

Screening checks:
- MCP handshake: pass (Answered in 280ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.dealwize.co, dealwize.co not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (14 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)