MCP access is coming soon. This guide explains the workflow; the connection URL and supported clients will be published when access opens.
What MCP does here
MCP lets your development tool query QueryTend directly. You do not need to reopen a dashboard or paste keyword tables for every question. Generating a report is not a prerequisite.
- Add a website you manage; connect Search Console when you need its search performance.
- Open MCP setup to obtain workspace connection information when the service is available.
- Configure a compatible client and authorize only the websites it needs.
- Query site context and data timestamps first, checking the correct workspace and site.
- Describe the optimization task and let your tool request relevant keywords, findings and page evidence.
A task prompt to use
Before optimizing my website, query QueryTend MCP for: 1. Site status, data sources and observation times; 2. Keywords and ranking changes for the page involved; 3. Existing findings, evidence and recommended scope. Do not guess when evidence is missing. Propose changes first and act only within my permissions. Report changed pages and request a live-page check. Do not equate deployment with ranking improvement.
Troubleshooting
- No site: check workspace, access scope and site setup.
- No search data: connect the correct GSC property; a new site may have little exposure.
- Old results: distinguish observation time, cached data and upstream delays.
- Limited query: narrow the scope and inspect quota or job status rather than retrying indefinitely.
A plain-text alternative
Copy the optimization report into your development tool. It reflects its export time. Use MCP when the next question needs a fresh lookup.