[cursor]

Unreviewed third-party plugin submission. Nobody at Cursor has reviewed this plugin or tested the MCP server yet. Do not merge without review.

Summary

Adds third_party/seltz/, a remote MCP plugin for Seltz web search and fetch.

• mcp.json uses the submitted hosted URL as-is (https://mcp.seltz.ai/mcp, type: http), and .cursor-plugin/plugin.json points to it with "mcpServers": "./mcp.json". This follows the PitchBook layout in Add PitchBook third-party MCP plugin #796.
• assets/logo.png was downloaded from the submitted logo_url (a 460×460 PNG avatar of the seltz-ai GitHub organization, which links to seltz.ai).
• Adds a README, one row in the root README integrations table, and one entry in .cursor-plugin/marketplace.json. .claude-plugin/marketplace.json is unchanged.
• node scripts/validate-plugins.mjs passes.

Submission details

• Publisher handle: seltz
• Company: Seltz
• Contact: Matteo Pietra, matteo@seltz.ai (contact during review: chris@seltz.ai)
• plugin_url: https://mcp.seltz.ai/mcp
• Website: https://seltz.ai/
• Logo URL: https://avatars.githubusercontent.com/u/218088754?s=460&v=4
• Listing targets: Grok, Grok Bot, Cursor

Testing instructions (from the submitter)

• MCP server: https://mcp.seltz.ai/mcp
• Header: Authorization: Bearer <test API key>. The submitter included a test key with credits in the submission. It is left out of this public PR; get it from the original submission or from the contact.
• Docs: https://docs.seltz.ai/integrations/mcp
• Test prompt: "Use Seltz to find the most recent funding round announced by an AI compute or inference infrastructure company, then fetch the official announcement and summarize the amount, lead investors and use of funds."
• Expected: the agent uses search and fetch and returns a sourced summary.
• Contact during review: chris@seltz.ai

Notes for reviewers

• The server uses an API key sent as a Bearer header. mcp.json only stores the URL, so check how Cursor asks users for the key when they install.
• The automation environment could not reach mcp.seltz.ai or docs.seltz.ai (TLS connection reset), so the server and its auth flow were not checked here.

  

---

Note

Medium Risk
Unreviewed third-party submission that exposes users to an external MCP endpoint and API keys; repo changes are metadata-only but merge should follow manual server and auth review.

Overview
Adds a new Seltz third-party integration under third_party/seltz/, wiring agents to Seltz’s hosted HTTP MCP at https://mcp.seltz.ai/mcp for web search and page fetch (with source URLs), using Bearer API key auth documented in the README.

Listing updates register the plugin in .cursor-plugin/marketplace.json and the root README integrations table (author Seltz). The bundle includes plugin.json, mcp.json, README, and logo assets—same remote-MCP layout as other URL-only integrations like PitchBook.

^{Reviewed by Cursor Bugbot for commit d85f2ca. 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 API key auth wiring
  • Added a required SELTZ_API_KEY variable and an Authorization Bearer header so install collects the key and every hosted MCP request sends it.

Or push these changes by commenting:

@cursor push 1c331d0aed

Preview (1c331d0aed)

diff --git a/third_party/seltz/.cursor-plugin/plugin.json b/third_party/seltz/.cursor-plugin/plugin.json
--- a/third_party/seltz/.cursor-plugin/plugin.json
+++ b/third_party/seltz/.cursor-plugin/plugin.json
@@ -25,5 +25,18 @@
     "web",
     "mcp"
   ],
+  "variables": {
+    "type": "object",
+    "properties": {
+      "SELTZ_API_KEY": {
+        "type": "string",
+        "title": "Seltz API key",
+        "description": "API key from https://console.seltz.ai/api-keys. Sent as Authorization: Bearer <key>."
+      }
+    },
+    "required": [
+      "SELTZ_API_KEY"
+    ]
+  },
   "mcpServers": "./mcp.json"
 }

diff --git a/third_party/seltz/README.md b/third_party/seltz/README.md
--- a/third_party/seltz/README.md
+++ b/third_party/seltz/README.md
@@ -19,13 +19,16 @@
   "mcpServers": {
     "seltz": {
       "type": "http",
-      "url": "https://mcp.seltz.ai/mcp"
+      "url": "https://mcp.seltz.ai/mcp",
+      "headers": {
+        "Authorization": "Bearer ${SELTZ_API_KEY}"
+      }
     }
   }
 }

-Seltz authenticates with an API key sent as Authorization: Bearer <your-seltz-api-key>. See the Seltz MCP docs for how to get a key.
+Seltz authenticates with an API key sent as Authorization: Bearer ${SELTZ_API_KEY}. Create one at https://console.seltz.ai/api-keys, then set it when Cursor prompts during install. See the Seltz MCP docs.

What agents can do

diff --git a/third_party/seltz/mcp.json b/third_party/seltz/mcp.json
--- a/third_party/seltz/mcp.json
+++ b/third_party/seltz/mcp.json
@@ -2,7 +2,10 @@
"mcpServers": {
"seltz": {
"type": "http",

•  "url": "https://mcp.seltz.ai/mcp"
  

•  "url": "https://mcp.seltz.ai/mcp",
  

•  "headers": {
  

•    "Authorization": "Bearer ${SELTZ_API_KEY}"
  

•  }
  

  }
  }
  }

</details>


<sub>You can send follow-ups to the cloud agent <a href="https://cursor.com/agents/bc-90a0ac6e-1169-41a5-bb00-7a3394c2fc9f">here</a>.</sub>
<!-- BUGBOT_AUTOFIX_REVIEW_FOOTNOTE_END -->

<sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit d85f2ca28865a48a341c470e8d0ca55cf0392a65. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>

[cursor]

Missing API key auth wiring

High Severity · Logic Bug

Seltz authenticates with a Bearer API key, but mcp.json has no headers mapping and plugin.json defines no variables. Install never collects a key or sends Authorization, so the hosted MCP rejects every request.

Additional Locations (2)

• third_party/seltz/.cursor-plugin/plugin.json#L20-L29
• third_party/seltz/README.md#L10-L28

 

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