CipherHealth Cursor Plugins

Private team marketplace for the CipherHealth trial. Seven plugins — Salesforce, ZoomInfo, Seismic, Google Marketplace, Looker, HubSpot, and Gong — each with its own MCP server.

Repo: github.com/SolarCS/cursor-plugins

Plugins

Plugin	MCP server	Auth
CipherHealth Salesforce	platform/sobject-reads (read-only CRM)	OAuth on connect (Consumer Key bundled)
CipherHealth ZoomInfo	mcp.zoominfo.com via mcp-remote	OAuth on connect (requires Node.js)
CipherHealth Seismic	mcp.seismic.com/.../cipherhealth.com	Seismic MCP app Client ID + OAuth
CipherHealth Google Marketplace	cipher-mcp-365212235619.us-central1.run.app/mcp	OAuth on connect
CipherHealth Looker	insightsqaload.cipherhealth.dev/mcp (HTTP)	OAuth on connect
CipherHealth HubSpot	mcp.hubspot.com via mcp-remote (port 3334)	OAuth 2.1 + PKCE (Client ID bundled, requires Node.js)
CipherHealth Gong	mcp.gong.io/mcp via mcp-remote (port 8787)	OAuth + PKCE (Client ID + Secret via env vars, scopes mcp:ai-ask:read + mcp:ai-briefer:read, requires Node.js)

Salesforce has the Consumer Key bundled. Seismic and Gong require env vars (Gong needs both Client ID and Secret — it does not support Dynamic Client Registration). ZoomInfo, HubSpot, and Gong require Node.js for the mcp-remote OAuth bridge. Google uses the CipherHealth marketplace proxy — connect via OAuth in Cursor.

mcp-remote-based plugins each pin a distinct local OAuth callback port so they never collide: HubSpot = 3334, Gong = 8787. Each provider's OAuth app must register http://localhost:<port>/oauth/callback (and the 127.0.0.1 variant).

Connecting Gong? Non-technical teammates should follow the step-by-step Gong connection guide (Mac & Windows).

Admin: publish to team marketplace

1. Push to SolarCS/cursor-plugins.
2. Cursor Dashboard → Settings → Plugins → Team Marketplaces
3. Import from Repo (or Refresh if already imported) → https://github.com/SolarCS/cursor-plugins
4. Grant the Cursor GitHub App read access to this repo.
5. Cursor reads .cursor-plugin/marketplace.json and discovers all five plugins.
6. Set Marketplace Access to All Members.
7. Mark each plugin Required (or Optional per role) → Save.

After this restructure, re-import or refresh the marketplace so the old CipherHealth Integrations bundle is replaced by the three individual plugins.

See TEAM-TROUBLESHOOTING.md if plugins work for admins but not teammates.

Trial user: first run

1. Plugins auto-install (if Required).
2. Settings → Tools & MCP → Connect for Salesforce, zoominfo, Seismic, google, looker-qaload, HubSpot, and Gong.
3. Test in chat.

Skills included

Plugin	Skills
Salesforce	salesforce-setup, salesforce-queries
ZoomInfo	zoominfo-setup
Seismic	seismic-setup
Google Marketplace	google-marketplace-setup
Looker	looker-setup
Gong	gong-setup

Repository structure

.cursor-plugin/
  marketplace.json
plugins/
  salesforce/
    .cursor-plugin/plugin.json
    mcp.json
    skills/
  zoominfo/
    .cursor-plugin/plugin.json
    mcp.json
    skills/
  seismic/
    .cursor-plugin/plugin.json
    mcp.json
    skills/
  google/
    .cursor-plugin/plugin.json
    mcp.json
    skills/
  looker/
    .cursor-plugin/plugin.json
    mcp.json
    skills/
  hubspot/
    .cursor-plugin/plugin.json
    mcp.json
  gong/
    .cursor-plugin/plugin.json
    mcp.json
    skills/

Maintainers

• Bump version in each plugin's .cursor-plugin/plugin.json when changing that plugin's mcp.json or skills.
• Bump metadata.version in .cursor-plugin/marketplace.json when changing marketplace-level config.
• Enable Auto Refresh on the team marketplace for pushes to main.

Internal use only — CipherHealth / SolarCS.