Simba MCP Server
OfficialRelated Servers
Alternatives to Simba MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityBmaintenanceConnects AI assistants to marketing mix models, enabling natural language data upload, performance modeling, budget optimization, and scenario testing.-
- AlicenseBqualityAmaintenanceProvides a controlled interface for Bayesian Marketing Mix Modeling, letting AI agents validate datasets, fit and diagnose MMMs, analyze channel contributions and ROI, simulate and optimize budgets, calibrate with lift tests, and cross-validate models—all with statistical verification, uncertainty reporting, and full provenance.331Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables marketing optimization tasks such as copywriting, campaign analysis, social media planning, audience segmentation, and KPI tracking through natural language.82 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query campaign performance, metrics, audiences, and geography, and to analyze budgets, wasted spend, and account health through natural language.1MIT

PaidSync MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, analyze, and optimize ad campaigns across Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Amazon Ads, and ChatGPT Ads through natural language using 400+ tools.93MIT
TDQS
Scored across 63 tools
The core model/upload/optimizer/scenario tools are distinct, but the recipe and study clusters overlap heavily: create_recipe_draft vs create_study_recipe and get_recipe_revision_authoring vs get_recipe_revision are easy to confuse from names alone. Detailed descriptions resolve most ambiguity, but an agent must read carefully before choosing.
All 63 tools follow a consistent snake_case verb_noun pattern: get_*, list_*, create_*, update_*, run_*, launch_*, evaluate_*, compare_*. Even the longer compound nouns like study_validation_pair and recipe_revision_authoring are internally consistent with their siblings, so the set is highly predictable.
At 63 tools, the server is far above the well-scoped range and feels like a full platform API rather than a focused MCP surface. The broad Simba domain explains some of the count, but the surface would be much more usable split into modeling, run/optimization, and study-governance servers.
The surface covers nearly the entire MMM and VAR lifecycle: schema/upload, model creation/status/results, optimizer/scenario runs, projects, and deep study/recipe/quality governance. It is not a perfect 5 because a few lifecycle actions such as deleting non-failed models/projects, champion promotion, and manual sign-off are deliberately frontend-only and documented as gaps an agent cannot complete.