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-mcpversion 2.1.0. - Local use:
npx -y @shashwatgtmalpha/craft-gtm-mcpruns the same tools over stdio.
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.
curl -s -X POST https://craft-gtm.gtmhelix.com/api/tools/pmf_scorecard \
-H "Content-Type: application/json" \
-d '{"input": {"product": "ClinicFlow, scheduling software for clinics", "target_market": "smb_saas", "current_metrics": "MRR: $40K, Churn: 4%, NPS: 38, CAC: $600, LTV: $4200, Retention: 90%", "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, 429 when the rate limit is reached, 500 if the tool fails. - Limits: 30 requests per minute per IP address; text fields up to 6,000 characters; lists up to 50 items.
- Forms without JavaScript post
application/x-www-form-urlencodedand get an HTML page back. - Nothing is stored and the input is not logged (see Privacy).
Tool reference
Generated from the server's own input schemas on 25 September 2026.
PMF Scorecard pmf_scorecard
Generate a Product-Market Fit scorecard. Parses the metrics you provide (MRR, churn, NPS, CAC, LTV, retention, activation and similar) and scores each dimension against built-in benchmark ranges. Open the form.
| 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, healthtech, 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') |
Launch Commander launch_commander
Generate a context-aware launch plan. Have a date? Get a detailed timeline. Still planning? Enter 'TBD' or 'Q2 2025' for a flexible plan. Open the form.
| 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 2025', 'March 2025', 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 |
Customer Interview Kit customer_interview_kit
Generate interview guides that ADAPT based on interview type, industry, and product complexity. Includes synthesis templates. Open the form.
| 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, healthtech, 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 |
Retention Playbook retention_playbook
Generate retention strategies. Has DISCOVERY MODE - if you don't know WHY people churn, get a churn analysis framework first. Open the form.
| 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 |
Partner Architect partner_architect
Design partner programs that ADAPT based on partner model type. Different structures for resellers vs referrals vs integrations vs affiliates. Open the form.
| 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 (determines viable commission rates). E.g., '$5000 ACV' or '$500/month' | |
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 |
Crisis Planner crisis_planner
Generate crisis playbooks. Know your risks? Get specific playbooks. Not sure what to plan for? We'll suggest the top crises for your industry. Open the form.
| Field | Type | Required | Allowed values | Meaning |
|---|---|---|---|---|
company | string | yes | Company name | |
industry | string | yes | fintech, healthtech, saas, 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, we'll suggest the top 4 crises for your industry. 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 (GDPR, HIPAA, SOC2, etc.) |
Competitive Intel competitive_intel
Generate battle cards. If you know your strengths/weaknesses, get complete battle cards. If you only know competitors and win/loss stories, we'll derive your positioning. Open the form.
| 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., 'Competitor A is cheaper, Competitor B 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 |
CRAFT GTM Analyzer craft_gtm_analyzer
Analyze a GTM document against the CRAFT framework. Parses the content, identifies gaps, scores each dimension and suggests sections to add. Open the form.
| 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 |