Back to GrowthDex
Growth idea action plan

MCP server before custom agent

Expose the product through an MCP server first so developers can use it in their own agent workflows before you invest in a full in-app agent.

rare tactic
Best-fit channelAI Search · Developer Tools · Product
Stage + contextai products · distribution · demand validation · developer adoption
BudgetMediumbudget tier
Suggested operator signalQualified search visitors who complete the intended next action

Why this can grow a startup

A full agent can hide whether users truly want agentic help or just easier product access. An MCP server gives technical users an immediate way to pull the product into real workflows, while giving the product team a cleaner demand signal. It also avoids overbuilding UI and orchestration before the company knows which agent jobs people repeat often enough to deserve a native surface.

Source-backed example

PostHog says its MCP server was used as much as PostHog AI for some creation flows, with 34% of AI-created dashboards coming through MCP and 18% of all dashboards created that way in one observed week.

Source-reported evidence

Source: PostHog Newsletter · Browse PostHog Newsletter tactics

34% of dashboards created by AI were done through PostHog's MCP server, equal to 18% of all dashboards created that week.

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Source discovered: May 26, 2026

AI SearchDeveloper ToolsProductai productsdistributiondemand validationdeveloper adoption
GrowthDex operator note

When to use it

Use this when AI Search, Developer Tools, Product is relevant to ai products, distribution, demand validation and you can run a bounded test with a medium budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to AI Search and Developer Tools, using evidence from PostHog Newsletter as context—not as a promised result.
  3. Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian

SOURCE HUB

More tactics from PostHog Newsletter

Explore related GrowthDex examples and evidence connected to PostHog Newsletter.

Open PostHog Newsletter source hub