Files
roshansada 08631ab2ef Shorten plugin descriptions
Replace "Connect to [tool]" openers, em-dash asides, and MCP server
boilerplate with brief verb-first copy in plugin and marketplace
manifests. Resync the README table that mirrors them, adding rows that
had drifted out (teaching, ralph-loop, playwright, github, zoom, clay).
Also refresh the stale read-only X marketplace copy and clean em-dashes
from the Salesforce server URL help text.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-17 18:34:06 -07:00
..

Gong

Cursor plugin that connects agents to Gong through Gong's official hosted Model Context Protocol server.

Pull account summaries, deal insights, and call briefs into chat.

Install

  1. Open Cursor Settings → Plugins.
  2. Search for Gong.
  3. Click Install, then set the client ID and secret (below) and complete the Gong sign-in prompt.

Or run /add-plugin gong in chat.

MCP

{
  "mcpServers": {
    "gong": {
      "url": "https://mcp.gong.io/mcp",
      "auth": {
        "CLIENT_ID": "${CLIENT_ID}",
        "CLIENT_SECRET": "${CLIENT_SECRET}"
      }
    }
  }
}

Setup

Gong's MCP server uses static OAuth client credentials plus a per-user OAuth login, so an administrator has to register Cursor before anyone can connect.

  1. A Gong technical administrator creates an MCP integration under Company Settings → Ecosystem → API → Integrations and enables the MCP scope.
  2. Register both redirect URIs on that integration:
    • Desktop: http://localhost:8787/callback
    • Web and Cloud Agents: https://www.cursor.com/agents/mcp/oauth/callback
  3. In Dashboard → Plugins → Configure, set Gong Client ID and Gong Client Secret from that integration.
  4. Complete the Gong OAuth login when Cursor prompts.

On a team marketplace an admin sets the client ID and secret once for everyone; each member still completes their own Gong OAuth login, so tool calls run with that member's Gong permissions.

Docs

License

MIT