Claude Task Master vs Google Webtools MCP
A side-by-side look at the Claude Task Master and Google Webtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Google Webtools MCPDeveloper ToolsGoogle Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.51GoodAuth: oauth 2.0Verdict: choose Claude Task Master for developer tools work as a local process; choose Google Webtools MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Claude Task Master when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
GChoose Google Webtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_APPLICATION_CREDENTIALS. - You want tools like
list_properties, get_property_details, add_property.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Google Webtools MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | ANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS | GOOGLE_APPLICATION_CREDENTIALS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 28,227 | 7 |
| Directory activity | 9 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 39 |
| Full listing | View Claude Task Master | View Google Webtools MCP |
Tools & capabilities
Claude Task Master tools
No tool names declared yet. Check the project README from the listing page.
Google Webtools MCP tools 39
list_propertiesStarting point — see every GSC property you can access and your permission level on each.get_property_detailsCheck the type and permission level of one specific property.add_propertyRegister a new site in Search Console (verification is a separate step).delete_propertyDrop a property from the authenticated account's Search Console site list. Historical data is not destroyed — the property can be added back.list_sitemapsSee which sitemaps are submitted and whether Google reports errors or warnings.get_sitemap_detailsDrill into one sitemap: URL counts by content type, last download time, error and warning counts.submit_sitemapSubmit a new sitemap after publishing or moving one.delete_sitemapWithdraw a sitemap that is stale, duplicated, or returning errors.get_search_analyticsThe raw query — full control over dimensions, filters, search type, row limit, data state, aggregation. Use when the shaped tools below don't fit.get_performance_summary"How are we doing?" — clicks, impressions, CTR, position with period-over-period comparison. Trend advice is withheld when the previous period returned no data at all.compare_periodsCompare two explicit date ranges side by side (before/after a release, seasonal comparison).get_top_queriesTop queries by clicks, each scored against the CTR benchmark for its position.- +27 more on the listing page
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.
Claude Task Master
{
"mcpServers": {
"eyaltoledano-claude-task-master": {
"command": "npx",
"args": [
"-y",
"task-master-ai"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE",
"TASK_MASTER_TOOLS": "YOUR_TASK_MASTER_TOOLS_HERE"
}
}
}
}
Google Webtools MCP
No confirmed install command for Google Webtools MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Claude Task Master is categorized under Developer Tools and uses a local stdio subprocess. Google Webtools MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Claude Task Master for developer tools work and Google Webtools MCP for developer tools.
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. Google Webtools MCP has no confirmed install command yet — follow its own setup instructions.
Claude Task Master is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Google Webtools MCP has no declared pricing — check the project's own site. 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 eyaltoledano-claude-task-master and google-webtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Claude Task Master has a quality signal of 61/100 (Good) with 9 views, 0 installs and 28,227 GitHub stars. Google Webtools MCP has 51/100 (Good) with 0 views, 0 installs and 7 GitHub stars.