Skip to main content

Set Up Gainsight CC MCP (BETA)

  • May 27, 2026
  • 12 replies
  • 692 views

mdfahd
Forum|alt.badge.img
  • Gainsight Employee ⭐️⭐️

This article helps Admins and Community Managers set up and configure Gainsight Community MCP in Claude.

Overview

 

Gainsight Community MCP is a connector that lets you interact with your community data through AI assistants such as Claude. Model Context Protocol (MCP) is a standardized way for AI assistants to connect to external tools and data sources. Once connected, you can ask questions in natural language and get answers drawn directly from your community.

Setting up the Gainsight Community MCP involves two parts:

  • Admin Setup: An admin enables Community MCP for the community from Control. This is a one-time configuration step.
  • User Connection: Each user connects from their AI client, such as Claude, using their community credentials. The tools available to each user depend on their community role and permissions.

The scope of tools available depends on your community role. When you connect, the connector authenticates you against your community and displays only the tools that match your role. The tools are organized across three areas:

  • Search Tools: Find community content such as posts, topics, and discussions.
  • Analytics Tools: Query community performance metrics and dashboard KPIs.
  • Admin Tools (Read-only): Review community state such as moderation queues, recognition data, user information, community structure, and idea workflows.

The AI assistant selects the appropriate tools based on the prompts. Since the available tools depend on the community role assigned to each user, reviewing tool access helps determine what types of questions to ask and what data to expect.

  • Search to find content
  • Analytics to understand trends
  • Admin to see what needs your attention.

Prerequisites

Before you begin, ensure the following requirements are met:

  • You must have an Admin, Community Manager, or a Moderator role in your Gainsight Customer Community to enable the Community MCP server in Control.
  • The community must have at least one authentication method configured (SAML, OIDC, OAuth2, Google SSO, or local username and password).
  • Users who will connect must have an active account in the community with a valid role assignment.
  • Users must have access to an AI client that supports MCP connectors, such as Claude.
  • If your organization restricts outbound network traffic, ensure that your AI client can reach the Gainsight Community MCP server at https://mcp.insided.com/mcp. Refer to your AI client's documentation for the current IP range list.

Limitations

 

The following limitations apply to the Gainsight Community MCP:

  • Admin tools are read-only. You cannot modify community data through the MCP connector.
  • After you turn on or turn off the Community MCP toggle, it may take some time for the change to take effect.
  • You can connect only one community at a time.

Enable MCP in Customer Community

 

Admins must turn on the Community MCP Server toggle in Control before users can connect from their AI clients. This is a one-time setup step.

To enable Community MCP:

  1. Log in to Control.
  2. Navigate to AI > AI Settings. The AI Settings page appears.
  3. Scroll down to Features and turn on the Community MCP toggle.
     

    Note: After you turn on the toggle, it may take some time for the change to take effect.

Configure Gainsight Community MCP in Claude

 

Once Community MCP is enabled in control, admins need to set up the configuration in AI Assistant.

The connector uses dynamic client registration with PKCE, so no OAuth client credentials, authorization URLs, or callback allowlists are required at any point.

The following steps describe the connection flow using Claude as an example.

To configure Gainsight Community MCP in Claude:

  1. Log in to Claude.
  2. Navigate to Customize > Connectors. The Connectors page appears.
  3. Click the Plus icon.
  4. Select Add Custom Connector. The Add Custom Connector dialog appears.
     
  5. In the Name textfield, enter the name to identify the connector. For example Gainsight Community MCP.
  6. In the Remote MCP URL textfield, enter the MCP URL https://mcp.insided.com/mcp

     

    Note: No OAuth client credentials are required.

  7. Click Add. The MCP connector is now added in Claude.
     
  8. Click Connect. The Select Your Community page appears.
  9. In the Community URL textfield, enter your valid community URL. For example, if your community URL is https://community.acme.com, enter community.acme.com
     

  10. Click Continue. The community Login page appears.
     
  11. Enter the following details:
    • Username: Enter a valid user name.
    • Password: Enter your community password.
  12. Click LOG IN. The Authorize Application dialog appears.
  13. Click Approve. The Login is successful.

The permissions displayed depend on your role in the community.

The following table describes the permissions displayed for each role level:

Role

Permissions Displayed

All users

View your profile information, Search community content, View your email address

Admins and Community Managers

All user permissions, plus: View community analytics

Admins

All user permissions, plus: View community analytics, Manage community settings

Moderators

All user permissions, Manage Community settings

 

You are redirected back to Claude. The connector now shows as connected with a list of available tools based on your role.
 

 

Tools Available in Gainsight Community MCP

 

The Gainsight Community MCP provides a set of tools organized across three areas:

  • Admin
  • Search
  • Analytics

The tools available to you depend on your community role and the scopes granted during the connection flow.

The following table summarizes the scopes and tools available for each role: 

Role

Scopes Granted

Tools Visible

Admins

mcp:search, mcp:analytics, mcp:admin

All search, analytics, and admin tools

Community Manager

mcp:search, mcp:analytics, mcp:admin

All search, analytics, and admin tools

Moderator

mcp:search, mcp:admin

Search and admin tools

Registered user, Super-user

mcp:search

Search tools only

 

Admin Tool

The Admin Tool gives community admins a conversational way to review community state. It includes four read-only tools that surface information without modifying any community data.

The following table describes each Admin tool and the types of queries it supports:

 

Tool

What You Can Ask

Moderation Overview

Surface the moderation queue state, including trashed content and content with moderation labels.

Recognition Overview

Read leaderboards (all-time and weekly), available badges, an individual user's leaderboard position, and points history.

User Overview

Look up users by ID or field (email, username) and view their current role assignments.

Community Structure

Navigate the category tree, view content per category, and check visible topic counts.

 

The following scenario demonstrates how the Admin tools work together in a single conversation:

  • Prompt: What needs my attention today, and who should I celebrate this week?

    Result: The Moderation Overview surfaces content that has been trashed and content with active moderation labels, and the Recognition Overview returns this week's top point earners so you can recognize them publicly. 

Search Tool

The Search Tool allows you to query community posts, topics, and indexed content through the MCP connector. The AI assistant retrieves this data and uses its own capabilities to generate insights such as sentiment analysis across discussions, activity dashboards, member engagement breakdowns, and classification of search results by type.

Example prompts:

  • What were the most discussed topics this month?
  • Run a sentiment analysis on posts from the last 30 days.
  • Classify recent search results by type (questions, complaints, feature requests).
  • What were the most recent topics in the community?

Analytics Tool

The Analytics Tool allows admins and Community Managers to query community analytics data conversationally through the AI assistant. Previously, reviewing community KPIs required navigating to individual dashboards and manually comparing metrics across time periods.

The following table describes the insight areas available through the Analytics Tool:

 

Insight Area

What You Can Learn

Community Health

Overall community performance with period-over-period comparison across users, content, traffic, Q&A, and gamification.

User Insights

Individual user profiles and activity details.

User Trends

Registration trends, leaderboards, role breakdowns, active and churned user lists, and subscription activity.

Content Performance

Topic and reply analytics, Q&A metrics, response times, helpfulness ratings, and content gaps such as unanswered questions.

Audience Traffic

Pageview trends, visitor segments (contributors, reactors, viewers), and breakdowns by section or content type.

Product Ideas

Idea pipeline status, top-voted ideas, and delivered ideas.

 

Example prompts:

  • How is the community performing this quarter compared to last quarter?
  • How many new users joined in the last 30 days?
  • Which categories have the most unanswered questions?
  • Who are the top contributors this month?

Note: The AI assistant retrieves data that matches the KPIs visible in your community dashboards. The accuracy of the results depends on the quality and completeness of the data in your community.

12 replies

Nishers
Forum|alt.badge.img+3
  • Contributor ⭐️⭐️
  • May 27, 2026

This is EPIC! I am so glad GainsightCC is keeping up! So I’ve gone ahead and togged MCP on however I don’t see a place to add a custom connector in my Claude instance!  Your directory screenshot might be outdated! Can I get help here?

 


  • Gainsight Employee ⭐️
  • May 28, 2026

Hi ​@Nishers 
 

The custom connector option isn't in the Directory page - that only shows officially listed connectors. You'll need to add it as a custom connector.

 

If you're on a Team or Enterprise plan, reach out to your IT/operations team and ask them to add this custom connector URL: https://mcp.insided.com/mcp - once they add it at the org level, it'll be visible for you to connect.

 

Here's the full step-by-step setup guide with screenshots: https://communities.gainsight.com/integrations-54/set-up-gainsight-cc-mcp-beta-31009#Configure+Gainsight+Community+MCP+in+Claude

 

You'll then log in with your existing community credentials - no separate account needed.

 

We're also in the process of submitting for the official Connectors Directory - so soon you'll be able to find and connect it directly from that Directory page. Stay tuned!


aluciani
Forum|alt.badge.img
  • Helper ⭐️
  • May 30, 2026

This sounds interesting, is Google Gemini an option here as well? 

Wonder as well if it would make sense to add Glean as possible source. 


  • Gainsight Employee ⭐️
  • May 30, 2026

Hi ​​​​@aluciani 

Google Gemini - Yes, Gemini is fully supported. Our MCP server follows the standard MCP specification with OAuth 2.1 authentication and streamable-http transport, so any MCP-compliant client can connect.

 

Glean - Yes, Glean supports connecting to remote MCP servers via streaming HTTP and OAuth with PKCE, which is compatible with our MCP server.

However, for Glean (and any MCP client other than Claude, ChatGPT, Microsoft Copilot Studio, and Gemini), the first connection attempt will fail. For security reasons, we maintain a fixed allowlist of redirect URIs for OAuth authentication.

When a new MCP client tries to connect, its redirect URI won't be in our allowlist yet, so the OAuth flow will be rejected. We log that redirect URI on our side, add it to our supported list, and once that's done, subsequent connections from that client will work.

 

So if you're connecting via Glean or any other MCP client not yet in our supported list - expect the first attempt to fail, and reach out to us so we can get it enabled for you.


sarahmasterton-brown
Forum|alt.badge.img+4

Thanks ​@mdfahd and the GS team for delivering on this - it’s transformational! 
Does the MCP index all modules of the community: Ideation, Knowledge Base etc?


  • Contributor ⭐️
  • June 2, 2026

First off, really excited to see the MCP connector for CC, we've already started testing it internally and the use cases for our team are very clear!

One thing we'd love to see on the roadmap: more granular MCP permission scoping, separate from platform roles.

Right now, the analytics and admin tools are only available to community admins and managers. That makes sense for the platform itself, but it creates a gap for our use case. We want our CSMs to be able to generate customer-specific insights through Claude (things like account activity, engagement trends, top contributors) without giving them full admin access to the community platform. Making someone an admin just to access MCP analytics isn't feasible at scale, and it would introduce access risks we'd rather avoid.

The ideal would be an MCP-specific permission tier or a way to grant access to specific tool categories (e.g. analytics read-only) without elevating someone's role on the platform itself.

Is this something on the roadmap, or is there a workaround we might be missing? This feature is very meaningful to us, so hopefully it's something the team can consider for a future release 🤠


mdfahd
Forum|alt.badge.img
  • Author
  • Gainsight Employee ⭐️⭐️
  • June 4, 2026

Thank you ​@sarahmasterton-brown 
Tagging PM and EMs for addressing your query
FYI ​@Aleksandra 


mdfahd
Forum|alt.badge.img
  • Author
  • Gainsight Employee ⭐️⭐️
  • June 4, 2026

Thank you ​@ndebban for your query.
Tagging PMs for more information
FYI ​@Graeme Rycyk ​@Larry ​@Aleksandra 


  • Gainsight Employee ⭐️
  • June 4, 2026

Hi ​@sarahmasterton-brown,

 

“does the MCP index all modules of the community: Ideation, Knowledge Base etc?” → Yes.. all modules of community


  • Gainsight Employee ⭐️
  • June 5, 2026

Hi ​@ndebban 

Thanks for the feedback - this is something we're actively discussing internally. The direction we're leaning towards is scoping MCP permissions at both platform roles and custom role level, so admins can configure which MCP capabilities (search, analytics, admin) each role gets access to. Will keep this thread updated as we make progress.


Jean Walters
  • Contributor ⭐️
  • June 8, 2026

I configured the Gainsight Community MCP in Claude this morning with great success! I have set up a scheduled sync so that product ideas from community create and update ideas in Jira Product Discovery daily (for now). I was able to include vote count from Gainsight CC by setting up a custom number field in JPD, and I’m working on ARR as well (we are still working to set up the Salesforce integration to Gainsight CC).

One limitation I ran into. Though the MCP can tell me how many comments there are on a product idea post, it doesn’t give me the content of the comment/reply. It would be extremely helpful to have something like “get topic replies” so that I can continue to add context for our PM team.

Next, I’ll be working to sync idea statuses between the two systems. Curious if anyone else has done that yet.


abhishekh_singh
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • June 9, 2026

Hi ​@Jean Walters, thanks for sharing this, like the workflow you've built with JPD sync and vote counts!

You're right, today the MCP search tools can match on reply content (replies are individually indexed), but results are returned at the topic level - title, excerpt, metadata, and reply count. There's no tool yet to retrieve the full list of replies for a specific topic, which is what you'd need for your JPD workflow.

The good news is this is something we're actively looking into. A tool like "get topic replies" that returns the actual comment/reply content for a given topic or idea is a natural next step and aligns well with workflows like yours where the full discussion context matters.

We've noted this as a feature request. No ETA to share yet, but it's on our radar and your use case is a great example of why it's needed.

On the idea status sync between CC and JPD - that's an interesting one. Would love to hear how you approach it. If you run into anything else, keep the feedback coming. 
It's really helpful as we shape the MCP roadmap.