Marketing MCP prototypes

This started with too many tabs and too little shared memory.

I am building the marketing workspace I wanted to use.

I work with advertising accounts, analytics, multilingual content and landing pages. Each platform is useful on its own, but the work between them is where context gets lost: why a campaign changed, what we learned in the last review, whether the result improved, and how to explain it to somebody else. The tools below are my attempt to join those loose ends.

THE OPERATING LOOP

From account review to a useful report

I did not set out to build five MCP servers. I built the first integration, found the next missing piece during real work, and repeated that process. Each tool still has one clear responsibility, but together they cover a complete review cycle.

  1. 01

    Diagnose

    I inspect campaign structure and performance to find wasted search terms, budget constraints, zero-conversion spend and tracking gaps.

  2. 02

    Remember

    I save the finding together with client context, earlier decisions and a concrete follow-up task instead of losing it in chat history.

  3. 03

    Act

    The agent prepares a specific change and shows me the exact scope. In the prototyping setup, nothing is sent to an ad platform until I confirm it separately.

  4. 04

    Measure

    I compare the result against GA4 acquisition and conversion data, including cost and ROAS from linked Google Ads accounts.

  5. 05

    Report

    Finally I turn metrics, charts and conclusions into repeatable PDF or PNG deliverables rather than rebuilding the same deck by hand.

ADS ADS BABY

Five local tools. One marketing workspace.

I packaged the family for Claude Code, Codex and Cursor because I do not want the workflow tied to one model host. The servers run locally and the tools that can spend money or alter delivery use a separate confirmation step. Public repositories are available to inspect, but testing access is currently coordinated while credentials and integrations mature.

Prototype in use
Analysis + campaign operations

Google Ads Baby

This was the first piece of the family. I use it to inspect accounts through GAQL, automate repeatable reviews and prepare changes for Search, Display and Performance Max from one agent session. Because it can alter budgets and delivery, every mutation has a two-phase confirmation flow.

GitHub
Prototype in development
Meta campaign operations

Meta Ads Baby

I am adapting the same local workflow to Meta Marketing API. Meta does not provide the comfortable sandbox I would want for campaign changes, so I share the preview-first safety contract with the Google integration instead of treating confirmation as a sentence in the prompt.

GitHub
Prototype · read only
Measurement

Google Analytics Baby

Campaign-platform metrics are only half the story. I added a deliberately read-only GA4 integration for acquisition, conversion and channel performance. It can also retrieve linked Google Ads cost, CPC and ROAS through the GA4 Data API without granting another tool write access.

GitHub
Prototype · local first
Durable marketing memory

Marketing Context MCP

This is the memory layer the other tools were missing. It stores client profiles, decisions, reviews, tasks and reusable marketing procedures as ordinary files. I can inspect or edit them myself, version them, and carry the reasoning from one agent session into the next.

GitHub
Prototype · PDF + PNG
Reporting output

Report Baby

Analysis is not finished when the agent prints a table in the terminal. I built Report Baby to turn structured data, HTML and reusable templates into PDF reports, PNG charts and metric cards. It gives the workflow an output that can actually be sent, reviewed and compared later.

GitHub
Landing page workflow

I brought HubSpot development back to local files.

HubSmith grew out of the other side of my marketing work: building and adjusting HubSpot landing pages. The browser editor is fine for content, but it is a poor place for understanding a whole theme, comparing modules or asking an LLM to make a careful change. HubSmith synchronizes themes and modules to a normal filesystem, renders a local preview and pushes the result back to HubSpot.

A coding agent can inspect the real module structure, follow imports, search every template and reuse conventions already present in the theme. Instead of describing a landing page through screenshots and pasted fragments, I can give the model the same source material I have.

  • Inspect and edit the real theme structure
  • Preview modules with live reload
  • Use any editor or local AI coding tool
RELATED, BUT SEPARATE

PolyTrans is a different branch of my work.

The marketing MCP family is about helping an agent inspect, remember, measure and report on marketing work. PolyTrans is about multilingual publishing and editorial workflows. Both grew from practical work around the Trans.eu ecosystem, but they are not one pipeline and one does not depend on the other.