Sitearc

Connecting Sitearc to Claude Code

The install path, and the five steps that prove the connection works. A filled verification record before any credits are spent.

Answers
Connect the MCP server and confirm the connection with one read.
Included checklist
A filled install and verification record
Written for
Developers who already work in Claude Code

What you add

Claude Code connects to Sitearc’s hosted MCP server. The server gives the client its tools. A plugin with guided skills is built, but not public yet. This page uses the server alone.

Install and verify, in order

  1. Run claude mcp add --transport http sitearc --scope user https://app.sitearc.ai/mcp.
  2. Run /mcp in Claude Code, and complete the sign-in in the browser.
  3. Confirm the server shows as connected.
  4. Call the tool that lists your websites.
  5. Call budget status, which is free, and stop there.

A filled verification record

client:        claude code, version recorded at install
server:        https://app.sitearc.ai/mcp
transport:     http
auth:          oauth, completed in the browser
scopes:        mcp, offline_access

steps and results
1. server added with claude mcp add               ok
2. sign-in completed                              ok
3. server listed as connected                     ok
4. list websites returned two projects            ok
5. budget status returned a figure, cost zero     ok

stopped before:  any metered research call
credits spent:   none

not verified here
- a write tool, which needs a project and a linked repository
- any client other than the one named above

What it can and cannot do

It can read site context, research, feedback and audit findings. It can prepare work, draft content and open a pull request where the GitHub App is installed.

It cannot approve, merge, publish live or change a plan. There is no approval tool on the agent-facing surface.

Acceptance: the install is verified when

  • the server appears connected in the client
  • one read returns your own websites
  • the free budget read returns a figure
  • no metered call has run yet
  • the record names the client version and the date

Troubleshooting

Symptom Likely cause What to do
The client cannot reach the server A typo in the endpoint Compare with the docs, then retry
OAuth opens and nothing happens The browser blocked the redirect Allow the callback, then retry
Tools list is empty The server is connected but not authenticated Re-run the sign-in
A write call is refused No repository linked, or no GitHub App Link the repo, then connect the App
Every call is refused Rate limit Wait a minute, then read the limit for your plan

Limits

Tool names differ per client. Most clients prefix each tool with the server.

This page was written from Sitearc’s own documentation. It asserts no behaviour specific to one Claude Code version.

Where this came from