Sitearc
Your agent

Every site's data and tools, in one connection for your agent.

Sitearc's MCP server works with Claude, Claude Code, Codex and other MCP clients. Your agent gets 130 tools to read your sites, research, and file work for you to review.

Demo data. Harbor & Pine is a fictional boatyard.

What your agent gets

  • 01

    Every site, one connection

    One connection covers every site you can open, across the workspaces in your account. Your agent names the site on each call.

  • 02

    Your own data, free to read

    Search Console, GA4, audits, forms and feedback. Reading them never spends credits.

  • 03

    Research, paid with credits

    Keywords, rankings, competitors, backlinks and AI visibility. Rank checks are priced before they run.

  • 04

    Work it can file

    Your agent turns findings into ideas and proposals with evidence. It opens pull requests for you to review.

  • 05

    Brand and memory

    It reads your brand kit, project context and past learnings. Each session starts from what you already know.

  • 06

    A split you control

    61 tools only read. A read-only key sees only those, and cannot write, spend credits or publish.

All 130 tools, grouped by job.

61 only read. The other 69 may change something or spend credits, and none of them can approve.

Every tool and its cost

Connect in a minute.

Bring the agent you already use. Sitearc runs no AI of its own, so there is no model markup.

Claude on the web

OAuth, no keys
  1. 1In Claude, add a custom connector.
  2. 2Paste https://app.sitearc.ai/mcp as its URL.
  3. 3Choose Sign in now, then Register automatically if asked.
  4. 4Sign in to Sitearc and allow access.

Claude Code and Codex

One command

Add the server once for every project. Then run /mcp in Claude Code to sign in.

$ claude mcp add --transport http sitearc --scope user https://app.sitearc.ai/mcp

Codex takes the same address.

$ codex mcp add sitearc --url https://app.sitearc.ai/mcp

An API key

For scripts

Create a key in Sitearc's settings. Keys start with oseo_.

x-api-key: oseo_…

Or send it as a Bearer token. Choose read or write when you create it. A read key sees only the 61 read tools.

What no tool can do

  • Approve. Proposals and previews are approved in the dashboard. A test in the app fails if an approve tool appears.
  • Merge or deploy. Your agent opens the pull request. Merging happens in GitHub.
  • Pick its own result. Sitearc computes won, backfired or inconclusive from the measurements.
How approval works, step by step

What your agent can do

Your agent starts a session with tools like these. Some only read. Others may change something or spend credits.

app.sitearc.ai/mcp8 of 130 tools
  • get_project_briefReads

    Starts a session with the site, its repo, its sources, its learnings and running experiments.

  • list_projectsReads

    Lists every website your agent can reach.

  • whoamiReads

    Confirms which account the agent is connected as, its scopes and the credit balance.

  • get_budget_statusReads

    Reads the spend limits that apply to a site, and what has been spent this period.

  • get_search_console_performanceReads

    Reads clicks, impressions, CTR and position by query, page, country, device or date.

  • get_audit_issuesReads

    Reads the issues from the last audit by priority, each with how to fix it.

  • estimate_rank_tracker_costReads

    Prices a check or a schedule before anything is spent.

  • run_rank_trackerMay change or spend

    Runs a live check now, within a credit limit you approved.

How it works

  1. 1

    Add app.sitearc.ai/mcp to Claude, Claude Code, Codex or another MCP client, and sign in once.

  2. 2

    Your agent reads the project brief: the site, its sources, its learnings and what is running.

  3. 3

    It researches, files ideas and proposals with evidence, and opens pull requests through GitHub.

  4. 4

    You approve proposals and previews in Sitearc. Sitearc only records a change as shipped when what merged is exactly what you approved.

Limits and credits

Know the edges before you rely on it. Credits pay for outside data and heavy work, and saved data never costs any.

Limits

  • No tool can approve a proposal or a preview. That happens in the dashboard, signed in.
  • Sitearc never merges or deploys. It can't stop someone merging a pull request in GitHub.
  • Free includes 1,000 MCP requests a month on saved data. Paid data tools need Pro credits.
  • Claude on the web is tested end to end. Claude Code and Codex steps are documented, not tested on every client.
  • The WordPress tools need the Sitearc WordPress plugin, which is not released.
  • The Sitearc plugin and skills for Claude Code and Codex are not public yet.

Credits

Keyword search
Per call; about 256 in auto mode (3 calls)
80 credits
SERP analysis
At depth 10; about 67 at depth 100
7 credits
Backlinks overview
About 347 for a full lookup
163 credits
AI visibility lookup
Measured; up to about 3,500
2,086 credits
Rank check
Per keyword, device and check, queued at depth 10; 20 at depth 100; live checks 7 to 67
2 credits

One credit is $0.001. Pro includes 100,000 a month, and Free includes none. See pricing

Connect your first site free.

Add every site you run, at no cost. Your agent can start the same day.