Included as a customer-success system whose tenant-hosted MCP can assemble account and portfolio context from Companies, Relationships, CTAs, Success Plans, Timeline, Scorecards, reports, and contacts, then create or update selected customer-success work under user and OAuth-app permissions.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Companies, Relationships, CTAs and CTA tasks, Success Plans, Timeline activities, Scorecards, reports visible to the user, portfolio data, end-user contacts, object metadata, templates, picklists, and activity-type configuration.
Generate detailed account summaries; query Company and Relationship data with filters, aggregation, sorting, and cross-object lookups; fetch CTAs, Success Plans, Timeline, CTA tasks, Scorecards, visible reports, portfolio data, contacts, and read-only configuration metadata.
Create or update CTAs, create tasks in CTAs, create or update Success Plans, and create or update Timeline activities at Company, Relationship, CTA, or Success Plan level. Delete, company-field updates, admin configuration, Scorecard writes, custom-schema changes, and Customer Goals are unsupported.
A Gainsight admin creates an OAuth application with PKCE, client credentials, callback URLs, and optional allowed-IP enforcement. Each end user authenticates with Gainsight credentials; effective access is the intersection of user data permissions and OAuth-app scopes, so a read-only app can block writes the user could perform in the UI.
Field-level permissions, bundles, and mandatory fields are enforced at the data layer, but UI-only locked layouts and filters do not apply. Gainsight cannot currently scope individual MCP tools within a read-write connection or natively restrict access to a pilot group; client distribution and OAuth-app scopes carry those controls.
Custom objects, deletes, user management, connector setup, Rules Engine changes, schema creation, C360 layout, Health Score configuration, notifications, Customer Goals, and Email Logs V2 are unsupported. MCP calls count against tenant API limits. Customer-facing audit is planned; entries cannot be identified as LLM-created. The current MCP action catalog supports creating one task in an existing CTA.
Agent access
Support: Official MCP server
Read scope: Read customer-success context and configuration metadata only where the authenticated user can see the same data in Gainsight, subject to OAuth-app scope. Include user-visible reports and the dedicated contact-search tool; keep Scorecards read-only.
Write scope: Allow CTA creation and updates, CTA task creation, Success Plan creation and updates, and supported Timeline creation and updates only when both user permissions and OAuth-app scope permit them. Do not enable deletes, company-field edits, admin/configuration changes, or Scorecard writes.
Authentication: User-level OAuth 2.0 with PKCE through a tenant-configured OAuth app, using client ID, client secret, exact callback URLs, and optional allowed IP ranges.
Approval boundary: Require client confirmation for every create or update, showing tenant, user, company or relationship, object type, record identifier, changed fields, and any cross-account breadth. Gainsight’s server does not own the confirmation step, and clients let users disable it; broad instructions such as closing all CTAs need explicit rejection or batch review.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Gainsight ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
CTA, Success Plan and Timeline writes are supported; the explicit limitations section states Tasks are queryable only and Task CRUD is unsupported.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
