# North Star Metric Modeler MCP > North Star Metric Modeler takes your vague company goals and maps them into quantifiable action plans. It lets you break down a single metric—like Monthly Active Users—into structural components, allowing you to predict exactly how improvements in areas like Engagement or Retention will impact the final number. ## Overview - **Category:** analytics - **Price:** Free - **Tags:** metrics, north-star, growth-modeling, strategic-planning, simulation ## Description Figuring out how to grow is usually about guesswork until you build a model. This MCP helps bridge that gap by turning high-level objectives into weighted, measurable driver trees. You start by setting a clear target using your current performance data and defining what success looks like for your business. From there, the system lets you map structural relationships among key pillars—things like Acquisition, Activation, or Monetization—and assign weights to them so they accurately reflect how they contribute to the North Star Metric. Once that framework is set, you can run simulations. You don't have to guess; you just tell it which pillar improved by a certain percentage, and it predicts your new overall metric value. If you're stuck trying to figure out where to focus resources, this tool analyzes every component to show exactly which levers are most critical for closing the gap between where you are now and where you want to be. It’s the strategic planning engine that helps turn ambition into a clear, actionable roadmap; Vinkius hosts this MCP so your agent can access it directly from any compatible client. ## Tools ### set_north_star_goal Establishes your primary metric, defining both your current performance and the desired target milestone. ### simulate_lever_improvement Predicts your overall metric's impact based on a specified percentage improvement within one of the defined pillars. ### calculate_contribution_distribution Analyzes and reports which specific pillar is most responsible for closing the gap between current performance and goal. ### configure_driver_tree Structures how key pillars relate to the North Star Metric and assigns weights, ensuring the total weight equals 100%. ## Prompt Examples **Prompt:** ``` I have 10,000 Monthly Active Users and my goal is 25,000. How much growth do I need? ``` **Response:** ``` To reach your target of 25,000 from 10,000, you require a total growth of 15,000 users, which represents a 150% increase. ``` **Prompt:** ``` If I improve my Retention pillar by 20%, what will be the new North Star Metric value? ``` **Response:** ``` A 20% improvement in your Retention pillar will result in a projected North Star Metric of 12,500 users. ``` **Prompt:** ``` Which pillars are contributing most to my growth gap? ``` **Response:** ``` Based on your current configuration, the Acquisition pillar is responsible for 40% of the required growth, followed by Engagement at 30%. ``` ## Capabilities ### Establish Target Goals Sets the primary metric and target milestone for strategic planning. ### Map Driver Relationships Defines how core business pillars influence the overall North Star Metric using weighted relationships. ### Forecast Impact Predicts changes in the final metric based on specific, simulated improvements to any pillar. ### Identify Bottlenecks Analyzes current data to determine which pillars contribute the most to achieving a larger goal. ## Use Cases ### The Retention Strategy Meeting A Product Manager needs to prove that investing in better onboarding flow is worth the cost. They use set_north_star_goal to define their target increase, configure_driver_tree to establish 'Activation' as a key pillar, and then run simulate_lever_improvement by boosting the Activation metric by 15%. The agent returns a projected lift of 8,000 users. ### Budget Allocation Review The Marketing Director needs to argue for more funding for Content creation. They run calculate_contribution_distribution against their goal and discover that 'Content' (part of Engagement) is responsible for 45% of the required growth, giving them hard evidence for increased spending. ### Defining New Business Lines A CSO wants to know if a new monetization pillar makes sense. They use configure_driver_tree to add 'Monetization' and assign a weight of 10%. Then, they run simulate_lever_improvement, showing that the combined lift is sufficient to meet their goal. ### Post-Quarter Performance Review After reviewing poor performance, an executive asks which area needs immediate attention. They use calculate_contribution_distribution against the existing structure and immediately see that 'Engagement' has a contribution of only 15%, signaling where all resources must shift. ## Benefits - Pinpoint resource gaps instead of guessing. Use calculate_contribution_distribution to see precisely which pillar is holding back your growth, eliminating wasted effort on low-impact areas. - Test strategies risk-free. Simulate a 20% boost in Retention using simulate_lever_improvement and instantly know the projected impact on your North Star Metric without building anything first. - Build structured strategy. Use configure_driver_tree to formally map how all parts of your business—Acquisition, Engagement, etc.—fit together into one cohesive growth model. - Set a clear destination. Start every project by defining a measurable objective using set_north_star_goal, giving your entire team a single source of truth for success metrics. - Accelerate decision-making. Instead of holding multiple meetings to debate priority, run the numbers and let calculate_contribution_distribution provide an data-driven answer. ## How It Works The bottom line is you get a quantifiable plan showing exactly which internal changes will move the needle most effectively. 1. First, define your target by setting the core North Star Metric and desired end state. 2. Next, map out the structural relationships between key business pillars and assign weights to show their influence on that metric. 3. Finally, run a simulation or distribution analysis using your agent to predict outcomes based on hypothetical improvements. ## Frequently Asked Questions **How does set_north_star_goal work with other tools?** set_north_star_goal defines the single, overarching target. Every subsequent tool—like configure_driver_tree or simulate_lever_improvement—uses this defined goal as its anchor point for all calculations. **Can I use calculate_contribution_distribution without first setting a North Star Goal?** No. The distribution analysis must reference a target gap to be meaningful. You need set_north_star_goal to define the current state versus the desired end state before calculating contribution. **What if I change my core metric? Do I have to reconfigure everything?** Yes. If you change your North Star Metric, you must first update it using set_north_star_goal and then rerun configure_driver_tree to correctly reflect the new structural dependencies. **What does simulate_lever_improvement calculate?** It predicts the total impact on your North Star Metric if you increase a specific pillar (like Activation) by a certain percentage, based on the weights established in the driver tree. **If I use `configure_driver_tree` and my pillar weights don't sum to 100%, what happens?** The MCP will throw a structural validation error. The tool requires the total weight of all defined pillars (Acquisition, Engagement, etc.) to exactly equal 100% for the model to run correctly. **When I call `set_north_star_goal`, do I need to provide historical performance data?** No. You only input your current metric value and your desired target milestone. The MCP handles calculating the required delta based on those two figures. **Can `simulate_lever_improvement` accept both percentage increases and absolute user counts for pillar gains?** Yes, it accepts both formats. You can provide a raw number or a percentage increase; the MCP scales the input correctly according to your configured driver weights. **If my North Star Metric already meets its target, how does `calculate_contribution_distribution` respond?** It will run successfully and report that zero contribution is needed. It confirms you've closed the gap without assigning any required growth percentage to specific pillars.