Totango MCP connector
Connect Totango to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can search accounts, check usage and health, and update records, with every call running as the signed-in person and logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which accounts renewing this quarter have dropped in usage?
Working in Totango with Elaichi
-
Totango accounts search
-
Totango accounts get plan summary
-
Totango collections search
How to connect Totango to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Totango MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Totango MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Totango MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Totango MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Totango MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Totango to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Totango through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Totango is logged.
-
Customer Success
Catch the account up after a call
Finish a customer call and tell the agent what changed. It updates the account's attributes in Totango so the health picture reflects what you just heard.
-
Customer Success
Find accounts at risk before renewal
Ask which accounts renewing this quarter have slipped in usage or status. The agent searches Totango accounts and pulls each plan summary so you can prioritize outreach.
-
Account Management
See what a customer actually uses
Before a business review, ask for the recent events and usage on an account. You walk in knowing which features they lean on and which they have stopped touching.
-
Support
Know who you are talking to
Look up the person who opened the ticket and the Totango account they belong to. The agent shows their plan, their status and recent activity without leaving the conversation.
-
Revenue Operations
Keep account fields and collections clean
Ask the agent to correct segment, owner or tier attributes across a set of accounts, or to tidy a collection. Routine cleanup stops waiting for someone with time to click through.
-
IT
Manage who has a Totango seat
Add a new hire as a Totango user through SCIM, move them into the right group, and check the audit log when someone asks who changed what.
Try asking
- “Which accounts renewing this quarter have dropped in usage?”
- “Summarize recent events for the Acme Corp account.”
- “Update the health notes on Globex after today's call.”
What connecting Totango gets you
6 screens from Elaichi, each doing one job for your Totango account.
Ask Elaichi to work across your apps.
Which accounts renewing this quarter have dropped in usage?
Summarize recent events for the Acme Corp account.
Update the health notes on Globex after today's call.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Totango account in plain language.
Health, usage and plan details come straight from live Totango records, not a stale export.
Copy the endpoint
AI apps
One endpoint brings Totango to every client.
Claude, ChatGPT and Cursor reach Totango through one governed endpoint, no SDK and no shared key.
Tool catalog
45 Totango tools, ready without writing code.
Accounts, users, collections, usage, events and SCIM, cataloged the moment Totango connects.
Toolboxes
Every team gets its own Totango toolbox.
Customer Success, Support and IT each see only the Totango tools their work needs.
Shared connections
Share a Totango connection, never the key.
One person connects Totango, teammates work through it, and nobody else ever sees the credential.
Audit log
Every Totango change is traced to a person.
When, who, what happened and which account, in an append-only log you can search.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Totango digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Totango
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Totango
Queued
Workflows
A schedule starts the Totango work itself.
Accounts are fetched and grouped, an agent drafts the digest, a person approves, Totango updates.
Totango health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Customer Success 34%
Enterprise CS 27%
Support 21%
Renewals 18%
Collections and dashboards
Totango account health, counted without a model.
Four metrics, fourteen days of accounts created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Totango
All three can connect Totango to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Totango tools | Allow or restrict single Totango 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 Totango 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 | Free for one person; $15 per user per month on Gold. | 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.
Totango tools for your AI agents
45 tools are ready to call through Elaichi's MCP endpoint the moment you connect Totango, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Totango to Claude?
Connect Totango in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Totango's own sign-in step is a single API key, which you paste in when you connect it in Elaichi. There is no OAuth application to register and no client ID or secret to generate.
Does Totango work with ChatGPT and Cursor as well as Claude?
Yes. Once Totango is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Totango once and every client you use gets it.
What can an AI agent actually do with my Totango data?
It can search Totango accounts and users, pull an account's plan summary and status, read recent events and usage, and update account or user attributes after a call. It can also tidy collections and, for admins, manage Totango users and groups through SCIM and review the audit log. Short concrete asks, like "find enterprise accounts with a red health status", work better than long paragraphs.
Does connecting Totango give the AI access to every account in my workspace?
No. Access follows the person who signed in, so an agent working in Totango sees and changes only what that person could see and change in Totango themselves. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Totango?
Yes. Restrictions in Elaichi work per action, so you can allow searching Totango accounts while restricting updates, or restrict deleting a Totango user, on a role or on one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Totango connection when someone leaves?
Offboarding that person in Elaichi ends their access to Totango at once, across every client they used. A shared Totango connection keeps working for everyone else on the team. If you want Totango gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Totango MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Totango 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, Microsoft Copilot, 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 Totango?
Yes. Both let Claude, ChatGPT or Cursor use Totango. 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 Totango call.
How is Elaichi different from Composio for Totango?
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 Totango: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Totango in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot