The Gainsight CS MCP Server should support querying and writing to Custom Objects (both High Volume and Low Volume). Custom Objects are currently excluded from MCP entirely -- they cannot be read, queried, or written to through any MCP tool. This is a significant gap for organizations that rely on Custom Objects to extend the Gainsight data model beyond standard objects.
Current Behavior
As documented in the MCP FAQ, the MCP server currently does not support querying custom objects. The supported scope is limited to standard objects: Company, Relationship, CTA, Success Plan, Timeline Activity, Scorecard, and their associated metadata/picklist configurations. Any prompt that targets a Custom Object returns no results or errors, with no workaround available through MCP.
Requested Behavior
Extend the MCP server to support Custom Objects with the following capabilities:
- Read/Query: Allow MCP to query Custom Objects using the same filtering, aggregation, and sorting capabilities available for standard MDA objects today. This includes cross-object lookups where a Custom Object is related to Company or Relationship via GSID.
- Write (Create/Update): Allow MCP to create and update records on Custom Objects, respecting the same field-level permissions, mandatory field enforcement, and OAuth scope (Read vs Read/Write) that apply to standard object writes today.
- Schema Discovery: Expose Custom Object field schemas and picklist values through the existing
get_object_metadataandget_picklist_valuesMCP tools, so LLMs can understand the object structure before querying or writing.