io.github.shashwatgtm/revenue-enablement-mcp

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Revenue Enablement: 12 deal and sales enablement tools by Helix GTM Consulting

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "revenue-enablement-mcp": {
      "url": "https://revenue-enablement.gtmhelix.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• account_plan_builder read-only

  Generate strategic account plans with power mapping (one row per contact you name), whitespace analysis, competitive questions and an answer for each objection. Builds a 90-day plan from the contacts, products, threats and notes you give it; it does not look the account up.

  Parameters:

  • account_name (required) — string — Company/account name
  • industry — string — Industry vertical
  • current_arr — number — Current ARR with this account (0 for prospects)
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • account_notes — string — Any additional context about the account
  • your_solution — string — Your product/service offering
  • known_contacts — string — Known contacts and their roles (can be rough notes)
  • current_products — string — Products/services they currently use from you
  • competitive_threats — string — Known competitors in the account
  • expansion_opportunities — string — Potential expansion areas or whitespace

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• deal_strategy_coach read-only

  Get deal-specific winning strategies based on deal stage, competitive dynamics, and stakeholder positions. Provides tactical next steps and risk mitigation.

  Parameters:

  • deal_name (required) — string — Deal/opportunity name
  • deal_stage (required) — string — Current deal stage
  • blockers — string — Known blockers or objections
  • close_date — string — Target close date
  • deal_value — number — Deal value in dollars
  • next_steps — string — Currently planned next steps
  • competitors — string — Competitors in the deal and their position
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • days_in_stage — number — Days the deal has been in current stage
  • your_solution — string — What you are selling
  • economic_buyer — string — Economic buyer name and engagement level
  • champion_status — string — Champion identification status

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• discovery_question_bank read-only

  Writes a discovery question list from the framework you choose (MEDDPICC, BANT, SPICED, Challenger, Gap Selling or all five) and what you already know about the prospect. Returns an opening for the conversation, questions in the language of the prospect's sector and on what your solution covers, the questions for each part of the framework, a closing for the call and what to say to an objection. It uses only the inputs you give and says which it did not get.

  Parameters:

  • framework (required) — string — Discovery framework to use
  • deal_stage — string — Stage of conversation
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • gaps_to_fill — string — Specific information gaps to address
  • known_metrics — string — Metrics/KPIs already discussed
  • prospect_role — string — Role of person you are meeting with
  • your_solution — string — Your product/solution for relevant questions
  • known_pain_points — string — Pain points already identified
  • prospect_industry — string — Prospect industry for context

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• roi_business_case_builder read-only

  Build an ROI business case from the buyer's own figures: annual_value_estimate, or current_annual_cost with expected_improvement_percent. With them it calculates the ROI, payback, three-year value and sensitivity. Without them it shows no ROI: it names the inputs to add and gives the structure of the case (the cost lines to price, your quoted results as reference points, the questions to ask).

  Parameters:

  • your_solution (required) — string — Your product/solution
  • primary_value_driver (required) — string — Primary value category
  • industry — string — The customer's industry, in any words. Used for wording and sector notes only: no industry figure is applied to the calculation. A return needs the buyer's own figures (annual_value_estimate, or current_annual_cost with expected_improvement_percent)
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • company_size — string — Company size tier
  • customer_name — string — Customer/prospect name
  • known_metrics — string — Metrics the prospect shared, or results you can quote. Listed as reference points, never as the buyer's figures; to turn the buyer's figures into the value, give current_annual_cost and expected_improvement_percent, or annual_value_estimate
  • annual_revenue — number — Customer annual revenue. Shown as your input; it is not turned into a value
  • employee_count — number — Number of employees. Shown as your input; it is not turned into a value
  • solution_price — number — Annual cost of your solution
  • current_process — string — How they do it today. Separate the ways of working with a semicolon: each becomes a cost line to price. Not used in the calculation
  • current_annual_cost — number — Optional: what the problem or the current process costs the buyer a year, in dollars (their figure)
  • annual_value_estimate — number — Optional: the buyer's own estimate of the annual value in dollars; used as the value when given
  • implementation_timeline — string — Expected implementation time. Shown in the output; not used in the calculation
  • expected_improvement_percent — number — Optional: the share of that annual cost the buyer expects to save, in percent (their figure)

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• mutual_action_plan_generator read-only

  Generate collaborative close plans with milestones, owners, and dates. Creates alignment between buyer and seller on path to decision.

  Parameters:

  • deal_name (required) — string — Deal/opportunity name
  • target_close_date (required) — string — Target close date (YYYY-MM-DD)
  • blockers — string — Known blockers or concerns
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • current_stage — string — Current deal stage
  • your_solution — string — What you are selling
  • buyer_champion — string — Champion name and title
  • economic_buyer — string — Economic buyer name and title
  • known_requirements — string — Known requirements or evaluation criteria
  • known_process_steps — string — Known steps in their buying process
  • procurement_contact — string — Procurement contact if known
  • technical_evaluators — string — Technical evaluators involved

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• win_loss_analyzer read-only

  Writes a short win/loss review of one deal, a competitor pattern or a set of deals from the details you give. Returns a write-up in plain sentences that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then the questions for the review call and sector notes. It adds no figure or reason you did not give, and says plainly what the outcome or reason would add when it is missing.

  Parameters:

  • analysis_type (required) — string — Type of analysis
  • deal_value — number — Deal value
  • loss_reason — string — Stated loss reason (for lost deals)
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • deal_details — string — Deal details, can be rough notes, CRM export, or structured data
  • deal_outcome — string — Deal outcome for single deal analysis
  • your_solution — string — What you were selling
  • competitor_won — string — Competitor who won (if applicable)
  • multiple_deals — string — For portfolio analysis: summary of multiple deals
  • sales_cycle_days — number — Length of sales cycle
  • stakeholders_involved — string — Key stakeholders and their positions

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• proposal_section_writer read-only

  Writes the proposal section you choose, such as an executive summary, solution overview or pricing justification, for a named buyer. Returns the section as sentences built from your solution, the buyer's challenges, your differentiators, pricing and success measures, with sector notes. It invents no figure, customer or date, and says once which inputs were not given.

  Parameters:

  • section_type (required) — string — Proposal section to generate
  • your_solution (required) — string — Your product/solution
  • tone — string — Tone for the proposal (changes only the opening of the executive summary)
  • pricing — string — Pricing details if relevant
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • customer_name — string — Customer name
  • success_metrics — string — Expected outcomes/metrics
  • primary_audience — string — Adds a one-line note at the top of the executive summary on what this audience looks for
  • customer_industry — string — Customer industry
  • customer_challenges — string — Key challenges identified
  • key_differentiators — string — Why you vs alternatives
  • implementation_approach — string — How you will implement

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• email_sequence_generator read-only

  Writes a multi-email sequence by persona, stage and objective, such as prospecting, nurture, follow-up or re-engagement. Returns each email with its subject, send day and body, built from your solution, the pain point, the value proposition, your proof and the ask, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented.

  Parameters:

  • sequence_type (required) — string — Type of email sequence. cold_outreach, warm_follow_up, post_demo and re_engagement have their own templates; the other types return a general outline
  • target_persona (required) — string — Target persona (e.g., VP Sales, CTO, CFO)
  • your_solution (required) — string — Your product/solution
  • tone — string — Email tone
  • num_emails — number — Accepted but not used yet: each sequence type has a fixed number of emails
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • social_proof — string — Customer names, stats, or proof points
  • call_to_action — string — Desired action (meeting, demo, reply)
  • key_value_prop — string — Primary value proposition
  • sender_context — string — Context about sender (role, shared connections, etc.)
  • target_industry — string — Target industry for context
  • specific_pain_point — string — Specific pain point to address

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• demo_script_builder read-only

  Writes a demo script for the demo type, persona and use case you choose. Returns a timed run from opening to close, with spoken lines and a step for each feature you must show, tied to the pains you name, then discussion, close and follow-up lines and sector notes. The steps come from the parts of your solution and your pains, and the answer says where they came from and what it did not get.

  Parameters:

  • demo_type (required) — string — Type of demo
  • your_solution (required) — string — Your product/solution
  • attendees — string — Other attendees and their roles
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • demo_duration — number — Demo duration in minutes
  • desired_outcome — string — What you want to achieve from this demo
  • key_pain_points — string — Pain points to address in demo
  • known_objections — string — Known objections to address
  • primary_audience — string — Primary demo audience (role/persona)
  • customer_industry — string — Customer industry
  • competitor_context — string — Competitor being displaced or compared
  • must_show_features — string — Features that must be demonstrated

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• pricing_negotiation_guide read-only

  Get value-based pricing defense strategies and negotiation tactics. Helps maintain deal value while addressing discount requests.

  Parameters:

  • scenario (required) — string — Negotiation scenario
  • deal_value — number — Current deal value
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • your_leverage — string — Your leverage points (unique features, timeline, etc.)
  • your_solution — string — Your product/solution. Named in the guide and used, with your leverage, to read the sector and how you charge
  • business_model — string — Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out
  • buyer_leverage — string — Buyer leverage points (size, reference potential, etc.)
  • value_delivered — string — Quantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own
  • competitor_price — string — Competitor pricing if known
  • decision_timeline — string — When decision needs to be made
  • approval_authority — string — Who has final approval on pricing
  • discount_requested — number — Discount percentage requested

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• champion_enablement_kit read-only

  Writes an internal selling asset for your champion, such as an executive brief, an internal business case, objection responses or presentation talking points, built from your solution, the customer's situation and the objections you expect. Returns the asset in the champion's voice with the recommendation, the answers to likely questions, the decision requested, a note on the reader and sector notes. It invents no figure or quote.

  Parameters:

  • asset_type (required) — string — Type of enablement asset
  • your_solution (required) — string — Your product/solution
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • champion_name — string — Champion name
  • champion_role — string — Champion role/title
  • champion_wins — string — How this makes the champion look good
  • budget_context — string — Budget situation and pricing
  • urgency_drivers — string — Why act now
  • key_value_points — string — Key value points to emphasize
  • known_objections — string — Expected objections from stakeholders
  • target_stakeholder — string — Who the champion needs to convince
  • competitive_context — string — Competitive alternatives being considered

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• competitive_trap_setter read-only

  Writes landmine questions and positioning tactics against a named competitor, so the buyer's own criteria expose its weak points without negative selling. Returns the set-up, your strengths and the competitor's weak points as you gave them, discovery questions, criteria to establish, reference call questions, requirement and scenario traps, commercial terms and stage-specific tactics, with sector notes. Every line comes from your inputs and the sector, and none from an invented fact about the competitor.

  Parameters:

  • competitor (required) — string — Primary competitor to position against
  • your_solution (required) — string — Your product/solution
  • trap_type — string — Type of competitive positioning
  • your_sector — string — Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
  • buyer_persona — string — Role of key evaluator
  • business_model — string — Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out
  • your_strengths — string — Your key differentiators
  • buyer_priorities — string — What the buyer cares most about
  • evaluation_stage — string — Stage of competitive evaluation
  • competitor_weaknesses — string — Known competitor weaknesses

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.