For developers

CRAFT GTM docs

For developers and marketing operations teams. The decision: how to call CRAFT GTM 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 8 tools.

By Shashwat Ghosh, Co-Founder and Fractional CMO, Helix GTM Consulting · Last updated 2 November 2026

Try these prompts

Use CRAFT GTM to score our product market fit. Product: our field sales app for consumer goods brands and their distributors; target market: enterprise SaaS. Metrics: MRR $60K, churn 1.5% monthly, NPS 44, CAC $9,000, LTV $72,000.
Build a launch plan with CRAFT GTM for our new order suggestions for field reps, a feature launch on 2026-11-15, for packaged food and personal care brands. Goals: 40 brand demos and $300K pipeline.
Create a customer interview kit for churn interviews with heads of sales operations at consumer goods brands about our field sales app.
Use CRAFT GTM to make battle cards for our product against your first competitor and your second competitor. Recent wins: offline order capture. Recent losses: buyers wanted billing and sales in one system.

MCP server

Address: https://craft-gtm.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: craft-gtm-mcp version 2.2.23.
Limits: 262,144 bytes per call; text fields up to 4,000 characters, except the document fields document_content (CRAFT GTM Analyzer) and competitor_details (Competitive Intel), which take up to 100,000 characters; one call per request (no batches). A call over a limit is refused before the tool runs.
Local use: npx -y @shashwatgtmalpha/craft-gtm-mcp runs 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://craft-gtm.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.

Terminal

curl -s -X POST https://craft-gtm.gtmhelix.com/api/tools/pmf_scorecard \
  -H "Content-Type: application/json" \
  -d '{"input": {"product": "our field sales app for consumer goods brands and their distributors", "target_market": "enterprise_saas", "current_metrics": "MRR: $60K, Churn: 1.5%, NPS: 44, CAC: $9000, LTV: $72000, Retention: 95%", "time_in_market": "1_2_years"}}'

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 (ok is false and error holds 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-urlencoded and get an HTML page back.
Inputs and answers are not stored, and the input is not logged (see Privacy).

Release history

History: first released 16 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	16 January 2026	npm
1.0.1	16 January 2026	npm and the MCP Registry
2.0.0	16 January 2026	npm
2.0.1	16 January 2026	npm
2.1.0	24 September 2026	GitHub, commit bcf9b59
2.2.0	26 September 2026	GitHub, commit 810815b
2.2.1	26 September 2026	GitHub, commit efa1f98
2.2.2	27 September 2026	GitHub, commit c5853fa
2.2.3	27 September 2026	GitHub, commit 630753d
2.2.4	27 September 2026	GitHub, commit 895828a
2.2.5	27 September 2026	GitHub, commit 5c2b706
2.2.6	28 September 2026	GitHub, commit 2825d23
2.2.7	28 September 2026	GitHub, commit 1867d8f
2.2.8	28 September 2026	GitHub, commit 2117b89
2.2.9	29 September 2026	GitHub, commit 175d219
2.2.10	29 September 2026	GitHub, commit 00bc46a
2.2.11	29 September 2026	GitHub, commit 168f785
2.2.12	30 September 2026	GitHub, commit cd4c9ba
2.2.13	30 September 2026	GitHub, commit 9a6b8b8
2.2.16	12 October 2026	safety fix only: the instruction echo safeguard; tool list and answers otherwise unchanged
2.2.20	15 October 2026	security update only: MCP SDK 1.31.0 (advisory GHSA-6qxp-vccf-f47h); tool list and answers unchanged
2.2.22	17 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
2.2.23 (this site)	17 October 2026	quality update: sector knowledge for the nine verticals on all eight tools; new optional input your_sector (your own industry); sub industry notes only when your own words name one; healthtech removed from the industry lists; a usage count per tool (no text you type is kept)

Tool reference

Generated from the server's own input schemas, version 2.2.23.

PMF Scorecard

pmf_scorecard

Helps you decide whether you have product market fit and whether to scale: it takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a scorecard that scores each dimension against example benchmark ranges. It also gives priority actions and the data gaps to fill, reads the business model from your inputs, leaves the activation score out for services, connectivity and investment businesses, and quotes and answers your customer feedback. See what it does.

Field	Type	Required	Allowed values	Meaning
`product`	string	yes		Product name and brief description
`target_market`	string	yes	enterprise_saas, smb_saas, consumer, marketplace, fintech, logistics_tech, vertical_saas, ai_native, ites, telecom, software, cybersecurity, other	Target market segment (e.g., 'Enterprise SaaS', 'SMB', 'Consumer')
`current_metrics`	string	yes		Your current metrics (will be PARSED). Include any of: MRR, ARR, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'
`time_in_market`	string	no	pre_launch, 0_6_months, 6_12_months, 1_2_years, 2_plus_years	How long the product has been in market (shown in the scorecard)
`customer_feedback`	string	no		Optional: Qualitative feedback themes (e.g., 'Users love X but struggle with Y')
`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.

Launch Commander

launch_commander

Helps you decide your launch plan: it takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and messaging follow the sector and business model read from your inputs, and each goal is filed under its own metric. See what it does.

Field	Type	Required	Allowed values	Meaning
`product_feature`	string	yes		What you're launching (product/feature name and description)
`launch_date`	string	no		Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode
`launch_type`	string	yes	major_release, feature_launch, beta_launch, product_update, market_expansion	Type of launch determines plan complexity
`target_segments`	string	yes		Target customer segments (comma-separated)
`goals`	string	yes		Launch success metrics (e.g., '500 signups, $50k pipeline, 10% trial conversion, 1000 downloads')
`available_channels`	string	no		Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'
`team_size`	string	no	solo, small_2_5, medium_6_15, large_15_plus	Marketing/GTM team size affects task distribution
`budget_level`	string	no	bootstrap, moderate, well_funded	Budget affects recommended tactics
`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.

Customer Interview Kit

customer_interview_kit

Helps you decide what to ask customers to test your hunch: it takes the interview type, the product context and the person you are interviewing, and returns an interview guide that fits the interview type, the sector and the product complexity. Questions use the sector's own language (the sector is chosen, or read from your inputs), your hypotheses are kept whole, and synthesis templates are included. See what it does.

Field	Type	Required	Allowed values	Meaning
`interview_type`	string	yes	discovery, validation, feedback, churn, win_loss, persona_research	Type of interview determines question focus
`product_context`	string	yes		Product/service being researched
`industry`	string	no	saas, fintech, logistics_tech, vertical_saas, ai_native, ites, telecom, software, cybersecurity, ecommerce, marketplace, enterprise_software, consumer, other	Industry affects terminology and context
`product_complexity`	string	no	simple, moderate, complex, highly_technical	Affects technical depth of questions
`target_persona`	string	yes		Who you're interviewing (role/title)
`key_hypotheses`	string	no		Optional: Hypotheses to validate during interview
`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.

Retention Playbook

retention_playbook

Helps you decide why customers leave and what to do about each reason: it takes your customer segment, business model and current churn rate, and returns a retention playbook with health signals, interventions and an email draft for each churn reason. If you do not know why customers leave, leave the churn reasons out and you get a churn discovery kit instead. Your current interventions and data signals are used when you give them. See what it does.

Field	Type	Required	Allowed values	Meaning
`customer_segment`	string	yes		Customer segment to focus on
`business_model`	string	yes	saas_subscription, usage_based, marketplace, transactional, freemium, enterprise_contract	Business model affects health score weighting
`current_churn_rate`	string	yes		Current churn rate (e.g., '5%' or '5% monthly')
`churn_reasons`	string	no		OPTIONAL: Known churn reasons (comma-separated). If you don't know, leave blank to get discovery mode with churn analysis framework
`available_data_signals`	string	no		What usage data you can track (comma-separated). E.g., 'login frequency, feature usage, support tickets, NPS responses'
`cs_team_size`	string	no	no_dedicated_cs, small_1_3, medium_4_10, large_10_plus	CS team capacity affects intervention strategy
`current_interventions`	string	no		Optional: What retention tactics you already do
`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.

Partner Architect

partner_architect

Helps you decide what partner program to run and how to start it: it takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs. The structure differs for resellers, referrals, integrations, agencies, affiliates and white label, uses your existing partners when given, and names the partner types that fit your sector's buying committee. See what it does.

Field	Type	Required	Allowed values	Meaning
`company`	string	yes		Your company name
`product`	string	yes		Product partners will sell/integrate
`partner_model`	string	yes	reseller, referral, integration_tech, agency_si, affiliate, oem_white_label	Partner type determines program structure
`partner_goals`	string	yes		Revenue/growth targets from partners
`your_deal_size`	string	yes		Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed
`partner_support_capacity`	string	no	minimal_self_serve, moderate, high_touch	How much partner support can you provide?
`existing_partners`	string	no		Optional: Current partner types/count
`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.

Crisis Planner

crisis_planner

Helps you decide who does what when a crisis hits: it takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks; without them it uses a default set of common crises for your sector, not ranked by likelihood. Each compliance item you list is used in the notification steps. See what it does.

Field	Type	Required	Allowed values	Meaning
`company`	string	yes		Company name
`industry`	string	yes	fintech, saas, logistics_tech, vertical_saas, ai_native, ites, telecom, software, cybersecurity, ecommerce, enterprise, consumer, other	Industry affects which crises to prioritize
`customer_base`	string	yes	b2b_enterprise, b2b_smb, b2c_consumer, mixed	Customer type affects communication approach
`data_sensitivity`	string	yes	high_pii_financial, medium_business_data, low_general	Data sensitivity affects security protocols
`potential_crises`	string	no		OPTIONAL: Crisis types to plan for (comma-separated). If not provided, the tool uses a default set of common crises for your industry (not ranked by likelihood). Options: data_breach, service_outage, pr_incident, executive_departure, security_vulnerability, regulatory_action, product_safety, customer_data_exposure
`company_size`	string	no	startup_under_50, scaleup_50_200, midsize_200_1000, enterprise_1000_plus	Affects response team structure
`compliance_requirements`	string	no		Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps
`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 Intel

competitive_intel

Helps you decide how to win against each competitor: it takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses stay in your own words. See what it does.

Field	Type	Required	Allowed values	Meaning
`your_product`	string	yes		Your product name and brief description
`competitors`	string	yes		Competitor names (comma-separated). Will generate battle card for EACH
`your_strengths`	string	no		OPTIONAL: What you do better (comma-separated). Will be DERIVED from wins/losses if not provided
`your_weaknesses`	string	no		OPTIONAL: Where competitors beat you (comma-separated). Will be DERIVED from wins/losses if not provided
`competitor_details`	string	no		Optional: Any known details about competitors. E.g., 'your first competitor is cheaper, your second competitor targets enterprise'
`common_objections`	string	no		Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'
`recent_wins`	string	no		Why customers chose you over competitors: will be used to DERIVE strengths
`recent_losses`	string	no		Why you lost deals to competitors: will be used to DERIVE weaknesses
`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.

CRAFT GTM Analyzer

craft_gtm_analyzer

Helps you decide whether a GTM plan is clear enough to run: it takes the text of a GTM document or plan and returns a score for each CRAFT dimension, based only on what the plan contains. Timeline counts real dates, durations and quarters; the answer shows the plan's own line for each dimension, names only the elements that are missing and suggests sections to add. See what it does.

Field	Type	Required	Allowed values	Meaning
`document_content`	string	yes		The GTM document/plan to analyze. Paste full content: it will be PARSED and EVALUATED
`document_type`	string	yes	gtm_strategy, launch_plan, campaign_brief, quarterly_plan, project_proposal, marketing_plan	Type of document (shown in the analysis)
`intended_audience`	string	no		Optional: Who will read/approve this document
`desired_outcome`	string	no		Optional: What action should this document drive
`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, scores are calculated from fixed rules, bracketed placeholders mark missing facts, and any unprovided benchmark is labelled as an example figure.

What to do next

Founder: Test PMF Scorecard or Customer Interview Kit via the MCP endpoint or REST API with your real segment metrics.
CEO: Review the input fields for PMF Scorecard, Partner Architect, and Crisis Planner so your team supplies complete facts before scoring.
CMO: Use the schemas for Launch Commander, Competitive Intel, and CRAFT GTM Analyzer to standardize launch and competitive briefs.
CRO: Check the fields for Competitive Intel and Partner Architect so sellers and partner managers include real deal and competitor details.
Demand generation head: Pass your real launch type, channels, and retention signals into Launch Commander and Retention Playbook.

Why come back

Come back when you integrate CRAFT GTM into an internal workflow, check allowed enum values, or review the latest release notes. 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