# 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.

Source: https://elaichi.ai/connectors/totango/

## Facts

| | |
| --- | --- |
| Application | Totango |
| Category | CRM |
| AI tools | 45 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Totango is connected

- 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.

## Connect Totango in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Totango.
2. Optionally set Share with, then press Connect.
3. Paste a Totango API key. One person generates a token in Totango and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Totango tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Totango MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Totango MCP connector for Microsoft Copilot

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

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.
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.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Totango tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Totango through Elaichi

### Catch the account up after a call

Customer Success. 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.

### Find accounts at risk before renewal

Customer Success. 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.

### See what a customer actually uses

Account Management. 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.

### Know who you are talking to

Support. 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.

### Keep account fields and collections clean

Revenue Operations. 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.

### Manage who has a Totango seat

IT. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Totango connection?

Yes. One person connects Totango in Elaichi and shares the connection with a team, so nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every Totango call in the audit log names the person who made 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.

## All 45 Totango tools

Every tool below is callable through https://api.elaichi.ai/mcp once Totango is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Update a Totango account by ID** (Update). Create or update Totango accounts in batch with their attributes and tags. Returns: batch_id, service_id, status, time_received, num_received, num_accepted, invalid_updates. Required: accounts. Max 1,000 accounts per request; accepted updates cannot be undone.
- **Totango accounts search** (Search). Search Totango accounts matching filter criteria. Returns the response envelope: response.status, response.stats.total_hits, and response.accounts.hits with name, display_name, last_activity_time, and selected_fields. Max 1,000 per page; page via offset. Required: accounts.
- **Totango accounts get plan summary** (Get). Get the plan summary of a Totango account. Returns: plan, updated_by, updated_date, _version. Required: account_id.
- **Update a Totango accounts attribute by ID** (Update). Create or update Totango account attribute definitions in batch. Returns: batch_id, service_id, status, time_received, num_received, num_accepted, invalid_updates. Asynchronous ingestion: attributes cannot be deleted via this endpoint and only name is updatable afterwards. Required: attribute_definitions.
- **Update a Totango accounts user by ID** (Update). Create or update Totango account users along with their attributes and tags, in batches of up to 1,000 users per request; received updates are irreversible and cannot be undone. Returns: updateId, service_id, status, time_received, num_received, num_accepted, invalid_updates. Required: users.
- **Update a Totango users attribute by ID** (Update). Create or update user attribute definitions in Totango. Returns: updateId, service_id, status, time_received, num_received, num_accepted, invalid_updates. Required: attribute_definitions. Only name and is_sensitive are updatable on existing definitions; once received, update requests are irreversible and cannot be undone.
- **Update a Totango collection by ID** (Update). Update a batch of Totango collections of a given type along with their attributes. Returns: batch_id, service_id, status, time_received, num_received, num_accepted, invalid_updates. Required: collection_type, collections. Max 1,000 collections per request; attribute keys must already be defined; updates are irreversible once accepted.
- **Totango collections search** (Search). Search collections linked to accounts in Totango by matching criteria. Returns the matching collection records including their id, account_id, and attribute values.
- **Update a Totango collection attribute by ID** (Update). Update collection attribute definitions for a Totango collection type. Accepted updates are ingested asynchronously; returns batch_id, service_id, status, time_received, num_received, and num_accepted. Required: collection_type, attribute_definitions.
- **Update a Totango usage by ID** (Update). Submit usage updates for account users in Totango. Accepts a batch of up to 1,000 usage updates per request and Returns: batch_id, service_id, status, time_received, num_received, num_accepted, invalid_updates. Required: usages. Updates are irreversible once received.
- **Get single Totango status by ID** (Get). Get the processing status of a Totango attribute records batch by batch id. Returns: batchId, serviceId, status, percentComplete, totalRecords, processedRecords, validRecords, invalidRecords, startTime, finishTime, duration. Required: id.
- **Totango users search** (Search). Search Totango users that match segment-style filter criteria and choose which fields to return for each hit. Returns the response envelope with total_hits, the users.hits entries (name, display_name, first/last activity times, selected_fields), and status. Required: query, terms, fields. Max 1000 results per call; 10,000 records total.
- **Delete a Totango user by ID** (Delete). Permanently delete an end user associated with a Totango account — irreversible (e.g. for GDPR removals), not intended for bulk deletes, and may take a few minutes to fully apply. Returns an empty 204 response on success. Required: account_id, id.
- **List all Totango whoami** (List). Get the currently authenticated Totango user (whoami). Returns the authenticated user record including its id. No additional parameters are required.
- **List all Totango events** (List). List the Totango events on an account's timeline, including touchpoints (type 'note'), tasks, alerts, and campaign events. Returns each event with id, timestamp, type, account, note_content, and properties. Required: account_id.
- **Totango events search** (Search). Search Totango events by criteria such as event type or date range. Returns a status envelope (status, service_id) with matching events in response.events.hits (id, timestamp, type, note_content, properties) and the total in response.events.total. Required: terms, fields, count, offset. Max 1000 events per call.
- **List all Totango audit logs** (List). List Totango audit log entries showing who viewed or changed end-user PII data. Returns one JSON entry per line with action, timestamp, totango_user, and service_id, plus action-specific fields (user_id, account_id, attribute_id, includes_sensitive_data). Required: startDate, endDate. Query span max one year; start and end years must be equal.
- **List all Totango SCIM users** (List). List Totango system users for a service via the SCIM API. Returns user records: schemas, meta, userName, name, externalId, title, groups, active, and license attributes. Required: service_id. Only one filter field (userName or externalId) can be used at a time.
- **Get single Totango SCIM user by ID** (Get). Get a Totango system user by id (the user's email) via the SCIM API. Returns the user record: schemas, meta, userName, name, externalId, title, groups, active, and license attributes. Required: service_id, id.
- **Create a Totango SCIM user** (Create). Create a Totango system user via the SCIM API. Returns: schemas, meta, userName, access_token, token_type, expires_in, scope. Required: service_id, schemas, userName (email, max 100 chars), and name.givenName / name.familyName (max 30 chars each).
- **Update a Totango SCIM user by ID** (Update). Update a Totango system user with a SCIM PatchOp — sent attributes override existing ones, others remain unchanged. Supports userName, name, externalId, title, managerEmail, managerExternalId, active, license, and groups. Returns an empty 204 response on success. Required: service_id, id, schemas, Operations.
- **Totango SCIM users replace** (Action). Replace a Totango system user by id — sent attributes override existing ones and attributes not sent are deleted, so send the full user record. Returns an empty 204 response on success. Required: service_id, user_id, schemas, userName.
- **List all Totango SCIM groups** (List). List the Totango SCIM groups (teams) of a service. Returns: schemas, id, displayName, members, meta, access_token, token_type, expires_in, scope. Required: service_id.
- **Get single Totango SCIM group by ID** (Get). Get a single Totango SCIM group (team) by id. Returns: schemas, id, displayName, members, meta, access_token, token_type, expires_in, scope. Required: service_id, id.
- **Totango SCIM groups replace** (Action). Set the users of a Totango SCIM group (team), overwriting its member list with the submitted SCIM Group payload. Returns the updated group with id, displayName, members, and meta. Required: service_id, group_id, displayName, and members.
- **Update a Totango SCIM group by ID** (Update). Add or remove users from a Totango SCIM group (team) via SCIM PatchOp operations. Returns the updated group with id, displayName, members, and meta. Required: service_id, id, Operations.
- **Get single Totango team by ID** (Get). Get a single Totango team by id. Returns the full team object including its id, display_name, terms, color, type, team_members, and team_role_settings. Required: id.
- **Totango successplays run** (Run). Run a manual Totango SuccessPlay for a given account, triggering its configured action (create a task or request information via form). Returns the plain string 'Success' when triggered. Required: successplayId, accountId. The SuccessPlay must be configured as manual and active.
- **Totango objective settings get status** (Get). Read the legacy objective status settings in Totango. Returns each status with id, displayName, createdBy, updatedBy, createdAt, and updatedAt. Custom objective status is no longer supported — results cover legacy objectives only.
- **Totango objective settings get category** (Get). Read the objective category settings in Totango. Returns each category with id, displayName, createdBy, updatedBy, createdAt, and updatedAt.
- **Create a Totango objective** (Create). Create an objective on a Totango account. A UUID objectiveId is generated when not supplied, and milestones may be automatic (attribute-driven) or manual. HTML markup is not supported. Required: accountId, objectiveData.
- **Totango objectives create by template** (Create). Create a Totango objective from an objective template in the template library. If a template role or owner fallback does not exist, the owner becomes the user performing the request. Required: accountId, ObjectiveTemplateId.
- **Totango objectives bulk update** (Update). Update an objective on a Totango account, or reopen a completed one by setting status back to In Progress. Use milestonesIdsToDelete to remove milestones. Required: accountId, objectiveId, objectiveData.
- **Totango objectives bulk delete** (Delete). Delete an objective from a Totango account and choose how its tasks are handled: deleteAllTasks, assignToOtherObjective, or keepOrphaned. newObjectiveId is required only when moving tasks to another objective. Required: accountId, objectiveId, objectiveTasksHandling.
- **List all Totango objective templates** (List). List Totango objective templates. Returns: id, displayName, createdBy, updatedBy, createdAt, updatedAt. Optional: objectiveTemplateIds to filter; extended=true returns full milestones and tasks, addCounts=true (not with extended) returns only their counts.
- **Get single Totango osp report by ID** (Get). Get the data of an Outcome Success Plan (OSP) standard report in Totango by its SBID. Returns the report's data payload, whose fields depend on the specific report definition. Required: id (the report's SBID).
- **Create a Totango task** (Create). Create a task in Totango. Returns a plain 'Success' confirmation on success. Requires activity_type_id (the flow ID); an unknown account_id returns a 400 'Account not found' error.
- **Update a Totango task by ID** (Update). Update a task in Totango by id — change its priority, due_date, assignee, account, status, or status label. Returns a plain 'Success' confirmation on success. Required: id.
- **Delete a Totango task by ID** (Delete). Delete a task in Totango by id. Returns a plain 'Success' confirmation on success. Required: id, account_id.
- **Create a Totango touchpoint** (Create). Create a new touchpoint on a Totango account. Returns: terms, fields, offset, count. Required: account_id and content. Content is limited to 12K characters.
- **Update a Totango touchpoint by ID** (Update). Update an existing touchpoint in Totango by its note id. Returns: terms, fields, offset, count. Required: id, event_id, account_id, and content. Content is limited to 12K characters.
- **Delete a Totango touchpoint by ID** (Delete). Delete a touchpoint from a Totango account by its note id. Required: id and event_id, both retrieved from the account's events.
- **List all Totango touchpoint types** (List). List the touchpoint types defined in Totango — the ids used as the meeting_type value on touchpoints. Returns a map of each type's id and name.
- **List all Totango touchpoint tags** (List). List all touchpoint reason tags in Totango. Returns a map of reason ids to names (id -&gt; name); the ids are the values accepted by touchpoint_tags when creating or updating touchpoints.
- **List all Totango activity types** (List). List Totango SuccessFlow activity types available for touchpoints and tasks. Returns each entry with activity_type_id, display_name, icon_class, system_type, default_type, disabled, and num_of_activities_assign_to. Takes no parameters.
