Use Antigravity with mowteng to ask about your Search Console clicks, queries and indexing. Connect once, then start with a question about your own site.Connect Antigravity
For Antigravity CLI, add the server:
agy mcp add mowteng https://mowteng.app/mcpThen run /mcp in Antigravity CLI and sign in with Google. Antigravity CLI replaced Gemini CLI. For the Antigravity app, add this entry to mcp_config.json:
{"mcpServers": {"mowteng": {"serverUrl": "https://mowteng.app/mcp"}}}Leave the Search Console permission ticked during Google sign-in.
mowteng uses one remote MCP URL and Google sign-in. There is no Google Cloud project, API key or OAuth client of your own to set up. The connection guide explains the shared setup.
Start with your properties
Choose the setup for the client you use: the app configuration and CLI command both point to the same remote MCP URL. Begin with a property list so the assistant can identify the correct site before it starts a performance comparison.
List my Search Console properties, then show which pages on the busiest one lost the most clicks in the last 28 days.
Confirm the property the assistant chose before acting on the report. Ask it to include the earlier period, the current period and the click change for each page.
Turn the result into a useful next check
Ask Antigravity for pages with high-impression queries at average positions 11–20. Then inspect the query intent and the page that already receives those impressions. Use the result as a shortlist for review; average position summarizes many impressions and does not promise a fixed rank for every search.
Use content decay analysis for declining pages, or ask for striking distance keywords when you want a list of queries close to page one. You can also inspect an individual URL to check its indexing and canonical.
Troubleshoot access and keep changes deliberate
If no properties appear, check whether you used the Google account that owns the site. See no properties showing. If access was not granted, reconnect with the Search Console permission ticked.
Search data is fetched live for each request and never stored by mowteng. Write actions, such as submitting a sitemap, are marked so assistants ask before running them. mowteng never edits your site pages. Review any proposed page changes in your own workflow.