Ongoing Operations with MCP

Use the Model Context Protocol to let your AI agent manage content, media, menus, and site context through approved tools — without editing project files directly.

Use this when

Your restaurant site is built, reviewed, and stable. Now you want your AI agent (Claude, Codex, or similar) to manage content updates, media, menus, and site context through a structured interface instead of running CLI commands or editing files.

MCP (Model Context Protocol) gives the agent access to approved site tools. Think of it as giving the agent a set of keys to specific rooms — it can manage content through those keys, but it cannot do anything outside what the tools allow.

Copy this prompt

Connect to this Dineway site with MCP and help me manage content. List available tools, then inspect current content and site context before making changes. Apply all changes as drafts unless I approve publishing. Do not use tools that require provider credentials I have not set up.

What the agent can do with MCP

MCP exposes tools for:

  • Content — list, create, update, delete, publish, unpublish, schedule.
  • Media — upload, list, delete.
  • Menus — list, create, update menu items.
  • Search — query and rebuild the search index.
  • Taxonomies — manage tags, categories, and other groupings.
  • Site context — record and read durable knowledge like brand voice, seasonal strategy, and operating rules.
  • Entity resolution — map natural-language references (“the patio post”) to exact content items.

What the agent should inspect first

  • Available MCP tools — the list tells the agent what it can and cannot do.
  • Current content status — what is draft, what is published.
  • Recorded site context — has anyone set up brand voice or operating rules?
  • Media library — what images and files exist.
  • Menu structure — what navigation is in place.

When to use MCP vs. CLI

| Situation | Use | |-----------|-----| | First-time site build | CLI and skills | | Ongoing content updates | MCP | | SEO research and audits | CLI commands | | Design or layout changes | CLI and skills | | Recording site context | MCP | | Quick content inspection | Either |

MCP is designed for ongoing operations after the first build. For the first site, start with the Quick Start and CLI.

How you review MCP changes

Ask the agent:

  • What tools did you use and what changed?
  • Show me the before and after for any content updates.
  • Is anything still in draft that should be published, or published that should be draft?
  • Did you record any new site context? Show me what you recorded.

Do not let the agent invent

The same rules apply with MCP as with CLI:

  • No invented menu items, prices, awards, or reviews.
  • No publishing without your approval.
  • No deleting content without confirmation.
  • No fabricated site context or brand voice you did not provide.