For developers
Revenue Enablement docs
For developers and marketing operations teams. The decision: how to call Revenue Enablement from your own code or assistant.
This page covers the MCP address, the REST API behind the web forms and every input field of all 12 tools.
Try these prompts
- Use Revenue Enablement to build an account plan for a third party logistics customer paying $36,000 a year for our route planning.
- Use Revenue Enablement to give me a MEDDPICC discovery question bank for a discovery call with a head of last mile operations at a third party logistics company.
- Create a mutual action plan with Revenue Enablement for the logistics expansion deal, target close date 2026-12-15, currently in evaluation.
MCP server
- Address:
https://revenue-enablement.gtmhelix.com/mcp(Streamable HTTP, stateless, JSON responses). GET returns 405 by design. - Authentication: none. Every tool is marked read only (
readOnlyHint: true,destructiveHint: false) and has a title. - Rate limit: 300 requests per minute per IP address. Server:
revenue-enablement-mcpversion 1.2.31. - Limits: 262,144 bytes per call; text fields up to 4,000 characters, except the document fields
known_contacts(Account Plan Builder),account_notes(Account Plan Builder) anddeal_details(Win/Loss Analyzer), which take up to 100,000; one call per request (no batches). A call over a limit is refused before the tool runs. - Local use:
npx -y @shashwatgtmalpha/revenue-enablement-mcpruns these tools over stdio (npm can lag behind this site until a new version is published).
REST API (used by the web forms)
Send POST https://revenue-enablement.gtmhelix.com/api/tools/<tool name> with a JSON body {"input": {...}}. The answer is JSON: {"ok": true, "tool": "...", "title": "...", "text": "..."}, where text is the same Markdown the MCP tool returns. The endpoint calls the same server code as the MCP address.
curl -s -X POST https://revenue-enablement.gtmhelix.com/api/tools/account_plan_builder \
-H "Content-Type: application/json" \
-d '{"input": {"account_name": "the logistics customer", "industry": "third-party logistics", "current_arr": 36000, "your_solution": "our product", "current_products": "our route planning in 3 of their 12 cities"}}'- Errors: 400 with
errors(missing or invalid fields), 404 for an unknown tool, 405 for methods other than POST, 413 above 32,000 bytes, 422 when the tool itself refuses the input (okis false anderrorholds the tool's message), 429 when the rate limit is reached, 500 if the tool fails. - Limits: 30 requests per minute per IP address; the whole request up to 32,000 bytes; top level text fields up to 6,000 characters and top level lists up to 50 items.
- Forms without JavaScript post
application/x-www-form-urlencodedand get an HTML page back. - Inputs and answers are not stored, and the input is not logged (see Privacy).
Release history
History: first released 17 January 2026, on npm and in the MCP Registry. Dates for npm and the MCP Registry come from their public records; later versions come from the commits in the GitHub repository. npm can lag behind this site until a new version is published.
| Version | Date | Where |
|---|---|---|
| 1.0.0 | 17 January 2026 | npm and the MCP Registry |
| 1.1.0 | 24 September 2026 | GitHub, commit a4d23ee |
| 1.2.0 | 26 September 2026 | GitHub, commit 19f723f |
| 1.2.1 | 26 September 2026 | GitHub, commit 769cbce |
| 1.2.2 | 27 September 2026 | GitHub, commit ba243cf |
| 1.2.3 | 27 September 2026 | GitHub, commit 0a5e4fa |
| 1.2.4 | 27 September 2026 | GitHub, commit ba724e2 |
| 1.2.5 | 27 September 2026 | GitHub, commit f0b9812 |
| 1.2.6 | 28 September 2026 | GitHub, commit d70dba1 |
| 1.2.7 | 28 September 2026 | GitHub, commit 6fc39b0 |
| 1.2.8 | 28 September 2026 | GitHub, commit eae9857 |
| 1.2.9 | 29 September 2026 | GitHub, commit c8375c2 |
| 1.2.10 | 29 September 2026 | GitHub, commit 93e4756 |
| 1.2.11 | 29 September 2026 | GitHub, commit 2cd7cc4 |
| 1.2.12 | 29 September 2026 | GitHub, commit 62cb780 |
| 1.2.13 | 29 September 2026 | GitHub, commit 33349e8 |
| 1.2.14 | 30 September 2026 | GitHub, commit fbf67f1 |
| 1.2.15 | 30 September 2026 | GitHub, commit 63b225e |
| 1.2.16 | 30 September 2026 | GitHub, commit 30e854f |
| 1.2.17 | 30 September 2026 | GitHub, commit 939b1a3 |
| 1.2.18 | 1 October 2026 | GitHub, commit 552b944 |
| 1.2.19 | 1 October 2026 | GitHub, commit 72bc033 |
| 1.2.20 | 2 October 2026 | GitHub, commit f608cb0 |
| 1.2.21 | 2 October 2026 | GitHub, commit e1fc180 |
| 1.2.24 | 11 October 2026 | safety fix only: the instruction echo safeguard; tool list and answers otherwise unchanged |
| 1.2.28 | 15 October 2026 | security update only: MCP SDK 1.31.0 (advisory GHSA-6qxp-vccf-f47h); tool list and answers unchanged |
| 1.2.30 | 16 October 2026 | security update: text you type is shown with a small backslash before characters that could start a link, image, tag or code, so it can never become live markup; tool list unchanged |
| 1.2.31 (this site) | 18 October 2026 | quality update: sector knowledge for the nine verticals on every tool; ROI without your own figures explains the method and asks for your numbers instead of an example figure; sub industry notes only when your own words name one; fixes to email subjects, demo steps and objection evidence |
Tool reference
Generated from the server's own input schemas, version 1.2.31.
Account Plan Builder
account_plan_builder
Helps you decide how to grow an account in the next 90 days. You give the account name, plus contacts, products, threats and notes if you have them. You get a strategic account plan: a power map with one row per contact you name, whitespace analysis, competitive questions, an answer for each objection and a 90 day plan. It does not look the account up. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
account_name | string | yes | Company/account name | |
industry | string | no | Industry vertical | |
current_arr | number (0 or more) | no | Current ARR with this account (0 for prospects) | |
known_contacts | string | no | Known contacts and their roles, one per line or separated by semicolons, for example: Head of RevOps (champion); CFO. Each entry becomes one row, so put other notes in account_notes | |
current_products | string | no | Products/services they currently use from you | |
expansion_opportunities | string | no | Potential expansion areas or whitespace | |
competitive_threats | string | no | Known competitors in the account | |
your_solution | string | no | Your product/service offering | |
account_notes | string | no | Any additional context about the account | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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 Strategy Coach
deal_strategy_coach
Helps you decide what to do next to move a deal. You give the deal name and stage, plus competitors, stakeholder positions and blockers. You get a deal health score, a strategy for the stage, next steps and risks to handle. Ask the user to confirm blocker status, economic buyer engagement, incumbent status and project status when those facts affect the score; typed facts take precedence over text. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
deal_name | string | yes | Deal/opportunity name | |
deal_value | number (0 or more) | no | Deal value in dollars | |
deal_stage | string | yes | prospecting, discovery, demo, proposal, negotiation, closing, stuck | Current deal stage |
days_in_stage | number (0 or more) | no | Days the deal has been in current stage | |
champion_status | string | no | no_champion, potential_champion, confirmed_champion, multi_threaded | Champion identification status |
economic_buyer | string | no | Economic buyer name and engagement level | |
competitors | string | no | Competitors in the deal and their position | |
blockers | string | no | Known blockers or objections | |
next_steps | string | no | Currently planned next steps | |
close_date | string | no | Target close date | |
your_solution | string | no | What you are selling | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Discovery Question Bank
discovery_question_bank
Helps you decide what to ask on a discovery call. You give the framework you use (MEDDPICC, BANT, SPICED, Challenger, Gap Selling or all five) and what you already know about the prospect. You get an opening for the conversation, questions in the language of the prospect's sector and on what your solution covers, questions for each part of the framework, a closing and what to say to an objection. It uses only the inputs you give and says which it did not get. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
framework | string | yes | meddpicc, bant, spiced, challenger, gap_selling, all | Discovery framework to use |
prospect_industry | string | no | Prospect industry for context | |
prospect_role | string | no | Role of person you are meeting with | |
known_pain_points | string | no | Pain points already identified | |
known_metrics | string | no | Metrics/KPIs already discussed | |
deal_stage | string | no | first_call, discovery, deep_dive, technical, executive | Stage of conversation |
your_solution | string | no | Your product/solution for relevant questions | |
gaps_to_fill | string | no | Specific information gaps to address | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
ROI Business Case Builder
roi_business_case_builder
Helps you build an ROI case the buyer's finance team can check. You give your solution, its main value driver and the buyer's own figures: an annual value estimate, or current annual cost with the expected improvement percent. With them you get 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). See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
customer_name | string | no | Customer/prospect name | |
industry | string | no | Industry for the example benchmarks: Technology, Financial_Services, Healthcare, Manufacturing or Retail (exact spelling). Any other value uses Technology | |
company_size | string | no | startup, smb, mid_market, enterprise | Company size tier |
annual_revenue | number (0 or more) | no | Customer annual revenue | |
employee_count | number (0 or more) | no | Number of employees | |
your_solution | string | yes | Your product/solution | |
solution_price | number (0 or more) | no | Annual cost of your solution | |
primary_value_driver | string | yes | revenue_increase, cost_reduction, productivity, risk_mitigation, multiple | Primary value category |
known_metrics | string | no | Metrics the prospect shared. Shown in the output; to turn them into the value, give current_annual_cost and expected_improvement_percent, or annual_value_estimate | |
current_annual_cost | number (0 or more) | no | Optional: what the problem or the current process costs the buyer a year, in dollars (their figure) | |
expected_improvement_percent | number (0 or more) | no | Optional: the share of that annual cost the buyer expects to save, in percent (their figure) | |
annual_value_estimate | number (0 or more) | no | Optional: the buyer's own estimate of the annual value in dollars; used as the value when given | |
current_process | string | no | How they do it today. Shown in the output; not used in the calculation | |
implementation_timeline | string | no | Expected implementation time. Shown in the output; not used in the calculation | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Mutual Action Plan Generator
mutual_action_plan_generator
Helps you decide what has to happen, by whom and when, for a deal to sign on time. You give the deal name and the target close date, plus the current stage, the buyer's champion, economic buyer and evaluators, known requirements and process steps if you have them. You get a close plan both sides can work from, with milestones, owners and dates. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
deal_name | string | yes | Deal/opportunity name | |
target_close_date | string | yes | Target close date (YYYY-MM-DD). A Saturday or Sunday date moves to the Friday before, and the plan says so | |
current_stage | string | no | discovery, evaluation, proposal, negotiation, procurement | Current deal stage |
buyer_champion | string | no | Champion name and title | |
economic_buyer | string | no | Economic buyer name and title | |
technical_evaluators | string | no | Technical evaluators involved | |
procurement_contact | string | no | Procurement contact if known | |
known_requirements | string | no | Known requirements or evaluation criteria | |
known_process_steps | string | no | Known steps in their buying process, separated by semicolons or new lines (for example: Pilot; security review; procurement). Each step becomes its own milestone | |
blockers | string | no | Known blockers or concerns | |
your_solution | string | no | What you are selling | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Win/Loss Analyzer
win_loss_analyzer
Helps you decide why you won or lost and what to change. You give the details of one deal, a competitor pattern or a set of deals. You get a short write up that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then questions for the review call and sector notes. It adds no figure or reason you did not give, and says what a missing outcome or reason would add. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
analysis_type | string | yes | single_deal, deal_portfolio, competitor_analysis, loss_pattern | Type of analysis |
deal_outcome | string | no | won, lost, no_decision, mixed | Deal outcome for single deal analysis |
deal_details | string | no | Deal details, can be rough notes, CRM export, or structured data | |
loss_reason | string | no | Stated loss reason (for lost deals) | |
competitor_won | string | no | Competitor who won (if applicable) | |
deal_value | number (0 or more) | no | Deal value | |
sales_cycle_days | number (0 or more) | no | Length of sales cycle | |
stakeholders_involved | string | no | Key stakeholders and their positions | |
your_solution | string | no | What you were selling | |
multiple_deals | string | no | For portfolio analysis: summary of multiple deals | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Proposal Section Writer
proposal_section_writer
Helps you write one section of a proposal for a named buyer. You give the section you need (such as an executive summary, solution overview or pricing justification), your solution, the buyer's challenges, your differentiators, pricing and success measures. You get that section in sentences built from your inputs, with sector notes. It invents no figure, customer or date, and says once which inputs were not given. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
section_type | string | yes | executive_summary, problem_statement, solution_overview, implementation_plan, pricing_justification, risk_mitigation, success_metrics, company_overview, case_studies, next_steps | Proposal section to generate |
customer_name | string | no | Customer name | |
customer_industry | string | no | Customer industry | |
primary_audience | string | no | c_suite, vp_level, director, manager, technical, procurement | Accepted but not used yet: the text is the same for every audience |
customer_challenges | string | no | Key challenges identified | |
your_solution | string | yes | Your product/solution | |
key_differentiators | string | no | Why you vs alternatives | |
pricing | string | no | Pricing details if relevant | |
implementation_approach | string | no | How you will implement | |
success_metrics | string | no | Expected outcomes/metrics | |
tone | string | no | formal, consultative, bold, conservative | Tone for the proposal (changes only the opening of the executive summary) |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Email Sequence Generator
email_sequence_generator
Helps you decide what to send, and when, to open or restart a conversation. You give the persona, stage and objective (prospecting, nurture, follow up or re engagement), plus your solution, the pain point, value proposition, proof and ask. You get each email with its subject, send day and body, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
sequence_type | string | yes | cold_outreach, warm_follow_up, post_demo, proposal_follow_up, re_engagement, nurture, event_follow_up, referral_request | 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 | string | yes | Target persona (e.g., VP Sales, CTO, CFO) | |
target_industry | string | no | Target industry for context | |
your_solution | string | yes | Your product/solution | |
key_value_prop | string | no | Primary value proposition | |
specific_pain_point | string | no | Specific pain point to address | |
social_proof | string | no | Customer names, stats, or proof points | |
call_to_action | string | no | Desired action (meeting, demo, reply) | |
num_emails | number (0 or more) | no | Accepted but not used yet: each sequence type has a fixed number of emails | |
tone | string | no | professional, casual, urgent, consultative, provocative | Email tone |
sender_context | string | no | Context about sender (role, shared connections, etc.) | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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 Script Builder
demo_script_builder
Helps you decide what to show in a demo, and in what order. You give the demo type, the persona and the use case, plus the features you must show and the pains you name. You get a timed run from opening to close, with spoken lines and a step for each feature tied to the pains, then discussion, close and follow up lines and sector notes. The answer says where each step came from and what it did not get. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
demo_type | string | yes | first_look, technical_deep_dive, executive_overview, competitive_displacement, expansion_upsell, proof_of_concept | Type of demo |
primary_audience | string | no | Primary demo audience (role/persona) | |
attendees | string | no | Other attendees and their roles | |
customer_industry | string | no | Customer industry | |
your_solution | string | yes | Your product/solution | |
key_pain_points | string | no | Pain points to address in demo | |
competitor_context | string | no | Competitor being displaced or compared | |
demo_duration | number (0 or more) | no | Demo duration in minutes | |
must_show_features | string | no | Features that must be demonstrated | |
known_objections | string | no | Known objections to address | |
desired_outcome | string | no | What you want to achieve from this demo | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Pricing Negotiation Guide
pricing_negotiation_guide
Helps you decide how to answer a discount request without giving away margin. You give the negotiation scenario, plus deal value, the discount asked, each side's leverage and who approves. You get a leverage assessment, a value based negotiation strategy, answers to common pushback and a discount approval framework. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
scenario | string | yes | discount_request, budget_objection, competitor_pricing, procurement_pressure, multi_year_negotiation, enterprise_agreement, renewal_negotiation | Negotiation scenario |
deal_value | number (0 or more) | no | Current deal value | |
discount_requested | number (0 or more) | no | Discount percentage requested | |
your_solution | string | no | Accepted but not used yet by this tool | |
competitor_price | string | no | Competitor pricing if known | |
value_delivered | string | no | Quantified value your solution delivers. Shown in the output; the value example does not use it | |
buyer_leverage | string | no | Buyer leverage points (size, reference potential, etc.) | |
your_leverage | string | no | Your leverage points (unique features, timeline, etc.) | |
decision_timeline | string | no | When decision needs to be made | |
approval_authority | string | no | Who has final approval on pricing | |
business_model | string | no | saas, services, connectivity, transactions, marketplace, hardware_software, investment | 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_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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 Enablement Kit
champion_enablement_kit
Helps you give your champion what they need to sell internally. You give the asset you need (an executive brief, internal business case, objection responses or presentation talking points), your solution, the customer's situation and the objections you expect. You get the asset in the champion's voice with the recommendation, answers to likely questions, the decision requested, a note on the reader and sector notes. It invents no figure or quote. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
asset_type | string | yes | executive_brief, internal_business_case, objection_responses, presentation_talking_points, email_to_stakeholder, roi_one_pager, competitive_comparison, risk_assessment | Type of enablement asset |
champion_name | string | no | Champion name | |
champion_role | string | no | Champion role/title | |
target_stakeholder | string | no | Who the champion needs to convince | |
your_solution | string | yes | Your product/solution | |
key_value_points | string | no | Key value points to emphasize | |
known_objections | string | no | Expected objections from stakeholders | |
competitive_context | string | no | Competitive alternatives being considered | |
budget_context | string | no | Budget situation and pricing | |
urgency_drivers | string | no | Why act now | |
champion_wins | string | no | How this makes the champion look good | |
your_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
Competitive Trap Setter
competitive_trap_setter
Helps you decide which questions expose the gaps in your main competitor, without negative selling. You give the named competitor, your solution, your strengths and its weak points as you know them. You get the set up, discovery questions, criteria to establish, reference call questions, requirement and scenario traps, commercial terms and tactics for your stage, with sector notes. Every line comes from your inputs and the sector, and none from an invented fact about the competitor. See what it does.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
competitor | string | yes | Primary competitor to position against | |
competitor_weaknesses | string | no | Known competitor weaknesses | |
your_solution | string | yes | Your product/solution | |
your_strengths | string | no | Your key differentiators | |
evaluation_stage | string | no | early, mid, late, finalist | Stage of competitive evaluation |
buyer_priorities | string | no | What the buyer cares most about | |
buyer_persona | string | no | Role of key evaluator | |
trap_type | string | no | discovery_questions, evaluation_criteria, reference_questions, technical_requirements, commercial_terms, all | Type of competitive positioning |
business_model | string | no | saas, services, connectivity, transactions, marketplace, hardware_software, investment | 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_sector | string | no | logistics_tech, fintech, saas, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other | 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. |
How to read the answer
Both the MCP server and the REST endpoint return the same structured Markdown text for a given input object. Inside the returned Markdown, figures calculated from your inputs are shown directly, bracketed placeholders mark missing facts, and any unprovided benchmark is labelled as an example figure.
What to do next
- Founder: Test Account Plan Builder, Discovery Question Bank, or ROI Business Case Builder via the MCP endpoint or REST API with your real deal details.
- CEO: Review the input fields for ROI Business Case Builder, Mutual Action Plan Generator, and Win/Loss Analyzer so your team supplies real buyer numbers.
- CMO: Use the schemas for Email Sequence Generator, Champion Enablement Kit, and Competitive Trap Setter to standardize campaign and enablement briefs.
- CRO: Check the fields for Deal Strategy Coach, Pricing Negotiation Guide, and Account Plan Builder so sellers pass complete deal context.
- Demand generation head: Pass your target persona, industry, and pain points into Email Sequence Generator and Discovery Question Bank.
Why come back
Come back when you wire Revenue Enablement into an internal workflow, check allowed enum values, or review the release history. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Choose your app
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh