Add the server
- Add the hosted endpoint as an MCP server in your client.
- Complete the OAuth sign-in when the client asks.
- Confirm the client lists the tools the server registers.
- Call the tool that reports who the token belongs to.
- Call one free read, such as budget status, before anything metered.
A filled record
client: name and version
server: https://app.sitearc.ai/mcp
transport: http
auth: oauth, completed in browser
scopes: mcp, offline_access
verified
- whoami returned the account and its website reach
- budget status returned a figure, cost zero
- tools listed every name in the MCP reference
not verified
- a write tool against a linked repository
- any second client
Protocol support versus a recorded install
Any client that completes OAuth and speaks MCP should reach the same tools. That is a statement about the protocol, not a record of a tested install.
Where this team has recorded an install, the docs name the client and the version. Where it has not, the page says unverified.
Acceptance: the connection is verified when
- the client lists the server’s tools
- one read returns your own account
- the free budget read returns a figure
- the record names the client version and the date
- no credits were spent to prove the connection works
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Tools list is empty | Connected but unauthenticated | Re-run the sign-in |
| A refused call | A missing project or repository link | Link the project, then retry |
| A write is refused | The GitHub App is not installed | Install it, or use the read-only path |
| Rate-limit refusals | Too many calls in a minute | Wait, then read your plan’s limit |
| Costs appear after one read | A metered tool ran | Read the budget status first next time |
What the connection can reach
The token belongs to your account. Everything the tools can touch is scoped to it.
read every website in the workspaces you can open
read feedback, audit findings, proposals and their evidence
metered keyword, competitor, backlink and domain research
write a pull request, where a repository and the GitHub App are connected
never an approval, a merge, a live publication or a plan change
Revoking the client’s grant stops that client alone. The other connections in the account keep working.
Limits
The server never approves work, merges a pull request or publishes live. An agent can prepare all three, and a person finishes them.
Tool schemas can change between clients. Treat a refused call as a version question first, and a permissions question second.