Skip to content

Gladly MCP connector

The Gladly connector brings your customers, conversations, tasks, agents, teams, and inboxes into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can look up a customer, read a thread, or create a follow-up task inside their own Gladly access, with every call logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Gladly to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Gladly once

  1. Open Connections, choose Add connection, and pick Gladly.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Gladly API key. One person generates a token in Gladly and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

gladly
Gladly
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Gladly MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Gladly MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Gladly MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Gladly to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Gladly through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Catch up on a customer before replying

    Ask for a customer by name or email and get their Gladly profile plus every past conversation across email, chat, SMS, and voice in one view. No more scrolling through the timeline while the customer waits.

  • Support

    Turn a promise into a Gladly task

    When you tell a customer you will check on a refund or a reshipment, ask the agent to create the task in Gladly, assign it, and add a comment once it is done.

  • Customer experience

    Summarize a long conversation thread

    Pull every message and internal note from a Gladly conversation and get a short summary of what the customer asked, what was promised, and what is still open.

  • Support leadership

    See who is handling what today

    List Gladly agents, teams, and inboxes, then ask which tasks are open and who owns them, without opening a dozen tabs.

  • Quality

    Pull conversations for coaching reviews

    Fetch the recent conversations handled by a specific Gladly agent and review tone, accuracy, and follow-through before a one-to-one.

  • Operations

    Correct customer records after checkout errors

    Find the Gladly customer whose email or phone was entered wrong, update the details, or create a new customer record from an order that never matched.

Try asking

  • “Summarize open Gladly tasks assigned to the support team.”
  • “Which Gladly agents closed the most tasks last week?”
  • “Show recent comments on Gladly tasks for this customer.”

See all 64 Gladly tools below

Compare

Elaichi vs Zapier MCP vs Composio for Gladly

All three can connect Gladly to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Gladly, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Gladly tools Allow or restrict single Gladly tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Gladly call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Gladly tools for your AI agents

64 tools are ready to call through Elaichi's MCP endpoint the moment you connect Gladly, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Gladly gets you

6 screens from the product, each doing one job for your Gladly account.

The agent

Ask about Gladly customers, get real answers.

Plain language questions run against live Gladly customers, tasks and agents.

  • customers
  • tasks
  • agents
  • task comments

Ask Elaichi to work across your apps.

Summarize open Gladly tasks assigned to the support team.

Which Gladly agents closed the most tasks last week?

Show recent comments on Gladly tasks for this customer.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Gladly.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

64 Gladly tools ready without custom code.

Browse Gladly agents, customers, tasks and comments with methods already wired.

  • List all Gladly agents
  • Get single Gladly agent by ID
  • List all Gladly customers
  • Get single Gladly customer by ID
ElaichiTools
Tool Action Description
List all Gladly agents List List agents in Gladly. Returns an array of agents with fields id (agent identifier), name (agent's full name), and emailAddress (agent's login email).
Get single Gladly agent by ID Get Get an agent profile by id in Gladly. Returns id, name, and emailAddress of the agent.
List all Gladly customers List Get customers by phoneNumber in Gladly. Returns up to 50 profiles sorted by most recent updatedAt. Response includes customerProfiles with key customer details.
Get single Gladly customer by ID Get Get customer by id in Gladly. Returns customer details including id. If the customer has been merged, an error with the new id is returned.
Create a Gladly customer Create Create a new customer profile in Gladly with supplied profile data including name, emails, phones, and address. Returns the unique id and profile details of the created customer.

Toolboxes

Every team gets its own Gladly toolbox.

Toolboxes scope Gladly tools to Support, Success, Quality and Operations separately.

  • Support
  • Customer success
  • Quality
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Gladly · customers and conversations

Gladly starter 18 Mar 4, 2026

Customer success toolbox

Gladly · customer profiles and follow ups

— 9 Mar 2, 2026

Quality toolbox

Gladly · agents and task comments

— 24 Feb 27, 2026

Operations toolbox

Gladly · task queues and routing

Gladly starter 6 Feb 19, 2026

Onboarding toolbox

Gladly · new customer records

— 31 Jan 30, 2026

Analytics toolbox

Gladly · task and agent reporting

— 12 Jan 22, 2026

Shared connections

Teammates use Gladly without seeing a credential.

Each Gladly connection shows who connected it and which teams and members share it.

  • Support EMEA
  • Support US
  • Customer success
  • Quality assurance
ElaichiConnections
Connection Scope Status Access
GL

Gladly (Support EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GL

Gladly (Support US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GL

Gladly (Customer success)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GL

Gladly (Quality assurance)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GL

Gladly (Operations)

Connected by Ryan Hayes

Personal • Active Not shared
GL

Gladly (VIP desk)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Gladly customer.

Append-only log records when, who, what happened, type and Gladly resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Gladly Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Gladly Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Gladly Customers List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Gladly task digest.

Six steps fetch and group Gladly tasks, draft a digest, await approval, post back.

Gladly digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    Gladly

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Gladly

    Queued

Collections and dashboards

Gladly numbers arrive before anyone asks.

Four metrics, 14 days of Gladly customers created, split by team, refreshed on schedule.

Gladly health

Refreshed 4 minutes ago · every 15 minutes · from the customers collection

Live

Customers

1,284 ↓ 12%

Tasks

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support US 27%

Customer success 21%

Quality assurance 18%

FAQ

Frequently asked questions

How do I connect Gladly to Claude?

Connecting Gladly to Claude takes two steps. First, connect Gladly in Elaichi by pasting a Gladly API key, which you copy from the API tokens area of your Gladly settings; there is no client ID or secret to generate and no OAuth application to register. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Gladly is ready to use.

Does Gladly work with ChatGPT and Cursor as well as Claude?

Yes. Once Gladly is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Gladly once and every client you use picks it up.

What can an AI agent actually do with my Gladly data?

With Gladly connected, an AI agent can look up a customer and read their full conversation history, pull the messages and internal notes from a single conversation, and summarize what happened. It can create and update Gladly customers, create and update tasks, add comments to tasks, and list your agents, teams, and inboxes. Because Gladly exposes a lot of actions, short concrete asks such as "find the customer with this email" work better than one long paragraph.

Does connecting Gladly give the AI access to every customer and conversation?

No. The AI acts inside the access of the person who signed in, so it sees the Gladly customers, conversations, and inboxes that person can already see. Elaichi can narrow that further, for example read-only on customers, but it can never widen what Gladly itself allows for that person.

Can my team share one Gladly connection?

Yes. One person connects Gladly in Elaichi and shares the connection with a team, and nobody else ever handles the Gladly API key. Each teammate still signs in to Elaichi as themselves, so every action against Gladly is logged under their own name, not the name of whoever connected it.

Can I stop an agent from deleting or changing things in Gladly?

Yes. Restrictions in Elaichi work per action, so you can block deleting Gladly customers or updating tasks while leaving reading and summarizing available. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Gladly connection when someone leaves?

When you offboard someone in Elaichi, their access to Gladly through every AI client ends at once. If they were using a shared Gladly connection, it keeps working for everyone else on the team. If you disconnect Gladly in Elaichi altogether, it disappears from Claude, ChatGPT, Cursor, and every other client in one step.

Does the Gladly MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Gladly is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Gladly?

Yes. Both let Claude, ChatGPT or Cursor use Gladly. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Gladly call.

How is Elaichi different from Composio for Gladly?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Gladly: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Gladly in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.