mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
Sam Sokolin
b01315dc14
Both mcp.json files declared $schema: https://cursor.com/schemas/mcp.json. parsePluginMcpConfig treats any $schema outside SUPPORTED_SCHEMA_IDS (the two agent-plugins.org 1.0.0 ids) as unsupported and returns null, so indexing found zero MCP servers and both plugins registered with no components. The Google plugins omit $schema entirely, which is why they were unaffected. Removing the key restores discovery. Co-authored-by: Cursor <cursoragent@cursor.com>
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
- Open Cursor Settings → Plugins.
- Search for Gong.
- 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.
- A Gong technical administrator creates an MCP integration under Company Settings → Ecosystem → API → Integrations and enables the MCP scope.
- Register both redirect URIs on that integration:
- Desktop:
http://localhost:8787/callback - Web and Cloud Agents:
https://www.cursor.com/agents/mcp/oauth/callback
- Desktop:
- In Dashboard → Plugins → Configure, set Gong Client ID and Gong Client Secret from that integration.
- 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
- Gong MCP server overview: https://help.gong.io/docs/about-gong-mcp-server
License
MIT