All projects

AI-Operated WordPress via MCP

This site is administered by an AI agent over the Model Context Protocol — theme, content and media, through an audited connection.

sidspanos.me // model context protocol

Choose Your Operator

Insert coin ▮
● now operating·The Operator

Claude

Select — 04 agentsvs. the task
operator@sidspanosinit.sh

P1 ready
Claude — holds admin rights
$ sidspanos.me administered over MCP, not by hand

Click a tile · ←→↑↓ move · Enter lock in · stats are for fun

Context: This website

The portfolio is also the working system

This WordPress site is connected to WPVibe over the Model Context Protocol. An AI assistant can read the REST API, run supported WP-CLI operations, edit theme files and upload media. The front page was built through that connection.

How changes reach the site

The connection uses a WordPress application password and records operations in an audit trail. Theme edits are staged in a draft with a preview URL before publication.

What the build exposed

  • Reverse-proxy configuration: a scheme mismatch between the site URLs caused a repeating wp-admin login loop.
  • Theme behaviour: a fixed-footer rule painted over page content.
  • Network boundaries: the image-fetching guard rejected private network addresses.

Related work

The container platform underneath the sites · The measured portfolio theme trial

Skills in practice

The work connects AI-assisted administration with WordPress, authentication, reverse-proxy behaviour and front-end debugging. The operating lesson is visible in the workflow: inspect the result in its real context before putting a change live.

Explore connected work