Guides8 min read

Best MCP Servers for Growth Engineers in 2026

Growth engineers sit at the intersection of product, data, and marketing — running experiments, analyzing funnels, and shipping features that move acquisition and retention metrics. These MCP servers give your AI access to analytics, A/B testing, CRM, and campaign data so you can ship faster and learn clearer.

By MyMCPTools Team·

Growth engineering is a high-velocity discipline. You run experiments, analyze results, ship follow-up features, and repeat — often across acquisition, activation, retention, and revenue simultaneously. The bottleneck is rarely ideas or engineering capacity; it's the time it takes to pull context from a fragmented tool stack before you can act on it.

MCP servers let your AI become a growth research assistant that can actually query your stack. Ask it to pull funnel data, summarize experiment results, check what segments converted, or draft a hypothesis from recent behavioral patterns. Here are the best MCP servers for growth engineers in 2026.

1. PostHog MCP Server — Product Analytics and Experimentation

PostHog combines product analytics, session recordings, feature flags, and A/B testing in a single platform — making it the natural hub for a growth engineer's workflow. The PostHog MCP server gives your AI access to all of it, so you can query behavioral data and experiment results in one conversation.

Key capabilities:

  • Query funnel conversion rates by step, cohort, and segment
  • Read A/B test results and statistical significance assessments
  • Access feature flag configurations and rollout percentages
  • Pull retention curves and cohort analysis data

Best for: Analyzing experiment results immediately after a test concludes. Ask "did the new onboarding modal improve 7-day retention for users who saw it?" and get the PostHog data to answer the question before writing up the results for the team.

2. Amplitude MCP Server — Behavioral Event Analytics

Amplitude excels at event-based product analytics — tracking user actions, building behavioral cohorts, and computing engagement metrics over time. The Amplitude MCP server lets your AI query this behavioral layer directly, turning raw event data into growth insights without manual chart-building.

Key capabilities:

  • Query event counts and unique user metrics by segment and timeframe
  • Read funnel reports to identify drop-off points
  • Access retention and stickiness metrics for cohort comparison
  • Retrieve chart data from saved Amplitude analyses

Best for: Identifying the highest-leverage drop-off in your funnel. Ask "at what step do we lose the most users between signup and first value?" and get an Amplitude-backed answer that turns a vague hypothesis into a prioritized experiment opportunity.

3. Mixpanel MCP Server — Conversion Funnel Deep Dives

Mixpanel's strength is cohort-based funnel analysis and user journey mapping. The Mixpanel MCP server gives your AI access to saved funnels, user profiles, and engagement reports — making it possible to answer segment-level questions that would normally require building custom reports manually.

Key capabilities:

  • Query funnel conversion rates with breakdowns by property
  • Access user profile data for segment profiling
  • Read flow reports to visualize navigation paths
  • Retrieve saved reports and board data for synthesis

Best for: Understanding behavioral differences between converting and non-converting users. Ask "what do users who complete the first purchase do differently from users who don't?" to identify the behavioral patterns worth amplifying in your growth experiments.

4. LaunchDarkly MCP Server — Feature Flag Control and Rollout Management

Feature flags are the mechanism of controlled growth experiments. The LaunchDarkly MCP server gives your AI access to your flag library, targeting rules, rollout percentages, and evaluation logs — making flag management faster and less error-prone during high-stakes experiments.

Key capabilities:

  • List active flags and their current rollout configurations
  • Read targeting rules and segment definitions for flag evaluations
  • Check flag evaluation logs to diagnose unexpected behavior
  • Audit flag lifecycle to identify stale flags accumulating technical debt

Best for: Pre-launch experiment audits. Ask "what flags are currently active in production with more than 50% rollout?" to catch configuration errors before they affect your control group, or to identify flags that have been fully rolled out and should be cleaned up.

5. Segment MCP Server — Customer Data Pipeline Visibility

Segment is the data pipeline that connects your product events to every downstream tool in your growth stack. The Segment MCP server gives your AI visibility into your sources, destinations, and event schemas — making it easier to debug data pipelines, audit tracking coverage, and ensure your analytics are measuring what you think they are.

Key capabilities:

  • Browse source configurations and connected destinations
  • Read event schemas and property definitions
  • Inspect workspace settings for data governance
  • Audit destination connections for data flow verification

Best for: Diagnosing missing data before blaming the analytics tool. When an Amplitude funnel shows unexpected drop-off, check Segment first — ask "is the checkout_completed event configured to flow through to Amplitude?" before assuming the product behavior is wrong.

6. HubSpot MCP Server — Marketing Attribution and Lead Flow

Growth doesn't end at the product boundary. For B2B or mixed motion companies, HubSpot connects marketing acquisition with sales pipeline — and the HubSpot MCP server makes that connection queryable, letting you trace user journeys from first touch to closed revenue.

Key capabilities:

  • Query contacts, deals, and companies by segment, stage, or source
  • Read email campaign performance and engagement metrics
  • Access marketing attribution data for channel ROI analysis
  • Review workflow automations for lead nurture sequence logic

Best for: Attribution analysis for B2B growth. Ask "what was the conversion rate from free signup to paid for users acquired through the content channel last quarter?" and get a traceable answer across the product and CRM data — the kind of analysis that usually requires a BI query and a CRM export to reconcile manually.

7. BigQuery MCP Server — Data Warehouse Queries for Growth Analysis

Growth questions often require joining behavioral data with transactional data — cohort revenue, LTV by acquisition channel, subscription retention by plan type. BigQuery is where most of that joined analysis lives, and the BigQuery MCP server makes it queryable in natural language rather than requiring a data engineering request.

Key capabilities:

  • Execute SQL queries across growth and revenue datasets
  • Browse table schemas for available dimensions and metrics
  • Run ad hoc cohort queries for LTV and payback period analysis
  • Access dbt model outputs for business-logic-enriched metrics

Best for: Revenue-side growth analysis that product analytics tools can't answer on their own. Ask "what is the 90-day LTV for users acquired through the referral program versus organic?" and get a SQL-backed answer from the data warehouse where revenue and acquisition source data actually live together.

8. GitHub MCP Server — Experiment Code and Implementation Context

Growth experiments are code. Variant implementations, tracking calls, flag evaluations, and A/B test configurations all live in the codebase. The GitHub MCP server gives your AI access to the actual experiment implementation — so you can verify what a variant actually does, rather than relying on a brief written weeks ago.

Key capabilities:

  • Read experiment code to verify variant implementation correctness
  • Search for feature flag references to understand experiment scope
  • Review tracking calls to audit data collection completeness
  • Check pull request diffs to understand what changed between experiment iterations

Best for: Post-experiment debugging when results don't match expectations. Ask "what exactly does the B variant of the checkout experiment do differently?" and get the answer from the actual code, not from a product brief that may have evolved during implementation.

Recommended Stacks for Growth Engineers

  • Experiment analysis: PostHog + LaunchDarkly + GitHub (results → flag config → implementation verification)
  • Funnel optimization: Amplitude + Mixpanel + Segment (event data → cohort analysis → data pipeline audit)
  • Revenue growth: BigQuery + HubSpot + PostHog (LTV queries → pipeline data → behavioral context)
  • B2B growth: HubSpot + BigQuery + Amplitude (CRM data → revenue data → product behavior)
  • Full growth stack: PostHog + Amplitude + LaunchDarkly + BigQuery + HubSpot — complete coverage across behavioral data, experiments, revenue, and CRM

Browse all Analytics MCP servers on MyMCPTools. For related guides, see Best MCP Servers for Marketing and Best MCP Servers for Product Managers.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

📊

PostHog MCP Server

The PostHog MCP Server is PostHog's official Model Context Protocol integration, giving AI assistants direct access to product analytics, feature flags, session replay, experiments, and error tracking without leaving the chat. It's hosted remotely at mcp.posthog.com (Streamable HTTP) and authenticated with a personal PostHog API key passed as a Bearer token — the quickest setup is `npx @posthog/wizard@latest mcp add`, which auto-configures Cursor, Claude, Claude Code, VS Code, or Zed in one command; manual setup adds an `mcp-remote` proxy entry with the `Authorization` header for clients without native remote-MCP support. Tools cover the full PostHog surface: creating and toggling feature flags with percentage rollouts and targeting rules, running trends/funnel/retention queries via `query-run`, inspecting session recordings, pulling error-tracking issues, and managing experiments — all scoped to the project tied to your API key. Typical use: ask Claude to "create a feature flag for the new checkout flow at 20% rollout" or "how many unique users signed up in the last 7 days, broken down by day?" and the assistant executes the query or mutation against your live PostHog project and returns formatted results. Originally shipped as the standalone PostHog/mcp repo (150+ stars), the server's source has since moved into the main PostHog monorepo under `services/mcp` but documentation and install instructions are unchanged.

Auth required
📊

Amplitude

Search, analyze, and query charts, dashboards, experiments, and feature flags.

Local
📊

Mixpanel

Query and analyze your product analytics data through natural language.

Local
💻

GitHub MCP Server

The GitHub MCP server is GitHub's official Model Context Protocol integration, giving AI assistants like Claude and Cursor direct, authenticated access to the GitHub platform and its full developer surface. With this MCP server, you can ask your AI to read and write repository files, create and merge branches, open and review pull requests, comment on and close issues, trigger GitHub Actions workflows, search across code repositories with GitHub's code search, and inspect commit history — all through natural-language prompts in your AI interface. Developers use it to supercharge code review workflows, automate issue triage, generate PR descriptions from diffs, bulk-update repository settings, and wire AI agents into CI/CD pipelines. The GitHub MCP server connects via a GITHUB_PERSONAL_ACCESS_TOKEN environment variable with scopes for the operations you need, keeping authentication clean and auditable. Install with Docker: `docker run -e GITHUB_PERSONAL_ACCESS_TOKEN=<token> ghcr.io/github/github-mcp-server` — or configure it as a remote MCP server in Claude Desktop, Cursor, VS Code, Windsurf, and Cline. With over 8,000 GitHub stars, it is the most widely deployed official code-platform MCP server and the reference implementation for AI-native GitHub automation.

Auth required
🔧

LaunchDarkly

Feature flags as a service for continuous delivery.

Local
📊

Segment

Segment (Twilio Segment) does not currently ship a first-party Model Context Protocol server — repos claiming to be an "official Segment MCP" (like segmentio/mcp-server) don't actually exist, and no Twilio-published MCP package has shipped as of this writing. The closest authoritative reference is Segment's own actively-maintained analytics-next SDK (400+ stars), the JavaScript library that powers Segment's client- and server-side tracking calls (track, identify, page, group) across web and Node. In practice, teams that want an AI assistant to read or write Segment data build a thin MCP wrapper around Segment's public HTTP Tracking API using a per-source write key, exposing tools like track_event, identify_user, and group_account so an assistant can execute requests such as "log a purchase event for this user in Segment" or "identify this contact with these traits" without a human touching the dashboard. Segment's Engage and Unify APIs (audience management, profile lookups) are also reachable this way with a workspace access token. Until Twilio ships (or a well-maintained community project emerges for) a dedicated Segment MCP server, this entry points at the SDK repo that actually documents the underlying event schema and auth model any wrapper would need — update this entry if a real one ships.

Local
🌐

HubSpot MCP Server

The HubSpot MCP Server is HubSpot's official Model Context Protocol integration, giving AI assistants direct read and write access to your CRM data — contacts, companies, deals, tickets, and pipelines — without leaving your conversation. Built and maintained by HubSpot, the server connects to the HubSpot APIs using your private app access token and exposes tools that let Claude search contacts by email or name, retrieve company records, create and update deal stages, log notes on CRM objects, list pipeline stages, and query ticket queues. This eliminates the round-trip of switching tabs to look up a contact or manually log an interaction. Setup requires a HubSpot account with a Private App — create one at app.hubspot.com/private-apps, grant the scopes your workflow needs (contacts read/write, crm.objects.deals, crm.objects.tickets), and copy the generated access token into your environment as HUBSPOT_ACCESS_TOKEN. Once connected, Claude can power CRM workflows like: "Find all contacts at Acme Corp and list their recent activity," "Create a new deal in the Prospecting stage for $15,000," or "Log a meeting note on this contact." The server supports Claude Desktop, Cursor, Windsurf, Cline, and any MCP-compatible client. It is especially valuable for sales, RevOps, and support teams who want AI-assisted CRM work without manual data entry or tab-switching.

Auth required
🗄️

BigQuery MCP Server

Google's official BigQuery MCP integration ships as part of the MCP Toolbox for Databases (googleapis/mcp-toolbox, 15,800+ stars, formerly published under the genai-toolbox repo name before Google renamed it), a single Go-based server binary that speaks the Model Context Protocol for over a dozen Google Cloud and third-party databases. Rather than a BigQuery-only package, you run the shared toolbox binary with a `--prebuilt=bigquery` flag to instantly load BigQuery-specific tools — schema/table discovery (`list_dataset_ids`, `list_table_ids`, `get_table_info`), running arbitrary SQL via `execute_sql`, and dry-run query validation for cost estimation before executing — over stdio or as an HTTP/SSE server. The quickest install is `npx -y @toolbox-sdk/server --prebuilt=bigquery --stdio` in your MCP client config; it also ships as a downloadable binary and Docker image for teams that prefer not to run via npx. Authentication uses standard Google Cloud credential chains (Application Default Credentials, service account keys, or Workload Identity) rather than embedding a project-specific key. Toolbox also underlies Google's official SDKs for Python, JS/TS, Go, and Java, so the same server config can back both ad hoc AI-assistant queries ("show me the schema for the events table and the row count for last week") and production agent tools built with LangChain, LlamaIndex, or ADK. For teams that want a fully managed remote option instead of self-hosting, Google Cloud also offers managed MCP servers for its databases including BigQuery.

Local
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local
📋

Notion MCP Server

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 3,500+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_API_KEY in your environment. Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

Auth required

📚 More from the Blog