Skip to main content
Glama
google-meridian-mcp

google-meridian-mcp

Google Meridian MCP Server (google-meridian-mcp)

License: MIT Python 3.11+ Node.js 18+ MCP Standard

A Cloud-Agnostic, First-Principles Model Context Protocol (MCP) server for Google Meridian and Marketing Mix Modeling (MMM).

It empowers data scientists and AI assistants (Cursor, Claude Desktop, Antigravity) to create, audit, calibrate, and optimize mathematically sound, causally valid Marketing Mix Models with zero cloud vendor lock-in.


šŸ’” Why First Principles Over Rigid Scripts?

Most assistant implementations rely on hardcoded procedural scripts (SKILL.md). In real-world data science, rigid scripts break because every business, industry, and marketing dataset is unique:

  • A retail brand with 50 DMAs operates differently than a B2B SaaS startup with national data.

  • App install targets (NON_REVENUE) require different priors than revenue models (REVENUE).

  • Specific channel CPMs, flighting patterns, and Lift Tests vary across campaigns.

First Principles never change. Causal identification (DAGs), carryover/saturation physics (Adstock & Hill curves), Bayesian probability calibration, NUTS MCMC geometry ($\hat{R} < 1.05$), and KKT convex budget optimization apply universally to every dataset on Earth.

By anchoring this MCP server in First Principles & Dynamic Data Science Tools, the co-pilot adapts seamlessly to any specific edge case while guaranteeing mathematical rigor.


Related MCP server: Gemini Docs MCP Server

šŸ›ļø The 4 Mandate Pillars

ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ 1. EVERY CONTROL POINT   │ Covers Data Inputs, Controls/DAG, Baseline, Adstock,        │
│                          │ Hill Saturation, Bayesian Priors, MCMC, Optimization.       │
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¼ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│ 2. END-TO-END WORKFLOW   │ Guides the 5 phases & 3 iteration loops (Convergence        │
│                          │ Diagnostics āž” Causal Plausibility āž” Lift Calibration).      │
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¼ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│ 3. FIRST PRINCIPLES      │ Grounded in causal inference, probability theory, HMC/NUTS  │
│                          │ sampling geometry, and convex optimization math.            │
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¼ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│ 4. PLATFORM AGNOSTIC     │ 100% portable with zero cloud vendor lock-in. Runs locally, │
│                          │ in Docker, or on AWS, Azure, GCP, Railway, Render, etc.     │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

šŸ› ļø Complete MCP Tool Suite (11 Tools)

Category

Tool

Parameters

Description

Control Points

get_control_point_guide

control_point: str

Operational parameters, math formulas, and bounds for all control points.

Workflow

get_mmm_workflow_guide

phase: str

Decision trees and iteration rules for the 5 modeling phases & 3 iteration loops.

Prior Math Engine

calculate_bayesian_prior

point_estimate, ci_lower, ci_upper

Converts 95% CIs from Lift Tests into exact Meridian LogNormal ($\mu, \sigma$) prior parameters.

Spec Auditor

audit_model_first_principles

config_json: str

Audits model specs for identifiability, knot density, prior variance, and Hill parameter bounds.

EDA Engine

run_eda_checks

config_json: str

Pre-modeling EDA checks (VIFSpec, PairwiseCorrSpec, DataParameterRatioArtifact).

Model Reviewer

run_model_review_checks

check_type: str

Diagnostic checks (BayesianPPPCheck, PriorPosteriorShiftCheck, ImplausibleROICheck).

Code Synthesizer

synthesize_meridian_code

pipeline_stage: str

Generates clean, portable, cloud-agnostic Python code for Google Meridian pipelines.

Data Utility

generate_schema_template

n_weeks, n_geos, n_channels

Generates synthetic CSV schema templates matching Meridian's input format.

Documentation

list_doc_sources

category: str

Lists documentation sources filtered by category.

Documentation

fetch_docs

url: str

Fetches and parses documentation pages/GitHub code to Markdown.

Documentation

search_doc_topics

query: str

Searches Meridian topic index (Adstock, Hill curves, NUTS, Priors, etc.).


⚔ Quick Connect (Remote SSE Mode)

Add this to your IDE's mcp_config.json:

{
  "mcpServers": {
    "google-meridian": {
      "url": "https://google-meridian.mcp.borobudur.ai/sse"
    }
  }
}

šŸ’» Local Setup & Running

# Install dependencies
pip install -r requirements.txt

# Run server in stdio mode
python server.py

mcp_config.json:

{
  "mcpServers": {
    "google-meridian-mcp": {
      "command": "python",
      "args": [
        "C:/path/to/google-meridian-mcp/server.py"
      ]
    }
  }
}

Option B: Node.js Setup

npm install
npm start

šŸ“„ License

MIT License. Open source and free for the community.

Available Tools

9 tools
audit_model_first_principlesC

Audits model spec for identifiability, knot density, prior variance, and Hill parameter bounds.

Inputs: config_json.

calculate_bayesian_priorA

Solves probability equations to convert 95% CIs into Meridian LogNormal (mu, sigma) prior parameters.

Inputs: ci_lower (required), ci_upper (required), point_estimate (required), experiment_type.

fetch_docsB

Fetch and parse Google Meridian documentation or code into clean Markdown.

Inputs: url (required).

generate_schema_templateC

Generates a synthetic benchmarking CSV schema template matching Meridian's input format.

Inputs: n_geos, n_weeks, n_channels.

get_control_point_guideB

Provides operational parameters, math formulas, and bounds for data science control points.

Inputs: control_point.

get_mmm_workflow_guideB

Provides decision trees and iteration rules for modeling phases and iteration loops.

Inputs: phase.

list_doc_sourcesA

List all available Google Meridian documentation sources, user guides, API references, and GitHub repository links.

Inputs: category.

search_doc_topicsA

Search Google Meridian documentation by topic or keyword (e.g., 'adstock', 'priors', 'budget optimizer', 'NUTS', 'R-hat', 'DAG', 'causal').

Inputs: query (required).

synthesize_meridian_codeC

Synthesizes clean, portable, cloud-agnostic Python code for Google Meridian.

Inputs: config_json, pipeline_stage.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Documentation tools (fetch, list, search) are separated by action, guides target different aspects (control points vs workflow), and remaining tools cover calculation, auditing, code synthesis, and schema generation without overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, e.g., fetch_docs, get_control_point_guide, calculate_bayesian_prior, list_doc_sources. The verbs are varied but predictable, and there is no mixing of conventions.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a domain-specific MCP server. It covers documentation, guides, prior calculation, auditing, code synthesis, and schema generation without being overloaded or too sparse.

    Completeness4/5

    The tool surface covers core documentation, guides, prior calculation, and auditing. Minor gaps exist: missing tools for directly running models or retrieving results, but these may be handled by synthesized code. Overall, it's fairly complete for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers