Web agency · Site managed with Claude through MCP

An agency that edits its site by writing a sentence: Claude connected through MCP, a human review before every release

After its migration to Astro, a digital agency of about twenty people wanted its team to stay in control of its site without going through a developer for every fix. We connected Claude to the site repository through an MCP server, wrote the house rules, and kept a person to approve every release.

The starting point

Under Drupal, every change to a text, a title or an image went through someone who knew the tool. Requests piled up, and the site aged faster than the team could fix it.

A static site is faster and safer, but it removes the admin screen. Without the right tool, the team risked depending more on the developer, not less.

What we did

1. Connect Claude to the site

Claude reaches the site repository through GitHub’s MCP server, with an account limited to that repository. It reads the pages, prepares a change on a separate branch and never touches the live site.

2. Write the house rules

An instructions file says where each page lives, how a title, an internal link or a FAQ is written, and what must not be touched. Claude reads it before each request, so two people get the same result.

3. One single procedure

For each request, the same sequence: find the page from its URL, announce what will change, edit, run the checks, show a preview, then propose the merge.

4. A person approves

Each change comes with a preview link. Nothing goes live until a team member has looked at it and accepted it: publishing means merging.

5. Team onboarding

One session to learn how to phrase a request, read a preview and turn down a proposal, then follow-up over the first weeks.

What it changes

  • The team fixes a text, a title or a FAQ itself, by writing what it wants in plain language.
  • The developer focuses on real projects instead of small touch-ups.
  • Every change is reviewed, dated and reversible: the history shows who asked for what and when.
  • SEO and internal linking rules apply by themselves, since they are written into the instructions Claude follows.

Timeline

  1. September 2026

    House rules and procedure written during the migration

  2. October 2026

    Claude connected through MCP, trials on a copy of the site

  3. 16 October 2026

    In use with the site switch

  4. Mid-November

    First review with the team

Under the hood

  • Astro
  • GitHub
  • Serveur MCP GitHub
  • Claude
  • Aperçu par branche
  • Contrôles automatiques

The offers this project proves

Other case studies

Real estate · Portal, CRM and automations

Palmora Property

Read the case study

E-commerce · Takeover and turnaround

Peluche Kingdom

Read the case study

App · Web, iOS and Android

Challenge Us

Read the case study

Web agency · CRM, automations and publishing

Brain Plus AI

Read the case study

See all case studies

A similar project?

We start by checking together that it is the right workstream, and what it would change for you.

Let's talk
WhatsApp