Support
Getting unstuck
Most problems are one of four things, and all four are documented. Start with the troubleshooting guide — it is written around the failures that actually happen.
Reporting a defect
If it looks like a genuine bug rather than a misunderstanding, these four things are almost always enough to reproduce it.
- 1The tool name you called and the arguments you passed.
- 2The `meta` block from the response — window, upstream calls, cached or not.
- 3The `meta.window` you expected, so a window mismatch is obvious.
- 4Whether the account is hosted or self-hosted, and the version.
Three quick checks before you report
- Did you pass a ScopeMCP
propertyIdfromscopemcp_list_propertiesrather than a rawsc-domain:value? - Does the
meta.windowcover the dates you expected? Windows end three days before today because Search Console data lags. - Did the source actually return a
limitsnote that explains it? Tools say when data was unavailable rather than guessing.
Using it in a team
Every member connects their own Google, Bing or Microsoft account, so permissions stay with the person who holds them. If you want someone to see a finding without an account, generate a share link — it is a revocable pointer to one snapshot and grants no access to anything else.