-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Context
For AI developer audiences, the MCP tool itself is the top of the marketing funnel:
Discover MCP → Install → Use tools → See footprint → Subscribe
We need to optimize this path so that free MCP users convert to paid subscribers at a higher rate.
Ideas to Explore
In-tool nudges (subtle, not spammy)
- After
estimate_session_footprint, include a brief CTA: "Subscribe for $1.25/mo to offset this automatically → compute.regen.network" check_subscription_statusfor non-subscribers should return a compelling summary of what subscribers get (impact numbers, dashboard access, certificates)- Consider a
show_my_impactor similar tool that shows non-subscribers what they would have funded this month based on their usage
Frequency/tone
- Nudges should NOT appear on every tool call — that would be annoying and hurt the free experience
- Maybe every Nth footprint estimate, or only when cumulative unoffset footprint crosses a threshold
- Tone should be informational, not guilt-driven: "Your session used ~X kWh. Subscribers offset this for $1.25/mo."
Free experience quality
- The free tools should be genuinely useful — good estimates, interesting credit browsing, real certificate lookups
- If the free experience feels valuable, conversion is natural
- If it feels like a nag-wall, people uninstall
Metrics to track
- MCP installs (how do we even measure this currently?)
- Tool call frequency per user (can we distinguish subscribed vs. free?)
- Conversion rate from MCP install to subscription
- Time-to-convert (how many sessions before someone subscribes?)
Open questions
- Can we identify MCP users who aren't subscribed? (API key vs. anonymous usage)
- Should there be a "free tier" with limited tool calls that upgrades to paid?
- What does the Claude MCP marketplace listing look like — is the description optimized?
Acceptance Criteria
- Audit current MCP tool responses for conversion opportunities
- Design nudge strategy with frequency limits
- Implement at least one conversion touchpoint in tool responses
- Add tracking for MCP-to-subscription conversion if feasible
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels