Case Study

The Site That Runs Itself.

How we shipped a 21-tool MCP connector that makes every content operation — publishing, image generation, voice calibration, prospect outreach — agent-addressable from a single Claude conversation.

CMS and outreach MCP connector for Automaton
21
Agent-Callable Tools
5
Operation Categories (CMS, Blog, Images, Voice, Outreach)
0
Manual Tool-Switching Required
Live
Current Status

The Problem

Site content updates, blog publishing, image generation, voice calibration, and prospect outreach were scattered across separate tools with no programmatic surface for autonomous agents. Every content operation required manual context-switching.

As the autonomous workflow at Automaton matured, the bottleneck shifted from what Claude could do to what Claude could reach. The tools existed — they just weren't agent-addressable.

What We Built

We shipped a 21-tool MCP connector deployed on Supabase Edge Functions, covering five categories: CMS page CRUD (read, write, list, deploy), blog workflows (draft, publish, update, list), a Gemini-powered image generation and upload pipeline, a voice clone rules and phrases database for maintaining consistent output voice, and a prospect-and-outreach CRM for tracking firm research and email history.

The connector is accessible from any Claude session. A single conversation can now research a prospect, draft an outreach email, generate a hero image for a new blog post, publish the post, and log the outreach — without switching tools or tabs.

The entire content operation is now agent-addressable. Any Claude session can draft, illustrate, publish, and log outreach without leaving the conversation.

The System Architecture

21-tool MCP connector deployed on Supabase Edge Functions. CMS tools: getPage, updatePage, listPages, triggerDeploy. Blog tools: getPost, addPost, updatePost, listPosts. Image tools: generateImages, uploadImage, selectImage. Voice tools: listRules, addRule, listPhrases, addPhrase. Outreach tools: addProspect, updateProspect, listProspects, logOutreach, updateOutreach, listOutreach.

The Results

The entire Automaton content operation is now agent-addressable. Blog posts, case studies, image assets, and outreach sequences all flow through the same conversation interface.

The connector also made this website possible: every case study, insight, and image on automatonagency.com was created or managed through the MCP without touching the database directly.

Client

Automaton (internal — content and outreach infrastructure)

Engagement

Internal Build
Initial build: Ongoing

Stack

  • Supabase Edge Functions
  • MCP Protocol
  • Gemini Image Pipeline
  • HubSpot
  • Claude API

Services

  • MCP Development
  • CMS Architecture
  • Image Pipeline
  • Voice Clone System
  • Outreach CRM

Your Turn
Similar problem?
Every system we build starts with understanding what's broken.
Book a call →