Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Godot MCPWatchlist candidate | Google Search Console MCP Server for SEOsMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation io.github.tugcantopaloglu · Publisher source ↗ | Community implementation github:aminforou · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Jul 13, 2026 Package: Mar 7, 2026 | Repo: Jul 29, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 407 GitHub stars · checked 2026-08-14T18:46:26.000Z | 1,355 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 280 30-day package downloads · checked 2026-08-14T18:46:26.000Z | No reliable download data |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Default MCP transport is local stdio and runtime interaction listens on 127.0.0.1:9090. No authentication is documented. GODOT_MCP_ALLOWED_DIRS is optional; any project path is allowed when unset. | Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property. |
| Cost | The MIT-licensed project lists no MCP fee. Godot, Node.js, client, and model costs are separate. | The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented. |
| Permissions | Provides broad Godot project, scene, runtime, file, network, input, resource, and export control, including arbitrary GDScript evaluation, file read, write and delete, runtime mutation, and HTTP or WebSocket requests. | Lists Google Search Console properties and reads analytics, URL inspection, and sitemap data. Site and sitemap add/delete tools are disabled unless GSC_ALLOW_DESTRUCTIVE=true. |
| Data handling | Processes Godot files, scene data, runtime state, screenshots, logs, and errors locally; networking tools can send requests from the running game. Telemetry, retention, and model-training behavior are not documented. | Search Console properties, queries, pages, crawl and indexing results, and sitemap data are returned to the connected client. OAuth tokens are saved for reuse; service-account JSON is read from a configured path. Further retention is not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Arbitrary code, file deletion and modification, runtime mutation, and outbound networking create a broad trust boundary. Keep it local, set GODOT_MCP_ALLOWED_DIRS, and supervise destructive or networked calls. | Can expose private Search Console data and, when explicitly enabled, modify sites or sitemaps. Protect credential files, leave destructive tools disabled unless required, and restrict remote SSE deployments. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-08-11 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →