AI agent (MCP)
Good to know & troubleshooting
Alpha limitations and quick fixes for the Equall MCP server.
Good to know (alpha)
- First scan needs your workspace authorized once. Scans run with your workspace's server-side GitHub access, and authorizing the MCP in your browser is enough to set it up. If the workspace was never authorized, the scan fails fast with a message telling you to sign in to the Equall dashboard once.
- Private repos need a GitHub id to connect.
- Scans always run on the default branch — per-branch scanning isn't available yet.
- A suggested page scope is never a confirmed one. Adding a page can attach a §5.6 scope suggestion, but confirming it is a dashboard-only step for a workspace member.
Troubleshooting
- No issues returned → confirm the repo is connected and has a completed scan.
- The equall tools disappeared, or calls return 401 → the authorization lapsed; re-run the
browser flow (
claude mcp login equall, or your client's MCP re-authorize action). If you use the legacy pasted-token fallback, your ~1h session token expired — prefer switching to the browser flow, which refreshes itself. - Scan never produces results → the workspace may not be authorized yet; authorize the MCP or sign in to the dashboard once (see above).
- "Rate limited" replies → by design: one connect per minute, one scan per repo per minute, up to 10 pages added per 10 seconds (20 per repo per minute). Have the agent wait and retry.
- Another workspace's data? → never happens by design; access is scoped to the workspace you authorized.