SoftTech AI Registry
Gainsight · Gainsight CS MCP Server

MCP write tools

The documented write tools that the Gainsight CS MCP Server exposes to external MCP-compatible AI clients. The external AI client performs the reasoning and chooses and invokes the tool; the Gainsight CS MCP Server exposes and executes the corresponding Gainsight operation. The server is not itself the reasoning agent. Four write tools are established: Create Timeline Activity, Manage Cockpit Actions, Manage Success Plan Actions and Update Timeline Activity.

Recorded characteristics

Function
External MCP-compatible AI clients connected to the Gainsight CS MCP Server can invoke four documented write tools, alongside Core and Read-only tools that are supporting context only. (1) Create Timeline Activity: logs Timeline activities such as calls, meetings, updates, emails or milestones; logging an email activity records it in Gainsight and does not send an email. (2) Manage Cockpit Actions: creates and updates CTAs and associated tasks where supported. (3) Manage Success Plan Actions: creates and updates Success Plans, objectives, owners and due dates where supported. (4) Update Timeline Activity: edits an existing Timeline activity. Update Timeline Activity appears in the current Overview of AI Tools inventory but is omitted from the separate AI Tool Management admin list; this tension is unresolved. Not supported or not claimed: deleting records or objects, company field updates, admin configuration changes, scorecard writes, sending email, arbitrary external-system writes and unlimited bulk operations. The external AI client does the reasoning; Gainsight documents no separate AI model within the server.
Data access
Read and write access is limited to Gainsight CS objects enabled by the admin and to data the authenticated user is permitted to see, with field-level security enforced. Six Core tools and Read-only tools retrieve Gainsight CS data for the client. No access outside Gainsight CS is attributed.
Actions
Can take actions
External actions
No
Human confirmation
Not established
Permission basis
User permissions
Administrative control
Under Administration > AI Settings, admins manage Core Tools, Read-only Tools and Write Tools and the accessible objects. Tools and objects can be switched on or off; the six Core Tools are locked on, and the Company, User, Relationship and DA Picklist objects are locked. Objects are switched in bulk; turning a tool on turns on the objects it depends on. Users must reconnect after tool changes. Settings apply across Gainsight Copilot, the Slack agent and external MCP clients; no pilot-group setting is documented. Human confirmation is recorded as not_established: Gainsight states the confirmation step is a feature of the LLM client, not the MCP server. ChatGPT and Claude can show a confirmation before writes, users can disable it in client settings, and Gainsight recommends requiring approval for write actions, but the server enforces no per-action confirmation and behaviour is not established for every client. OAuth authentication, connector authorisation, admin tool or object activation and client setup are not treated as per-action confirmation. Bulk: Gainsight warns that a user could issue an instruction such as "close all CTAs" through a connected client, establishing potential multi-record action from one instruction within the user's authority; elsewhere bulk batch operations are described as unsupported while bulk Timeline activity operations are discussed. This is not recorded as unlimited autonomous bulk execution, and the contradiction is unresolved. Audit: tool calls and some LLM question and tool-call information are logged internally; admins can identify users who authorised the OAuth application; LLM-created records may not be distinguishable from other API or automation records. Documentation describes customer-facing audit visibility as planned while also referencing a CS MCP Logs object that tracks AI tool calls; unresolved.
Default state
Conditional
Availability
Default is conditional. Before MCP configuration the capability is unavailable. Configuration requires administrative OAuth application setup, MCP client configuration and individual user authentication. Within a configured environment Gainsight states all tools and objects are active by default. Client-side requirements documented include ChatGPT Developer Mode, Claude team or enterprise plans, and a Copilot Studio agent for Microsoft Copilot. Lifecycle context: CS MCP documentation appeared with the Q1 / April 2026 release period; unlike other Gainsight MCP servers it is not labelled Beta; June 2026 release notes include "GA-ready, not enabled by default" context; an official Claude directory connector was not established as live. No GA date is recorded.
Licensing
Users with a Gainsight sign-in licence (Full, Viewer + Analytics, Viewer) can use the MCP server once an admin has configured it. No separate pricing is established.
External model or provider
None recorded. The Gainsight CS MCP Server is model- and client-agnostic; documented clients include ChatGPT, Claude, Microsoft Copilot Studio and Sigma. These are clients, not the capability's model provider; no OpenAI, Anthropic or Microsoft attribution.
Limitations and uncertainty
External action is recorded as no, evaluated relative to the recorded product boundary: the established write tools persistently change Gainsight CS state (CTAs, tasks, Success Plans, objectives, Timeline activities) and no first-party evidence establishes persistent change outside the Gainsight product estate; the action is external to the calling AI client but internal to Gainsight. Permission basis is user_permissions: each user authenticates individually with their own Gainsight credentials using PKCE, the MCP server respects user-level data permissions with field-level security, and effective access is the intersection of user/application authority and OAuth constraints. Limitation: Super Admins may retain write capability even when the OAuth application is configured read-only; execution identity remains the authenticated user, so this is not recorded as mixed. Unresolved: OAuth 2.0 (FAQ) versus OAuth 2.1 (setup guide) wording; Update Timeline Activity missing from the admin tool list; conflicting bulk-operation statements; conflicting audit/log visibility statements; explicit GA status and date; confirmation behaviour in Copilot Studio and other clients; evolution of the client-side confirmation model. Excluded: Gainsight Copilot, Gainsight AI Agent in Slack, Agent Studio, Staircase AI MCP, PX, CC and Skilljar MCP servers, Admin CLI.

Evidence