[cursor]

Unreviewed plugin submission. Generated automatically from a partner submission form; nothing here has been reviewed or tested against the live server yet.

Submission

• Publisher handle: delivra
• Company: Delivra (https://delivra.com)
• Contact: Amaan Gokak agokak@delivra.com
• plugin_url: https://integration.delivra.com/mcp (remote MCP server, used as-is)
• Listing targets: Grok, Cursor, Grok Bot

Testing instructions (from submitter)

Login with the following email/pass:
Email: aitester@example.com
Password: (redacted from this public PR — see the original submission record)

Changes

• third_party/delivra/ with .cursor-plugin/plugin.json (mcpServers: ./mcp.json), mcp.json (HTTP server delivra → submitted URL), README, CHANGELOG, LICENSE.
• Logo: assets/logo.svg, downloaded from the submitted logo_url (valid 128×128 SVG, no scripts).
• Row added to the root README integrations table; entry appended to .cursor-plugin/marketplace.json. .claude-plugin/marketplace.json unchanged.
• node scripts/validate-plugins.mjs passes.

Notes for reviewer

• The submitted description said "directly in Claude"; the listing description drops that phrase.
• integration.delivra.com was not reachable from the build sandbox, so auth type (OAuth vs. other) and tool list were not verified.

  

---

Note

Medium Risk
New unreviewed third-party hosted MCP endpoint; users authenticate to Delivra and agent capabilities depend on a remote server that was not verified in CI.

Overview
Adds a new Delivra third-party integration so Cursor agents can reach Delivra’s hosted MCP at https://integration.delivra.com/mcp for email/SMS campaign analytics, subscriber engagement, domains, and poll reporting.

The PR introduces third_party/delivra/ with the standard plugin bundle (plugin.json → ./mcp.json, README, CHANGELOG, MIT license, and logo SVG) and wires delivra into the root .cursor-plugin/marketplace.json and README integrations table. The MCP config is a single HTTP server entry with no in-repo server code—tool behavior and auth live on Delivra’s side.

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

[cursor]

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

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

• ✅ Fixed: Missing Grok Bot server placement
  • Added "placement": "server" to the Delivra hosted HTTP MCP entry so Grok Bot dials the partner server and can show a connect card.

Or push these changes by commenting:

@cursor push cd3d02c36f

Preview (cd3d02c36f)

diff --git a/third_party/delivra/mcp.json b/third_party/delivra/mcp.json
--- a/third_party/delivra/mcp.json
+++ b/third_party/delivra/mcp.json
@@ -2,7 +2,8 @@
   "mcpServers": {
     "delivra": {
       "type": "http",
-      "url": "https://integration.delivra.com/mcp"
+      "url": "https://integration.delivra.com/mcp",
+      "placement": "server"
     }
   }
 }

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

^{Reviewed by Cursor Bugbot for commit 8da83ce. Configure here.}

[cursor]

Missing Grok Bot server placement

Medium Severity · Logic Bug

The submission lists Grok Bot as a target, but the delivra HTTP server in mcp.json omits "placement": "server". Partner-hosted MCP rows without that field stay UNDECIDED on Grok Bot and never show a connect or sign-in card, so this listing will not actually connect there.

 

^{Reviewed by Cursor Bugbot for commit 8da83ce. Configure here.}