Skip to content

Add Skydropx plugin (third-party submission, unreviewed) - #1026

Open
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/new-plugin-setup-7a14
Open

cursor[bot] wants to merge 1 commit into
mainfrom
cursor/new-plugin-setup-7a14

Conversation

@cursor

@cursor cursor Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

This is an unreviewed third-party plugin submission. Please convert this PR to a draft; the automation that opened it has no draft option. Do not merge until someone has reviewed it.

Summary

Adds third_party/skydropx/, a remote MCP plugin for Skydropx: quote, buy, and track shipments across Mexico's main carriers, print labels, schedule pickups, and manage store orders.

  • mcp.json with the skydropx server (type: http, url: https://mcp.skydropx.com), referenced from .cursor-plugin/plugin.json as "mcpServers": "./mcp.json" (same layout as PitchBook in Add PitchBook third-party MCP plugin #796)
  • .cursor-plugin/plugin.json, README.md, CHANGELOG.md, LICENSE, assets/logo.png
  • One entry appended to .cursor-plugin/marketplace.json and one row in the root README integrations table. .claude-plugin/marketplace.json is unchanged.

Submission

URL to check: plugin_url is https://mcp.skydropx.com (no path), and mcp.json uses it exactly as submitted. The testing instructions say to add the connector at https://mcp.skydropx.com/mcp. A reviewer should confirm which endpoint is right and update mcp.json and the README if it should be /mcp.

Testing instructions (as submitted)

Add the connector with URL https://mcp.skydropx.com/mcp. No client credentials needed (dynamic client registration).
When prompted, sign in with the test account:
email: [email protected]
password: [redacted from this public PR; see the original submission]
The account has no MFA, no email/SMS codes.
Accept read and write permissions.
The account is pre-loaded with balance, 2 shipments with tracking, saved addresses and a store with sample orders. Purchases are charged to its balance; "cancel label " reverts them where the carrier allows.

Logo

The submitted logo_url (https://ps.w.org/skydropx/assets/icon-128x128.png) could not be fetched from the build sandbox (TLS connection blocked), and neither could skydropx.com or its favicon. The committed assets/logo.png is the avatar of the official Skydropx GitHub organization (https://avatars.githubusercontent.com/skydropx, 420×420 PNG; the org lists https://skydropx.com as its site). A reviewer may want to swap in the submitted WordPress icon.

Verification

  • node scripts/validate-plugins.mjs passes.
  • The MCP server could not be probed from the sandbox (mcp.skydropx.com was blocked), so the README's capability table is based on the submission description, not on tools/list.
Open in Web View Automation 

Note

Medium Risk
New third-party remote MCP with OAuth and write actions (label purchases charged to the user’s Skydropx balance); repo changes are manifests/docs only, but the listed endpoint wasn’t probed in CI.

Overview
Adds a new Skydropx third-party integration under third_party/skydropx/, wiring agents to Skydropx’s hosted HTTP MCP at https://mcp.skydropx.com via mcp.json and plugin.json (OAuth with dynamic client registration; no local API keys).

The change also registers the plugin in the marketplace (.cursor-plugin/marketplace.json) and documents it in the root README integrations table, with install/README copy covering rates, labels, tracking, pickups, and store orders.

This is an unreviewed third-party submission; reviewers should confirm the correct MCP base URL (submission tests mention …/mcp while the committed config uses the host root) and exercise OAuth plus label purchase flows before merge.

Reviewed by Cursor Bugbot for commit 1fd2505. Bugbot is set up for automated code reviews on this repo. Configure here.

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Grok Bot missing server placement
    • Added "placement": "server" to the Skydropx HTTP MCP server so Grok Bot can show a connect card instead of leaving the row UNDECIDED.

Create PR

Or push these changes by commenting:

@cursor push 2631acab7f
Preview (2631acab7f)
diff --git a/third_party/skydropx/mcp.json b/third_party/skydropx/mcp.json
--- a/third_party/skydropx/mcp.json
+++ b/third_party/skydropx/mcp.json
@@ -2,7 +2,8 @@
   "mcpServers": {
     "skydropx": {
       "type": "http",
-      "url": "https://mcp.skydropx.com"
+      "url": "https://mcp.skydropx.com",
+      "placement": "server"
     }
   }
 }

You can send follow-ups to the cloud agent here.

Reviewed by Cursor Bugbot for commit 1fd2505. Configure here.

"skydropx": {
"type": "http",
"url": "https://mcp.skydropx.com"
}

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grok Bot missing server placement

High Severity · Logic Bug

The Skydropx server object has no "placement": "server", but this listing targets Grok Bot. Without that field Grok Bot leaves the row UNDECIDED and never shows a connect or sign-in card, so the integration is unusable there.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 1fd2505. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant