Prepublish MCP vs QuerySail: Google Search Console MCP
A side-by-side look at the Prepublish MCP and QuerySail: Google Search Console MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Prepublish MCPMarketing · Local subprocess (stdio)Audit YouTube scripts before recording: hook, structure and pacing scores, drop-off passages, policy and inauthentic-content checks, and runtime estimates.57GoodAuth: no auth requiredVerdict: choose Prepublish MCP for marketing work as a local process; choose QuerySail: Google Search Console MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Prepublish MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
audit_script, get_audit, audit_hook.
Choose QuerySail: Google Search Console MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_properties, get_performance, compare_performance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Prepublish MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 57/100 · Good | 77/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 5 |
| Full listing | View Prepublish MCP | View QuerySail: Google Search Console MCP |
Tools & capabilities
Prepublish MCP tools 6
audit_scriptFull audit of a finished draft: hook, structure and pacing scores, an attention-risk map naming the passages most likely to lose viewers, and a rewrite. Returns the analysis and its idget_auditCollect an earlier audit by `analysis_idaudit_hookPer-sentence attention pull across the opening, curiosity gap, payoff distance, a grade, and rewritten alternativescheck_authenticityReused, templated or mass-produced content risk, with the quotes that fired each signalpolicy_preflightWhich YouTube policy families a script touches, each citing YouTube's own pagescript_runtimeWords to runtime and runtime to a word budget, at 160, 181 and 201 words per minute measured across 349 videos
QuerySail: Google Search Console MCP tools 5
list_propertiesLists the Search Console properties your connected Google accounts can read, with exact IDs and permission level.get_performanceClicks, impressions, CTR and average position, as totals or by date, hour, query, page, country, device or search appearance, with filters. Covers web, image, video, news, Discover and Google News results.compare_performanceCompares two periods (previous period, same weekdays a year earlier, or custom dates) and lists the queries, pages, countries or devices that gained or lost the most.inspect_urlsInspects up to 20 URLs: whether each is on Google, why not, last crawl, robots.txt and noindex blocking, and the canonical Google chose.list_sitemapsLists submitted sitemaps with when Google last read them, URL counts, errors and warnings.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Prepublish MCP
{
"mcpServers": {
"prepublish-prepublish-mcp": {
"command": "npx",
"args": [
"-y",
"prepublish-mcp"
]
}
}
}
QuerySail: Google Search Console MCP
{
"mcpServers": {
"querysail-google-search-console-mcp": {
"url": "https://mcp.querysail.com/gsc/mcp"
}
}
}
Frequently asked questions
Prepublish MCP is categorized under Marketing and uses a local stdio subprocess. QuerySail: Google Search Console MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick Prepublish MCP for marketing work and QuerySail: Google Search Console MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Prepublish MCP has no declared pricing — check the project's own site. Auth: no auth required. QuerySail: Google Search Console MCP is listed as a paid service. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add prepublish-prepublish-mcp and querysail-google-search-console-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Prepublish MCP has a quality signal of 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars. QuerySail: Google Search Console MCP has 77/100 (Great) with 2 views, 0 installs and 0 GitHub stars.