The symptom
You connected mowteng and asked a question about your site. Instead of data, the assistant answers: mowteng needs access to Google Search Console. The assistant itself is connected; it is mowteng that has no permission to read your Search Console.
The cause
When you sign in with Google, the consent screen lists what mowteng may access. Search Console access is one of those permissions, and Google lets you untick it. If it was unticked, the sign-in still succeeds, but mowteng cannot call the Search Console API on your behalf. Without that permission none of the Google tools can return data.
Fix it
- Connect Google again. Either start the sign-in from your assistant by asking a question that needs your data, or open the Google sign-in page.
- On Google's consent screen, check that the Search Console permission is ticked. Do not untick it.
- Choose the Google account that owns your site in Search Console, and finish the sign-in.
- Ask your assistant to list your properties.
List my Search Console properties and tell me whether mowteng has access to them.
If Google keeps showing the old consent, open the account page and use Disconnect next to Google first. That revokes the earlier grant and signs out every assistant, so the next sign-in shows the full consent screen again. Bing and Yandex stay connected.
Related messages that look similar
- “Please verify your Google account's email address, then connect again.” Google reports the account's email as unverified. Verify it in your Google account, then connect again.
- Access was revoked. If you removed mowteng from your Google account's permissions page, the assistant must connect mowteng again. Nothing else is needed.
- An empty list of properties. That points to a different Google account, not this permission. See no properties showing.
Why mowteng asks for it
The permission is what lets mowteng fetch your clicks, impressions and index status live for each request. mowteng does not store that search data. Sign-in works through OAuth, so mowteng never sees your Google password. If the sign-in goes wrong in other ways, MCP server not connecting has the full checklist.