# Tealium MCP connector

Connect Tealium to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can look up visitors, send events, publish iQ profiles and manage users, each person acting under their own Tealium access.

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

## Facts

| | |
| --- | --- |
| Application | Tealium |
| Category | Marketing Automation |
| AI tools | 52 |
| 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 Tealium is connected

- Find the visitor with email jane@example.com and summarize their profile.
- Which iQ profiles have unpublished changes right now?
- Add Priya Shah to the Marketing group in Tealium.

## Connect Tealium in Elaichi

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

1. Open Connections, choose Add connection, and pick Tealium.
2. Optionally set Share with, then press Connect.
3. Paste a Tealium API key. One person generates a token in Tealium 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 Tealium tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## Tealium 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 Tealium 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 Tealium 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 Tealium through Elaichi

### Check what Tealium knows about a visitor

Marketing. Ask for a visitor by ID or attribute and get their profile back in the chat, before a campaign review or a customer call.

### Send a test event into Tealium

Marketing ops. Push an event, or a batch of them, into Tealium from a conversation to confirm a new data layer change arrives the way you expect.

### Handle a deletion request in minutes

Privacy. Find the visitor records tied to a privacy request, confirm them, and delete them in bulk, with the audit log recording who did it and when.

### Publish an iQ profile after review

Web. Ask which iQ profiles are waiting, read what changed, and publish the right one without opening the Tealium console.

### Add a new hire to Tealium

IT. Create the user, place them in the right groups, and update or remove them later from the same chat window.

### Update tag templates across profiles

Analytics. Change a tag template once and update several iQ profiles together instead of editing each one by hand.

## Elaichi vs Zapier MCP vs Composio for Tealium

All three can connect Tealium 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 Tealium tools | Allow or restrict single Tealium 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 Tealium 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 Tealium to Claude?

Connect Tealium in Elaichi by pasting a Tealium API key, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Tealium is ready in your next conversation.

### Does Tealium work with ChatGPT and Cursor as well as Claude?

Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. Connect Tealium once in Elaichi and every client you use picks it up.

### What can an AI agent actually do with my Tealium data?

An agent can search Tealium visitors and read a visitor's profile, send single or bulk events, list and publish iQ profiles, update tag templates, and add, change or remove users and check their groups. It can also find and delete privacy visitor records when you handle a deletion request. Short, concrete asks such as "find the visitor with this email" work better than long sentences.

### Does connecting Tealium give the AI access to every account and profile?

No. An agent can only do what the Tealium account behind the connection can do, and only on behalf of the person who signed in to Elaichi, so a Tealium account limited to one profile stays limited to that profile. Elaichi can narrow that access further with roles and restrictions, but it can never widen it.

### Can my team share one Tealium connection?

Yes. One person connects Tealium in Elaichi and shares it with a team, and nobody else ever handles the Tealium API key. Each teammate still signs in to Elaichi as themselves, so every event, deletion or publish in the audit log carries their own name.

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

Yes. Restrictions in Elaichi work per action, so you can allow searching Tealium visitors while restricting bulk deletes or user removals, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Tealium connection when someone leaves?

Offboarding a person in Elaichi ends their access to Tealium at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A Tealium connection they shared keeps working for everyone else on the team. If you later disconnect Tealium once in Elaichi, it disappears from every client at the same time.

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

Yes. Tealium 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 Tealium?

Yes. Both let Claude, ChatGPT or Cursor use Tealium. 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 Tealium call.

### How is Elaichi different from Composio for Tealium?

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 Tealium: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 52 Tealium tools

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

- **Create a Tealium auth** (Create). Exchange a username and API key for a Tealium JWT bearer token valid for 30 minutes. Returns: token, host. The username and key are supplied from the connection credentials. Required: account, profile, username, key.
- **Create a Tealium auth token** (Create). Generate a long-lived bearer token for the Tealium SCIM API; the token expires after 90 days. Returns: access_token, token_type, expires_in, scope. Required: account, profile, username, key.
- **Tealium auth tokens revoke** (Revoke). Revoke a Tealium long-lived token immediately; revocation is permanent and cannot be undone. Returns an empty 200 response on success, even if the token is already invalid. Use the credentials that generated the token. Required: token, account, profile, username, key.
- **Create a Tealium event** (Create). Send a single event to Tealium as a JSON payload. Returns an empty 200 response on success. Requires tealium_account, tealium_profile, and tealium_event; arbitrary attribute fields such as page_name are accepted alongside them. JSON keys must not contain periods. Required: tealium_account, tealium_profile, tealium_event.
- **List all Tealium events** (List). Send a single event to Tealium via GET query parameters, returning a 1x1 transparent tracking GIF (image/gif) instead of JSON for pixel-based implementations. Required: tealium_account, tealium_profile, tealium_event. Additional attribute key-value pairs can be appended to the query string.
- **Tealium events bulk create** (Create). Send up to 10 events to Tealium in a single JSON request, applying a shared object of common fields (tealium_account, tealium_profile, tealium_visitor_id, etc.) to all of them. Returns an empty 200 response on success. Requires an events array; individual events can override or extend the shared fields. Required: shared, events.
- **Create a Tealium integration event** (Create). Send a single server-side integration event to a Tealium data source for a given account and profile. Returns an empty 204 response on success. Required: account, profile, datasource_id, tealium_event.
- **Tealium visitors search** (Search). Get a Tealium visitor profile by looking up a Visitor ID attribute value. Returns: audiences, badges, attributes, currentVisit, dates, metrics, properties, flags. Required: account, profile, attributeId, attributeValue. Max 150 attributeId values in responseFilters.
- **List all Tealium privacy visitors** (List). List the Visitor ID attributes available for a Tealium account and profile. Returns a map of numeric attribute IDs to their display names (e.g. 43: "Email Address", 57: "Tax ID Number") for use in privacy lookups. Required: account, profile.
- **Get single Tealium privacy visitor by ID** (Get). Get the processing status of a Tealium visitor deletion request. Returns a map keyed by the transaction id whose value is PENDING, SUCCESS, or FAILED. Deletion requests may take up to 30 days to complete. Required: id, account, profile.
- **Tealium privacy visitors search** (Search). Retrieve a visitor's known data from Tealium for GDPR/CCPA lookup by Visitor ID attribute. Returns: audiences, badges, attributes, transactionId. Required: account, profile, attributeId, attributeValue.
- **Tealium privacy visitors bulk delete** (Delete). Queue deletion of a Tealium visitor record for GDPR/CCPA erasure, covering all data for the visitor ID including stitched visitors; processing may take up to 30 days. Returns: transactionId. Required: account, profile, attributeId, attributeValue.
- **List all Tealium iq profiles** (List). Get an iQ Tag Management profile in Tealium, including its configuration components and version history. Returns: account, profile, versionTitle, version, minorVersion, parentVersion, creation, customTargets, versionDetails, environmentVersions, dataCloudLinkedProfiles, libraryType, linkedProfiles, and 11 more. Required: account, profile.
- **Tealium iq profiles publish** (Publish). Publish a saved iQ Tag Management profile version to one or more targets. Returns: publishId, account, profile, versionId, operatorId, createdDate, publishTargets, title, revisionId, notes. Required: account, profile, versionId (format YYYYMMDDhhmm).
- **Get single Tealium iq profile by ID** (Get). Check the status of an iQ Tag Management profile publish request by polling by id. Returns: publishId, publishTargetEventResponses. Required: account, profile, id (the publishId returned by the publish or save-and-publish call). Rate-limited to one request per second per publish ID; faster polling returns 429.
- **Tealium iq profiles bulk update** (Update). Save changes to an iQ Tag Management profile via a JSON-Patch-style operationList (add/replace/remove on /extensions, /events, /variables, /tags, /loadRules; only JavaScript Code extensions are supported). Returns the saved profile (account, profile, version, minorVersion) and, when publish is true, the publish result with its status and data…
- **Update a Tealium iq tag template by ID** (Update). Update a tag template in a Tealium iQ account profile. Returns the saved template version including versionTitle, saveType, notes, and templateData content. Required: id, account, profile, notes, templateData.content. To add or remove a tag template you must add or remove the tag.
- **List all Tealium SCIM users** (List). List Tealium SCIM users in the account. Returns a SCIM ListResponse with totalResults, startIndex, itemsPerPage, and Resources (each user's id, userName, name, emails, active, meta). Filter by userName with filter using the eq operator. Max 100 per page.
- **Get single Tealium SCIM user by ID** (Get). Get a single Tealium SCIM user by id. Returns the full user object including id, userName, displayName, externalId, name (givenName, familyName), emails, active, and meta. Required: id.
- **Create a Tealium SCIM user** (Create). Create a Tealium SCIM user in the account. Returns the created user object including id, userName, displayName, externalId, name, emails, active, and meta. Required: userName (an email address).
- **Update a Tealium SCIM user by ID** (Update). Replace a Tealium SCIM user by id with a full user payload (SCIM PUT). Returns the updated user object including id, userName, name, emails, active, and meta. Required: id, userName.
- **Delete a Tealium SCIM user by ID** (Delete). Delete a Tealium SCIM user by id, removing their access to the account (a user on multiple accounts remains on the other accounts). Returns an empty 204 response on success. Required: id.
- **Tealium SCIM users partial update** (Update). Patch an existing SCIM user in Tealium with add, replace, or remove operations on attributes such as active, displayName, externalId, and name. Returns an empty 204 response on success. Requires user_id plus a patch body with schemas and Operations; userName cannot be changed.
- **List all Tealium SCIM groups** (List). List all SCIM groups in the Tealium account, including built-in groups such as Standard User and Account Admins. Returns: schemas, totalResults, startIndex, itemsPerPage, Resources. Max 100 per page.
- **Get single Tealium SCIM group by ID** (Get). Get a single SCIM group by id from the Tealium account. Returns: schemas, id, displayName, members, meta. Required: id.
- **Create a Tealium SCIM group** (Create). Create a custom group in the Tealium account, optionally adding members. New groups are created without permissions and built-in group names are reserved. Returns: schemas, id, displayName, members, meta. Required: displayName.
- **Update a Tealium SCIM group by ID** (Update). Update a SCIM group by id to rename a custom group or change its members. Built-in groups cannot be renamed. Returns: schemas, id, displayName, members, meta. Required: id, displayName.
- **Delete a Tealium SCIM group by ID** (Delete). Delete a custom group by id from the Tealium account. Built-in groups cannot be deleted. Returns an empty 204 response on success. Required: id.
- **Tealium SCIM groups partial update** (Update). Patch a Tealium SCIM group to update its members or rename a custom group. Returns the updated group: id, displayName, members, meta. Required: group_id. Sends a SCIM PatchOp body with schemas and Operations (op, path, value); built-in groups cannot be renamed and SCIM cannot change group permissions.
- **List all Tealium SCIM sync logs** (List). Export Tealium SCIM sync audit log entries for an account. Returns: timestamp, action_type, resource_type, target_email, target_first_name, target_last_name, target_user_uuid, external_id, idp_source, http_status, outcome, correlation_id, account_name, error_message. Required: account. Up to 5000 entries per export (default 1000).
- **Create a Tealium auth v 2** (Create). Exchange a Tealium iQ username and API key for a JWT bearer token that authenticates subsequent V2 API calls. Returns: token. Required: username, key. The token is valid for 30 minutes — reuse it until expiry instead of requesting a new one per call to avoid throttling.
- **Create a Tealium hosted data layer** (Create). Upload a hosted data layer object or JSON file to a Tealium account and profile. Returns an empty 200 response on success; changes may take up to one hour to reflect. Required: account, profile, datalayer_id, and a JSON body under 1MB whose keys contain no periods.
- **Update a Tealium hosted data layer by ID** (Update). Update a hosted data layer object or JSON file in a Tealium account and profile. Returns an empty 200 response on success; changes may take up to one hour to reflect. Required: id, account, profile, and a JSON body under 1MB whose keys contain no periods.
- **Delete a Tealium hosted data layer by ID** (Delete). Delete a hosted data layer object or JSON file from a Tealium account and profile by id. Returns an empty 200 response on success. Required: id, account, profile.
- **Get single Tealium hosted data layer by ID** (Get). Get file metadata for a hosted data layer object or JSON file in a Tealium account and profile; a 200 response confirms the upload succeeded. Returns: file, lastModified, size. Required: id, account, profile.
- **List all Tealium hosted data layers** (List). List up to 1,000 hosted data layer objects and JSON files in a Tealium account and profile. Returns: isTruncated, continuationToken, fileStatuses, badges. Required: account, profile.
- **Tealium hosted data layers search** (Search). Search failed hosted data layer uploads for a Tealium account and profile to identify files whose transfer failed and can be re-uploaded. Returns: account, profile, count, failedUploads. Required: account, profile. Up to 5,000 records, not paginated.
- **List all Tealium iq revisions** (List). List Tealium iQ revisions for a profile. Returns an array of revision IDs (YYYYMMDDHHMM timestamps) in reverse chronological order, newest first. Required: account, profile.
- **Get single Tealium iq revision by ID** (Get). Get the details of a single Tealium iQ revision by id. Returns: account, profile, name, time_created, checksums, revision_id, comment, created_by, targets_published. Required: account, profile, id.
- **Tealium iq revisions search** (Search). Download the Tealium iQ revision bundle (a .zip of the published JavaScript files) for a revision and target environment. Returns: account, profile, name, time_created, checksums, revision_id, comment, created_by, targets_published. Required: account, profile, revision_id, environment. Only works for the latest published revision.
- **Tealium omnichannel files search** (Search). Search Tealium omnichannel file import statuses for files sharing a file prefix within a date range. Returns file status records with _id, account, profile, file metadata, and processing status history. Required: account, profile, filePrefix, startDate, endDate.
- **Get single Tealium omnichannel file by ID** (Get). Get the import status of a single Tealium omnichannel file by id (the file name, e.g. sales-transaction_2016feb4v50.csv). Returns: _id, account, created_at, file, node_id, profile, status. Required: account, profile, id.
- **Tealium omnichannel files get count** (Get). Count uploaded Tealium omnichannel files for a file prefix within a date range. Returns the aggregate count object with count. Required: account, profile, filePrefix, startDate, endDate. If the count exceeds 50, narrow the date range.
- **Get single Tealium context API visitor by ID** (Get). Get visitor moments for a Tealium Context API visitor by anonymous visitor ID. Returns the visitor's audiences, badges, metrics, properties, flags, and dates. Required: account, profile, engine_id, id.
- **Tealium context API visitors search** (Search). Look up visitor moments in Tealium Context API by matching a Visitor ID attribute. Returns the visitor's audiences, badges, metrics, properties, flags, and dates. Required: account, profile, engine_id, attributeId, attributeValue.
- **Tealium visitor data enrichment enrich visitor** (Action). Send real-time visitor data to Tealium EventStream as name/value pairs in the query string. Returns the visitor enrichment data object with metrics, dates, properties, flags, badges, and audiences. Required: tealium_account, tealium_profile, tealium_vid.
- **Tealium visitor data enrichment enrich visitor JSON** (Action). Send visitor data to the Tealium Collect endpoint from server-side systems by POSTing a JSON data object with an event type of view or link. Returns the visitor enrichment data object with metrics, dates, properties, flags, badges, and audiences. Required: account, profile.
- **Get single Tealium dle visitor by ID** (Get). Get a Tealium visitor's data layer enrichment profile. Returns: metrics, dates, flags, current_visit, badges, audiences. Required: account, profile, id (the visitor id from the utag_main v_id cookie). Returns 200 with an empty JSON body when the visitor has no active visit; 404 if data layer enrichment is disabled.
- **List all Tealium dle profile definitions** (List). Get the Data Layer Enrichment profile definition for a Tealium profile, i.e. the audience and badge definitions used to resolve ID-keys from the DLE Public API. Returns: audiences, badges. Required: account, profile. Returns 404 if data layer enrichment is disabled.
- **Create a Tealium regional event** (Create). Send a single event to Tealium Collect's region-specific endpoint (regional host from the authentication API). Returns an acceptance acknowledgement with no documented response body. Requires a JSON event payload with tealium_account, tealium_profile, tealium_event, and tealium_datasource fields plus event attributes. Required: tealium_account, tealium_profile, tealium_event.
- ...and 2 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
