# Informatica MCP connector

The Informatica connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent manage Informatica users, user groups, roles and privileges as the person who signed in, with every change written to an audit log.

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

## Facts

| | |
| --- | --- |
| Application | Informatica |
| Category | IPAAS |
| AI tools | 280 |
| 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 Informatica is connected

- Add Priya to the finance pipelines user group
- Which Informatica users hold the administrator role?
- Create a read only role with the monitoring privileges

## Connect Informatica in Elaichi

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

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

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

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

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

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

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

### Onboard a new analyst in one ask

IT. Create the Informatica user, put them in the right user groups and give them the roles their team uses, from a single sentence instead of five screens.

### Review who holds the administrator role

Security. List every Informatica user with a given role, spot the accounts that should not have it, and remove the role on the spot.

### Keep project groups current

Data engineering. Add this quarter's hires to the pipelines user group and remove the people who rotated off, without opening the admin console.

### Answer an access audit question in minutes

Compliance. Pull the list of Informatica roles and the privileges each one grants, then hand the auditor a clean summary.

### Offboard a leaver without a checklist

People operations. Remove their roles and groups, sign out every Informatica session they hold and delete the user, in one go.

### Build a role instead of copying privileges

Data governance. Create a new Informatica role, attach exactly the privileges it needs and assign it to the user group that owns that work.

## Elaichi vs Zapier MCP vs Composio for Informatica

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

In Elaichi, pick Informatica from the catalog and paste in your Informatica API key. 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. Informatica now shows up in Claude as you, with your own Informatica access.

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

Yes. Informatica is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up for each client.

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

It can list the users, user groups and roles in your Informatica organization, create new ones, add or remove people from groups, grant or revoke roles and privileges, and sign out sessions. Ask for things like adding Priya to the finance pipelines group or finding every user who holds the administrator role. Short, concrete asks work better than long paragraphs.

### Does connecting Informatica give the AI access to everything in my organization?

No. Every call runs as the person who signed in, so an agent can only see and change the Informatica users, groups and roles that person is already allowed to manage. Elaichi can narrow that further with its own roles and restrictions, and it never widens it.

### Can my team share one Informatica connection?

Yes. One administrator connects Informatica with the API key and shares the connection with a team in Elaichi. Nobody else ever handles the key, and each person still signs in to Elaichi as themselves, so the audit log names who made each change to Informatica users, groups or roles.

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

Yes. Restrictions in Elaichi apply per action, for instance deleting an Informatica user or removing privileges from a role, and are set 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 an Informatica connection when someone leaves?

Offboarding them in Elaichi ends their access to Informatica through every client at once. A shared Informatica connection keeps working for everyone else on the team. If you disconnect Informatica once in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

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

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

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

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

## All 280 Informatica tools

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

- **Create a Informatica auth** (Create). Log in to Informatica Intelligent Cloud Services with a user name and password (platform REST API v3). Returns the session ID and the org-specific base API URL. Used internally to authenticate the connected account.
- **Create a Informatica jwt token** (Create). Generate a JSON Web (JW) access token from the current session ID. The token secures Data Governance and Catalog API calls and expires after 30 minutes. Used internally to authenticate the connected account.
- **Informatica sessions logout** (Action). Log out of the current Informatica Intelligent Cloud Services session (platform REST API v3). Ends the session that this connected account uses until the next scheduled re-login.
- **Informatica sessions logout v 2** (Action). Log out of the current session (platform REST API v2). Ends the session that this connected account uses until the next scheduled re-login.
- **Informatica sessions logout all** (Action). End all sessions of a user (platform REST API v2). Ends the session that this connected account uses until the next scheduled re-login.
- **List all Informatica users** (List). List users in the organization (platform REST API v3). Filter with q, for example userName=='jdoe' or userId=='&lt;id&gt;'.
- **Create a Informatica user** (Create). Create a user in the organization (platform REST API v3). Provide either roles or groups so the user has privileges.
- **Delete a Informatica user by ID** (Delete). Delete a user by ID (platform REST API v3).
- **Informatica users add roles** (Add). Assign roles (role names) to a user (platform REST API v3).
- **Informatica users remove roles** (Delete). Remove roles (role names) from a user (platform REST API v3).
- **Informatica users add groups** (Add). Assign user groups (group names) to a user (platform REST API v3).
- **Informatica users remove groups** (Delete). Remove user groups (group names) from a user (platform REST API v3).
- **List all Informatica user groups** (List). List user groups (platform REST API v3). Filter with q, for example userGroupName=='Analysts' or userGroupId=='&lt;id&gt;'.
- **Create a Informatica user group** (Create). Create a user group (platform REST API v3). At least one role ID is required.
- **Delete a Informatica user group by ID** (Delete). Delete a user group by ID (platform REST API v3).
- **Informatica user groups add roles** (Add). Assign roles (role names) to a user group (platform REST API v3).
- **Informatica user groups remove roles** (Delete). Remove roles (role names) from a user group (platform REST API v3).
- **Informatica user groups add users** (Add). Assign users (user names) to a user group (platform REST API v3).
- **Informatica user groups remove users** (Delete). Remove users (user names) from a user group (platform REST API v3).
- **List all Informatica roles** (List). List roles (platform REST API v3). Filter with q (roleId=='&lt;id&gt;' or roleName=='Designer') and set expand=privileges to include privileges.
- **Create a Informatica role** (Create). Create a custom role with a set of privileges (platform REST API v3).
- **Delete a Informatica role by ID** (Delete). Delete a custom role by ID (platform REST API v3).
- **Informatica roles add privileges** (Add). Add privileges to a custom role (platform REST API v3). Use privilege names from privileges.list.
- **Informatica roles remove privileges** (Delete). Remove privileges from a custom role (platform REST API v3). Use privilege names from privileges.list.
- **List all Informatica privileges** (List). List privileges available in the organization (platform REST API v3). Set q=status=='All' to include disabled and unassigned privileges.
- **List all Informatica objects** (List). Find assets (projects, folders, mappings, tasks, taskflows, connections) in the organization (platform REST API v3). Filter with q, for example type=='MTT' and location=='Default'.
- **Create a Informatica object lookup** (Create). Look up asset IDs from paths, or paths from IDs (platform REST API v3). Use the IDs for export, import and source control requests.
- **Create a Informatica export job** (Create). Start an export job that packages assets into a ZIP file (platform REST API v3). Use object_lookups.create or objects.list for asset IDs.
- **Get single Informatica export job by ID** (Get). Get the status of an export job (platform REST API v3). Set expand=objects to include per-asset status.
- **Informatica export jobs get log** (Export). Download the log of an export job as text (platform REST API v3).
- **Informatica export jobs download package** (Export). Download the ZIP package of a completed export job (platform REST API v3).
- **Informatica import jobs upload package** (Import). Upload an export ZIP package for import (platform REST API v3). Returns the job ID to pass to import_jobs.create. Sent as multipart/form-data with a package file field.
- **Create a Informatica import job** (Create). Start an import job for an uploaded package (platform REST API v3). Optionally map objects and set conflict resolution.
- **Get single Informatica import job by ID** (Get). Get the status of an import job (platform REST API v3). Set expand=objects to include per-asset status.
- **Informatica import jobs get log** (Import). Download the log of an import job as text (platform REST API v3).
- **Create a Informatica fetch state job** (Create). Start a fetchState job that exports the run state (for example last run time) of assets (platform REST API v3).
- **Get single Informatica fetch state job by ID** (Get). Get the status of a fetchState job (platform REST API v3).
- **Informatica fetch state jobs download package** (Download). Download the state package ZIP of a completed fetchState job (platform REST API v3).
- **Informatica load state jobs upload package** (Upload). Upload a state package ZIP for a loadState job (platform REST API v3). Sent as multipart/form-data with a package file field.
- **Create a Informatica load state job** (Create). Start a loadState job that applies uploaded asset run state to the organization (platform REST API v3).
- **Get single Informatica load state job by ID** (Get). Get the status of a loadState job (platform REST API v3).
- **List all Informatica schedules** (List). List schedules (platform REST API v3). Filter with q, for example status=='enabled'.
- **Get single Informatica schedule by ID** (Get). Get a schedule by ID (platform REST API v3).
- **Create a Informatica schedule** (Create). Create a schedule (platform REST API v3).
- **Informatica schedules partial update** (Update). Update a schedule, or enable or disable it with status (platform REST API v3). Send the changes inside schedules[0] with the schedule id and scheduleFederatedId.
- **Delete a Informatica schedule by ID** (Delete). Delete a schedule by ID (platform REST API v3).
- **List all Informatica security logs** (List). List security log entries such as logins and asset changes (platform REST API v3). Filter with q, for example entryTime&gt;='2024-01-01T00:00:00.000Z'.
- **Get single Informatica license by ID** (Get). Get the license information of an organization or sub-organization by org ID (platform REST API v3).
- **Update a Informatica license by ID** (Update). Update the licenses of a sub-organization (platform REST API v3). Requires the parent organization admin.
- **Update a Informatica agent service by ID** (Update). Start or stop a service on a Secure Agent (platform REST API v3).
- ...and 230 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
