Skip to main content
mobrien14
Helper ⭐️
May 28, 2026
New Idea

Admin Reporting on MCP Usage/Changes

Related products:CS Data Management & IntegrationsCS Authentication & User Management
  • May 28, 2026
  • 7 replies
  • 223 views

Did some digging through the Community and didn't find an existing idea for this — posting now given the Pulse announcements, especially Agent Studio and the MCP-adjacent functionality there.

We've been live with the Gainsight MCP for about a month with our CSMs on full read-write access. While we’ve managed to avoid major incidents, there have been moments of confusion and I’m finding two major product gaps that need to be resolved:

  • The first is visibility into the source of a created/update asset. Right now, we can't filter by how they were generated. If someone were to bulk-create a bunch of CTAs or logs Timeline entries on an incorrect company, I can’t proactively intervene when this is identified on our internal administration dashboard.
    • As Gainsight continues to expand support objects (such as adding write access to company records), this is going to become even more critical.
  • The second relates to field history tracking -- when something gets updated via MCP, there's no record of what it looked like before. If a CSM’s incorrectly created skill closes every open CTA in their book of business, I can't quickly assist by adjusting them to their former status: that history is just gone.

In an ideal world, system admins should be able to easily do the following without resorting to ad-hoc tools or going to Gainsight’s data operations team:

  • Identify records that were created or modified via MCP
  • See the prior field value for any record modified by the MCP (or, ideally, any record change in their instance)
  • Let us configure which objects & fields support write-to functionality through the MCP, as opposed to a blanket “All users with write access can do all of the supported objects”

These new AI tools definitely have their benefits to improve end user functionality, and I get the desire to move fast. But us as admins need to have these tools to support our instance at launch, not months (or years) down the line.

7 replies

brlayman2583
Helper ⭐️
May 28, 2026

Both of these need to be critical updates asap! 

Contributor ⭐️⭐️⭐️
May 29, 2026

Couldn’t agree more with this. There’s no way to securely give write access to end users until we have this kind of solution, especially the per-field/object permissions. Blanket access and no real ability to audit is a crisis waiting to happen. 

spencer_engel
Expert ⭐️
May 29, 2026

As I’ve said for years, all major features should be released with admin-level reporting ready at launch like ​@mobrien14 said. Especially now with AI.

mattmarcsmith
Helper ⭐️
June 3, 2026

Really glad someone raised this - we've been hitting exactly the same issues since going live with the Gainsight MCP. I wanted to add some technical detail from hands-on testing that hopefully strengthens the case.

On the Source field gap

We've confirmed via the MCP's get_object_metadata tool that all three writable objects - Activity Timeline (activity_timeline), CTA (call_to_action), and Success Plan (cta_group) - have a Source field. However, when we queried our Activity Timeline for entries created via the MCP, every single one came back with Source = "C360" - identical to activities created manually through the UI. There is currently no way to distinguish them.

We also confirmed that the Activity Timeline object (and CTA/ Success Plan) are System object types in Gainsight, meaning custom fields cannot be added. So there is no viable workaround available to Admins - no tagging, no custom flag field, nothing. The only option would be embedding a marker string in a notes or content field, which is fragile and dependent on end users not editing it out.

This makes the first point (visibility into the source of a created/ updated asset) more urgent than it might appear. It's not just a nice-to-have reporting feature; it's currently completely unresolvable at the Admin level without a platform change.

On field history tracking

We haven't tested this directly yet, but your second point about no record of prior field values after an MCP update is a significant concern for us too, particularly given that bulk updates via spreadsheet are a realistic use case. If a CSM uploads an incorrect file and bulk-updates 20 timeline entries, there's currently no way to see what any of those fields contained before. I think there’s a separate Idea about auditing fields so maybe this can be included in the scope for that?

What we'd like to see

In addition to the above three asks, we'd add:

  • A distinct Source value written by the platform automatically when any record is created or modified via MCP - something like MCP or Gainsight MCP - applied consistently across all writable objects, not just Timeline.
  • This should require zero configuration from Admins; it should be automatic.

Upvoting and hoping this gets traction ahead of further MCP object expansion! 😁

dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
June 8, 2026

[A]ll major features should be released with admin-level reporting ready at launch.

👆 This right here.

We shouldn’t have to ask for reporting after launch. We need to just be able to build the report when we enable the feature.

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
Jef Vanlaer
Helper ⭐️⭐️⭐️
June 17, 2026

On the Source field gap

We've confirmed via the MCP's get_object_metadata tool that all three writable objects - Activity Timeline (activity_timeline), CTA (call_to_action), and Success Plan (cta_group) - have a Source field. However, when we queried our Activity Timeline for entries created via the MCP, every single one came back with Source = "C360" - identical to activities created manually through the UI. There is currently no way to distinguish them.

Noticed the same behavior on the Copilot Beta and flagged it with ​@Ritika Jindal today. ​@Ritika Jindal Looks like this is something to pick up in the MCP as well.

Ritika Jindal
Gainsight Employee ⭐️⭐️
August 13, 2026

As part of Q2 release , we have already made sources available for timeline activities created via GS MCP or GS Copilot.
 

  • CS_COPILOT_MCP_C360 → activities created by Copilot via the C360 page → UI Tag(in timeline) Copilot
  • CS_COPILOT_MCP_R360 → activities created by Copilot via the R360 page → UI Tag Copilot
  • CS_COPILOT_MCP_SLACK → activities created by Copilot via the slack app → UI Tag Copilot
  • CS_COPILOT_MCP → activities created by Copilot main page → UI Tag Copilot
  • CS_MCP → activities created by external MCP clients (Claude, ChatGPT, MS Copilot Studio, etc.) → UI Tag CS MCP


also ,we are working on making source available for CTA/SP/task as well which are created/updated via GS MCP or GS copilot. Planned by or before Q3
Additionally we are trying to make MCP or Copilot logs available via an object where you can see who queried, what tools were called, when, source (Copilot fromm C360/R360/GS MCP etc) and prompt used. Planned by or before Q3