# Pigment MCP connector

Connect Pigment to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can list your Pigment applications, blocks and views, export metrics and tables, and trigger imports and data flows, with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Pigment |
| Category | BI |
| AI tools | 19 |
| 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 Pigment is connected

- Which Pigment data flows failed overnight?
- Export the FY25 revenue forecast table from the sales planning application.
- Trigger the actuals import and tell me when it finishes.

## Connect Pigment in Elaichi

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

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

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

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

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

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

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

### Pull the forecast numbers before the review

Finance. Ask for an export of a metric or table from a Pigment application and get the figures in the chat. No need to open the model and hunt for the right view.

### Kick off month-end imports and watch them land

Finance. Trigger an import configuration in Pigment, then ask whether it finished. The agent checks the import status so actuals are in before the close meeting.

### Push the latest plan to Looker

Data. Create a push to Looker or a CSV push from a Pigment data flow so downstream dashboards carry the current plan instead of last week's numbers.

### Check which data flows ran overnight

RevOps. List every Pigment data flow and ask for the status of each one. Catch a failed refresh before the sales forecast call rather than after it.

### Find the headcount block in the right application

People. List Pigment applications and their blocks to locate the workforce plan, then export the headcount table for the hiring review.

### Upload supplier rates and confirm the snapshot

Supply chain. Create a file in Pigment with the new rate card, then list application snapshots to confirm which version of the demand plan is current.

## Elaichi vs Zapier MCP vs Composio for Pigment

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

Connect Pigment in Elaichi by pasting a Pigment API key, which you create in Pigment's settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Pigment is ready in your chat.

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

Yes. A Pigment connection in Elaichi is reached through one endpoint, https://api.elaichi.ai/mcp, and that same address works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Pigment once and every client you use picks it up.

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

An agent can list your Pigment applications, blocks, views, files and snapshots, export a metric, list or table, and show the result in the chat. It can trigger an import or a data flow, check whether it finished, upload a file, and push a data flow out as CSV or to Looker. Short, concrete asks work best, such as export the headcount table from the FY25 plan, rather than a long paragraph.

### Does connecting Pigment give the AI every application in my workspace?

No. Every call to Pigment runs inside the access of the person who signed in to Elaichi and the Pigment key behind the connection, so an agent only reaches the Pigment applications and blocks that access already allows. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond what Pigment grants.

### Can my team share one Pigment connection?

Yes. One person connects Pigment with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who triggered an import or exported a table, not a shared account.

### Can I stop an agent from triggering or changing things in Pigment?

Yes. Pigment restrictions in Elaichi are set per action, on a role or on one person, so you can let people export tables while restricting import triggers, data flow triggers or file uploads. A restricted tool still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

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

Offboarding someone in Elaichi ends their access to Pigment at once, across every client they used. A shared Pigment connection keeps working for everyone else on the team. If you disconnect Pigment in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

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

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

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

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

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

## All 19 Pigment tools

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

- **List all Pigment data flows** (List). List the Data Flows configured in a Pigment application. Returns: dataFlowId, name, description, application_id, steps. Required: application_id.
- **Create a Pigment data flow trigger** (Create). Trigger an execution of a Data Flow in Pigment. Returns: dataFlowExecutionId. Required: dataFlowId. 400 if the Data Flow has no runnable steps; 429 if too many concurrent executions are already running.
- **Create a Pigment push CSV** (Create). Push a CSV file to a Pigment import configuration. The import starts asynchronously and Returns: importId. Required: configuration_id, file.
- **Create a Pigment push looker** (Create). Trigger a Looker Look import in Pigment. Pigment pulls the Look data and runs the import asynchronously. Returns: importId. Required: configuration_id.
- **List all Pigment import configurations** (List). List Pigment import configurations for the given application and block. Returns: id, name. The returned id is the configurationId needed to trigger imports or push data.
- **Create a Pigment import trigger** (Create). Trigger an automated import operation in Pigment for an integration-based import, list data copy or metric data copy; the pipeline type is detected from the configuration. Returns: importId. Required: configuration_id.
- **List all Pigment applications** (List). List metadata for every Pigment Application in the Workspace associated with the API key. Returns each application's id (UUID) and name — the values used to scope the other Pigment metadata calls. The source documents no additional fields or filters for this endpoint.
- **List all Pigment applications snapshots** (List). List metadata for all application snapshots in Pigment, including scheduled, in progress and failed ones. Returns: id, name, status, date, applications.
- **List all Pigment blocks** (List). List Pigment block metadata (metrics, lists, and tables) for an application. Returns: id, name, type.
- **Get single Pigment export view by ID** (Get). Export the data of a specific Pigment view as a CSV file. Returns the view's data as a CSV file (text/csv). Optional date_format (Legacy or Iso8601) and field_delimiter (Semicolon or Comma) control output formatting. Fails with 413 if the view is too big (use block export APIs instead) or 422 if the view type is not…. Required: id.
- **Create a Pigment export list** (Create). Export the data of a specific Pigment list as a CSV file. Returns the exported list data as a CSV file (text/csv). An optional ListRequest JSON body refines the export; sending {} accepts the list's defaults. Required: list_id.
- **Create a Pigment export metric** (Create). Export the data of a specific Pigment metric as CSV. Returns the exported data as a CSV file (text/csv). The optional MetricRequest JSON body refines the export; omit it or send an empty object to accept upstream defaults. Required: metric_id.
- **Create a Pigment export table** (Create). Export the data of a specific Pigment table as a CSV file. Returns the table's exported data as a CSV file (text/csv), not a JSON object, so its contents are content-type-specific. Optional TableRequest body refines the export; an empty {} body accepts defaults. Required: table_id.
- **List all Pigment files** (List). List the file metadata of a Pigment application with cursor-based pagination. Returns: organizationId, application_id, id, displayFilename, contentType, mimeType, sizeBytes, uploadedBy, uploadedAt. Required: application_id.
- **Create a Pigment file** (Create). Upload a file to a Pigment application as multipart form-data. Returns the uploaded file's metadata: id, displayFilename, contentType, sizeBytes, uploadedAt. Required: application_id, file.
- **Get single Pigment content by ID** (Get). Download a file's content from a Pigment application. Returns the raw file bytes (binary download, not a JSON object). Required: id, application_id.
- **List all Pigment views** (List). List view metadata for a block in Pigment. Returns: id, name, type. Use the returned view ids with the view export endpoint.
- **Get single Pigment data flow status by ID** (Get). Get the status of a Data Flow execution in Pigment. Returns: dataFlowExecutionId, dataFlowId, status, createdAt, completedAt, steps. Status is InProgress, Completed, PartialFailure, or Failed. Required: id. Rate limited — on 429, retry after the Retry-After delay.
- **Get single Pigment import status by ID** (Get). Get the status of a csv import, integration import, list data copy or metric data copy operation in Pigment by id. Returns: importId, createdAt, completedAt, importStatus, errorsDetails, detailedReport. Required: id. Set included_detailed_report=true for summary statistics; defaults to false.
