Skip to content

Add Stirling ONE (Stirlingshire) plugin - #1046

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
add-stirlingshire-plugin
Draft

cursor[bot] wants to merge 1 commit into
mainfrom
add-stirlingshire-plugin

Conversation

@cursor

@cursor cursor Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Unreviewed plugin submission. This PR was generated automatically from a submission form and has not been reviewed. Do not merge until someone has checked the MCP server, the logo, and the listing copy.

Submission

Changes

  • third_party/stirlingshire/mcp.json: remote MCP server stirlingshire (type: http) with the submitted URL https://app.stirlingshire.net/, unchanged.
  • third_party/stirlingshire/.cursor-plugin/plugin.json: category integrations, "mcpServers": "./mcp.json", "logo": "assets/logo.png". Same layout as PitchBook (Add PitchBook third-party MCP plugin #796).
  • README, CHANGELOG, and LICENSE for the plugin.
  • One entry added to .cursor-plugin/marketplace.json and one row added to the root README integrations table. .claude-plugin/marketplace.json is unchanged.

Things to check

  • MCP URL: https://app.stirlingshire.net/ looks like the web app's sign-in page, not an MCP endpoint. I couldn't reach it from the build VM, so I haven't confirmed that it speaks MCP. Please confirm the endpoint with the submitter before merging.
  • Logo: I couldn't download the submitted logo_url (https://stirlingshire.com/stirlingshire-logo-plate.png) because the TLS connection failed from the build VM. assets/logo.png is the 256×256 griffin crest from the Stirlingshire GitHub organization avatar. Please check that it matches their official brand.
  • Description: the submitted description had marketing and competitor claims, so the listing copy is a neutral summary instead.

Testing instructions (from the submitter)

Go to https://app.stirlingshire.net and sign in with:
Email: [email protected]
Temporary password: [redacted: this repository is public. The password is in the original submission, or ask the submitter]
On first sign-in you'll be asked to set a new password and to set up an authenticator app (any TOTP app, such as Google Authenticator or 1Password) by scanning the QR code shown. Please save the setup key from that step if more than one person on your team will test. Don't use "Forgot password" (that mailbox isn't monitored); if you need a reset, contact us and we'll reset it. The account is a test advisor: explore client households, portfolios, meeting prep and the AI.

node scripts/validate-plugins.mjs passes.

Open in Web View Automation 

Note

Medium Risk
New third-party hosted MCP for advisor wealth-management data; merge should wait on confirming the URL is a real MCP endpoint and reviewing branding/auth behavior noted in the PR.

Overview
Adds a new Stirling ONE third-party integration so Cursor agents can reach Stirlingshire’s wealth-management platform via a hosted HTTP MCP server.

The change introduces third_party/stirlingshire/ with the standard plugin bundle (plugin.json → ./mcp.json, README, CHANGELOG, MIT LICENSE) and wires mcp.json to https://app.stirlingshire.net/. Listing copy positions the plugin around households, portfolios, and meeting prep, with advisor sign-in documented in the README.

Marketplace surfacing: one new entry in .cursor-plugin/marketplace.json and a matching row in the root README integrations table (stirlingshire / Stirling ONE).

Reviewed by Cursor Bugbot for commit adfe168. 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 could not resolve the issue found in the latest run.

  • ⚠️ Could not fix: MCP URL is web app
    • The configured URL is the Stirling ONE advisor sign-in origin, but no documented Streamable HTTP MCP endpoint exists to replace it, so the listing was left unchanged instead of guessing a path.

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

Reviewed by Cursor Bugbot for commit adfe168. Configure here.

"mcpServers": {
"stirlingshire": {
"type": "http",
"url": "https://app.stirlingshire.net/"

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.

MCP URL is web app

High Severity · Logic Bug

The url in mcp.json is https://app.stirlingshire.net/, the Stirling ONE advisor sign-in origin rather than a Streamable HTTP MCP path. Cursor will get HTML or a login redirect instead of MCP, so the plugin cannot list tools or run household, portfolio, or meeting workflows.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit adfe168. 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