Add Google Search plugin

[acedatacloud-dev]

Summary

Add a separately searchable Google Search third-party Cursor plugin. It reuses the existing Ace Data Cloud hosted serp MCP, a focused Agent skill, and the exact service logo from the Ace Data Cloud GoogleSearch integration. The English and Chinese guides cover installation, service API key, permissions, one first-run prompt, task retrieval where applicable, result inspection, Credits, and troubleshooting.

Standalone source is reviewable at AceDataCloud/GoogleSearchCursor#1 and its exact commit AceDataCloud/GoogleSearchCursor@97ebb42. This is a tool plugin, not a Cursor chat-model provider.

Validation

• Official node scripts/validate-plugins.mjs: passed with this marketplace entry.
• git diff --check: passed. Logo SHA-256: cf8b5ead614e5ef7aed0f0a3de1b490563a3812c00f5328ec66d8efc16a2bfc1.
• Authenticated hosted MCP tools/list exposed serp_google_search; its live schema includes the first-run parameters. This is a read-only tool/schema check, not a claim of a new paid generation or a Cursor UI install.

Publication state

This PR is a formal submission. Review, merge, Marketplace listing and search, user installation, and a Cursor Agent call remain separate gates. Cursor 3.24.12 is signed in; this plugin's own UI installation and Agent call have not yet been verified. No credential is committed.

---

Note

Low Risk
Additive marketplace listing and isolated third-party plugin metadata; no core repo logic changes, though users must supply an external API token for paid search calls.

Overview
Adds a new google-search third-party integration to the marketplace catalog and root plugin table, alongside a full plugin package under third_party/google-search/.

The plugin wires Cursor Agent to Ace Data Cloud’s hosted serp HTTP MCP (serp_google_search), with a required ACEDATACLOUD_API_TOKEN plugin variable, an agent skill, MIT license, and English/Chinese setup docs plus a first-run prompt example. It is a tool/MCP plugin only (not a chat model provider), with Cursor 3.13.0+ as the minimum client version.

^{Reviewed by Cursor Bugbot for commit 39dd9aa. Bugbot is set up for automated code reviews on this repo. Configure here.}

README attribution: the shared English/Chinese CTA links are tagged with opensource / referral / evergreen, with service/Cursor/language content values. Matching source documentation is proposed at AceDataCloud/GoogleSearchCursor#2. This is a documentation-only update; source merge, official indexing, public search/install and measured activation remain separate gates.

2026-10-14 base refresh

Rebased onto current official main ce649c03ac3b75b6ae80cbd15b7e2c536caedb5a. The catalog and root README retain all 102 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (631224aaba24fd1b46d521347e016859726460a2), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree 233ce5ec9b7201d54cc181b82c8e44f4c60c0ea9 at head e99577fb46cbc13c080c801294fc496b129c7927: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-15 base refresh

Rebased onto current official main 850d7f2e9f5e55dff7eb00a0a479337fe79eb22f. The catalog and root README retain all 104 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (631224aaba24fd1b46d521347e016859726460a2), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree 02bf92c02c52312f870f23946af4266813308cc6 at head 6e34e664ec1ff5ce7c6e78336bf5801224e86ad7: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-18 native-distribution update

Updated onto current official main 101b274dd991f694e1f7024be2157e5f3adf07de. All 109 existing catalog entries and the full upstream README are preserved, including the revised Tailscale text. The plugin directory remains unchanged (631224aaba24fd1b46d521347e016859726460a2). This update only resolves the catalog/root README conflict against the latest official base.

Validation at 39dd9aa20e5a0cf555eb50de0bfd47f447faefe1: current node scripts/validate-plugins.mjs, node scripts/generate-pstack-harness-trees.mjs --check, git diff --check and merge-tree pass. Published Git commit/tree SHAs equal the locally validated objects. Every original OPEN branch update uses atomic beforeOid comparison. No duplicate submission, PR merge, deployment, paid generation or publisher agreement acceptance. Official review, live service-name search, installation and actual Cursor use remain separate gates.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 162b239. Configure here.}