Sitearc keeps the data for every website you run in one place. Your own agent connects over MCP and works from that data. A person approves each change before Sitearc counts it as shipped.
Sitearc runs no AI of its own. You bring Claude, Claude Code, Codex or another MCP client.
Start here
- Getting started: create an account, add a site and connect your agent.
- Connect a site: Google, GitHub and Vercel, and what each one reads.
- MCP reference: every tool, whether it only reads, and what it costs.
- Credits and plans: what spends credits and what never does.
By job
| Doc | What it covers |
|---|---|
| Getting started | Sign up, add a site, connect your agent, approve a first change |
| Connect a site | Shared connections, per-site overrides and what each source reads |
| MCP reference | Every tool, generated from the server’s own list |
| Claude Code plugin | The plugin and its skills, which are not public yet |
| WordPress plugin | The connector, which is not released |
| Feedback | Review links, pinned comments and turning a comment into work |
| Forms | Form endpoints, the inbox, delivery and limits |
| Credits and plans | Free and Pro, credits, packs and what happens at zero |
| Content and publishing | Briefs, drafts your agent writes, approval and pull requests |
| Recovery | What to check when a connection, a run or a delivery fails |
| Open source credits | The open source software Sitearc is built with |
The rules the product enforces
A person approves. No MCP tool can approve a proposal, a preview or a setup plan. Decisions are made in the dashboard by a signed-in person.
Shipped means matched. Sitearc only records a change as shipped when what merged is exactly what you approved. It never merges or deploys itself.
Results are computed. Sitearc measures changed pages against holdout pages and works out the result. Your agent can ask for it, but cannot set it.
Inconclusive is a result. Many changes show no clear effect. Sitearc says so rather than reading a trend into the noise.
Where it stops
The approval loop covers changes made through GitHub pull requests. Changes made any other way are not tracked or measured.
Some things are not built. They are listed here so nobody plans around them.
- WordPress plugin (not released)
- White label (part of Pro, coming)