--- title: "What is the Gladly MCP for Claude?" slug: "what-is-the-gladly-mcp-for-claude" updated: 2026-11-18T19:38:15Z published: 2026-11-18T19:38:15Z canonical: "help.gladly.com/what-is-the-gladly-mcp-for-claude" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.gladly.com/llms.txt > Use this file to discover all available pages before exploring further. # What is the Gladly MCP for Claude? The Gladly MCP for Claude connects Claude to your Gladly organization. Once connected, you can use plain English in Claude to investigate AI sessions, spot patterns, improve Guides and Workflows, and test your changes before customers see them. To connect Claude, see [Set up the Gladly MCP for Claude](https://help.gladly.com/docs/set-up-the-gladly-mcp-for-claude). ![](https://cdn.us.document360.io/7047b671-c4f2-4df0-bb0a-b9b511fd2452/Images/Documentation/image(398).png?sv=2026-02-06&spr=https&st=2026-11-19T06%3A10%3A43Z&se=2026-11-19T07%3A10%3A43Z&sr=b&sp=r&sig=XHUjwQGtRdmH5fN19gLs0IBNcdpEdZgB1ohVHbLP6gY%3D) > [!CAUTION] > Not the same as MCP connections > > The Gladly MCP for Claude lets Claude work in your Gladly organization. [MCP connections](https://help.gladly.com/docs/what-are-mcp-connections) do the opposite: they let Gladly AI call tools on your own servers during Customer conversations. The two features are separate and don't depend on each other. ## How the Gladly MCP for Claude works The Gladly MCP for Claude has two parts that you add to Claude: a plugin and a connector. The plugin adds a setup command that helps you connect. The connector gives Claude secure access to your Gladly organization and the knowledge it needs to work with Gladly AI, including Gladly Agents, Guides, Workflows, Actions, Knowledge, and the Simulator. When you ask a question or make a request, Claude plans the work, reads what it needs from Gladly, and saves changes using your Gladly permissions. For example, you can ask, "Why are returns sessions being handed off?" Claude opens the sessions, reviews each step, and explains what happened. Claude showing a visual report of Gladly AI sessions. **Claude acts as you** Claude signs in with your own Gladly account and has the same permissions you do. Changes that Claude saves appear in Gladly as if you made them yourself. They also appear in the Changelog under your name, tagged "(MCP)." ![](https://cdn.us.document360.io/7047b671-c4f2-4df0-bb0a-b9b511fd2452/Images/Documentation/gladly ai mcp claude.png?sv=2026-02-06&spr=https&st=2026-11-19T06%3A10%3A43Z&se=2026-11-19T07%3A10%3A43Z&sr=b&sp=r&sig=3JDRXqnKd0HzNwGOq77Ics%2Fu1OjQt0clpL0K994HEtA%3D) ## What you can do Claude helps you through the whole improvement loop: investigate a problem, estimate its impact, plan a fix, make the change, test it, and share what changed. You don't need to be technical. Start with a problem, and Claude suggests the next step and Gladly best practices along the way. - **Investigate:** Find out what went wrong in one session or across a group of sessions. - **Analyze:** Spot patterns across sessions, including which Workflows and steps ran, handoff and resolution rates, and results from Signals. - **Improve:** Test changes to a Guide or Workflow before they go live. - **Build:** Set up new Guides and Workflows from a description or a document, such as a policy or SOP. - **Understand Actions:** Ask what a custom Action does, see its recent runs, and update it safely. - **Test at scale:** Create Simulator Scenarios in plain English. See [Use the Gladly MCP for Claude](https://help.gladly.com/docs/use-the-gladly-mcp-for-claude) for example prompts. ## Requirements To connect Claude to Gladly, you need all of the following: - **Your organization is in the beta.** Gladly has enabled MCP access for your organization. - **You have an eligible role.** You're a Team Manager, Compliance Admin, or Admin in Gladly, or you have a custom role with the Manage Gladly AI, View Gladly AI, or Review Gladly AI permission. Other roles can't connect. - **You use a supported version of Claude.** You use Claude Desktop or [claude.ai](http://claude.ai) on a paid plan. **MCP is on for your whole organization** MCP access is turned on for your organization as a whole, not person by person. You can't allow or block one specific person. Claude gets the same access as the person who connects, so only give eligible roles to people you trust with customer data and your AI setup. For details, see [Review security and data for the Gladly MCP for Claude](/product-docs/docs/review-security-and-data-for-the-gladly-mcp-for-claude). > [!WARNING] > **Beta access is all or nothing** > > During the closed beta, MCP access is on or off for the whole organization. Anyone who can connect can both read and save changes, so only give the eligible roles to people you trust to edit your AI setup. *Customer* or C*ustomers* refers to the people you support through Gladly who buy or use your products or services.