Repository navigation
Add Google Search plugin - #554
Open
acedatacloud-dev wants to merge 4 commits into
Open
acedatacloud-dev wants to merge 4 commits into
acedatacloud-dev wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
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.
acedatacloud-dev
force-pushed
the
codex/google-search-plugin
branch
from
October 14, 2026 04:58
f88150c to
e99577f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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
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
Marketplace and docs-only addition with no core app changes; users supply third-party API tokens and outbound calls go to Ace Data Cloud’s hosted MCP.
Overview
Adds a new
google-searchthird-party Cursor plugin so Agent can run Google web searches via Ace Data Cloud’s hosted serp MCP (serp_google_search).The change registers the plugin in
.cursor-plugin/marketplace.jsonand the root README plugin table, and introducesthird_party/google-search/with manifest (ACEDATACLOUD_API_TOKEN), HTTPmcp.json, an Agent skill, EN/zh setup docs, a first-run example, changelog, and MIT license. It is a tool/MCP integration only—not a chat model provider.Reviewed by Cursor Bugbot for commit e99577f. 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
233ce5ec9b7201d54cc181b82c8e44f4c60c0ea9at heade99577fb46cbc13c080c801294fc496b129c7927:node scripts/validate-plugins.mjsandgit diff --checkpass, and merge-tree with the pinned base is clean. GitHubupdateRefswas used with an atomicbeforeOidlease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.