| FMRS | 47 / 100 · D | 69 / 100 · C | 67 / 100 · C |
|---|
| Reliability | 6 / 20 | 11 / 20 | 10 / 20 |
|---|
| Security and permissions | 3 / 20 | 15 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 15 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 14 / 20 | 16 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 | 13 / 20 |
|---|
| Best for | - Developers and teams wanting to integrate deployment into AI workflows
- Users already using Google Cloud and Cloud Run
- AI agents that need to quickly prototype or deploy applications
| - SEO professionals
- Content marketers
- Website owners
- Developers integrating Search Console data into their applications or workflows.
| - Users who want to integrate AI assistants (like Claude Desktop or IDEs) with a self-hosted Nextcloud instance.
- Developers and power users who need deep CRUD operations across multiple Nextcloud apps.
- Teams that prefer Docker or Kubernetes deployment.
|
|---|
| Not for | - Deployments requiring local hosting or other cloud provider support
- Users wanting fine-grained IAM control without skipping permission checks
- Seeking GitOps or fully automated CI/CD without MCP/CLI
| - Users without a Google Cloud project or Search Console access.
- Those needing real-time data (default is final data, but 'all' option exists).
- Non-technical users may find setup challenging due to required Google Cloud configuration.
| - Users who don't want to self-host (consider managed service Astrolabe Cloud).
- Users who need only simple read-only access (this server is more comprehensive).
- Users who require official support (it is not an official Nextcloud project).
|
|---|
| Required permissions | - Requires Google Cloud IAM credentials to access Cloud Run APIs.
- Authentication via `gcloud auth login` and `gcloud auth application-default login`.
- Deployment requires appropriate Cloud Run permissions like `run.services.create` and `run.services.update`.
- Project creation requires permissions like `resourcemanager.projects.create`.
| - Requires a Google Cloud service account key with access to the Search Console API.
- The service account must be granted property administrator rights in Search Console.
- The server reads the key via environment variable, typically for external services.
| - Requires a Nextcloud username and app password (or OAuth).
- Read/write access to the selected Nextcloud apps (Notes, Calendar, Contacts, Files, etc.).
- For semantic search, needs external services: Qdrant and Ollama (disabled by default).
|
|---|
| Risks and side effects | - Using remote MCP server without authentication may lead to unauthorized access.
- IAM checks are skipped by default (`SKIP_IAM_CHECK=true`), potentially allowing overly permissive access.
- Deploying file contents may expose sensitive data if provided in prompts.
- DNS rebinding risk unless host validation is enabled (`ENABLE_HOST_VALIDATION`).
| - Credential leak risk: If the service account key is not stored securely, data may be exposed. Use secret management services.
- Data access scope: The service account can access all authorized Search Console properties, including sensitive performance data.
- This is a third-party project, not an official Google server, and may not have undergone security auditing. Evaluate trustworthiness before use.
- Potential Google Cloud API costs, though Search Console API is usually free within quotas.
| - Credential storage with app passwords may pose a security risk if exposed.
- The server can access a user's full Nextcloud data, so proper access controls are necessary.
- Experimental semantic search relies on external services, which may introduce security and privacy issues.
- Tag-based exclusion (EXCLUDED_TAGS) depends on system tags to hide sensitive files, misconfiguration could expose data.
|
|---|
| Supported clients | Gemini CLI, Claude Desktop, VSCode, Cursor, Windsurf, Antigravity | Claude Desktop | Claude Desktop |
|---|
| Tools | 7 | 1 | 13 |
|---|