Four MCP servers for Gong, Salesforce, Datadog, and Letta
By RepoJournal , from @bgrgndzz's public GitHub activity
Backfilled
1 person shipped this
Buğra Gündüz shipped four Model Context Protocol servers across four repositories, each providing structured access to a different SaaS API for use with Claude.
The gong-mcp server [1] connects to the Gong API with tools for listing and searching calls, retrieving transcripts and call details including attendees and next steps, and managing users via API key and secret authentication. Gündüz scoped the npm package name to @bgrgndzz/gong-mcp [2] after finding the unscoped name already taken. He then added a find-calls-by-company tool [3] that works around Gong's lack of server-side company filtering by fetching calls in a date range and matching client-side against CRM context objects, party-level CRM associations, participant email domains, affiliations, and call titles. A type coercion bug in company matching [4] was fixed, and performance was improved by paginating results and stopping once enough matches were found, adding a safety cap of 2000 scanned calls. The gong-mcp package went through releases 0.1.1 [5], 0.1.2 [6], and 0.1.3 [7].
The salesforce-query-mcp server [8] provides SOQL query execution and Salesforce object describe calls. Gündüz simplified authentication [9] by removing the browser-based OAuth flow and instead reading the refresh token from an environment variable, reducing setup friction.
The datadog-mcp server [10] exposes tools for searching, retrieving, and aggregating Datadog logs with pagination and time range support. Gündüz fixed several issues [11]: he added JSON parsing preprocessing for array parameters that MCP sends as strings, coerced numeric parameters properly, fixed the aggregate_logs group_by sort to include a required type field, reimplemented get_log using the search endpoint (the single log GET endpoint does not exist), and removed the list_indexes tool which requires unscoped permissions.
The letta-mcp server [12] was released as read-only, and Gündüz removed the send-message tool [13] to keep it that way.
One email a day. Unsubscribe in one click.
A short briefing every day bgrgndzz ships something — in about 3 minutes.
One email a day. Unsubscribe in one click. Read a past issue →
References
- [1] Initial gong-mcp server bgrgndzz/gong-mcp
- [2] Use scoped npm package name @bgrgndzz/gong-mcp bgrgndzz/gong-mcp
- [3] feat: add find-calls-by-company tool for account-level call discovery bgrgndzz/gong-mcp
- [4] fix: coerce field.value to string before toLowerCase in company matching bgrgndzz/gong-mcp
- [5] 0.1.1 bgrgndzz/gong-mcp
- [6] 0.1.2 bgrgndzz/gong-mcp
- [7] 0.1.3 bgrgndzz/gong-mcp
- [8] Initial commit: Salesforce Query MCP server bgrgndzz/salesforce-query-mcp
- [9] Remove OAuth browser flow, use refresh token from env bgrgndzz/salesforce-query-mcp
- [10] Initial release: Datadog logs MCP server bgrgndzz/datadog-mcp
- [11] Fix aggregate_logs sort, get_log endpoint, and type coercion issues bgrgndzz/datadog-mcp
- [12] Initial commit: read-only Letta MCP server bgrgndzz/letta-mcp
- [13] Remove send-message tool to keep server read-only bgrgndzz/letta-mcp
